and more in a single search tool across platforms. Read the announcement here. |
12/12/2023 02:22 AM
Hi Team,
We have a requirement where we want to execute task instantaneously upon creation. we have a restriction where we are not able to utilize 'instantaneous provisioning' for particular security system and we are looking at workaround where we would be running a provisioning job for every 5 mins for that particular security system.
Hence we are looking for below information with respect to task creation and task provisioning :
1. How does task ids are assigned to tasks while creation, based on what aspect. is it in a sequential manner where it always creates a new account task first, assigns task id and then proceeds with creation of add access child task with incrementing the task id?
2. How does provisioning job picks up the tasks and executes them? does it picks tasks in sequential manner by incrementing the task ID and does it always picks up new account task first and then proceeds with add access task?
Thanks.
Solved! Go to Solution.
12/12/2023 06:47 PM
1. How does task ids are assigned to tasks while creation, based on what aspect. is it in a sequential manner where it always creates a new account task first, assigns task id and then proceeds with creation of add access child task with incrementing the task id?
Task IDs are assigned auto increment as its primary key & auto increment column in arstasks table, since account creation is mandatory account task created first then add access with parent task key added of new account.
2. How does provisioning job picks up the tasks and executes them? does it picks tasks in sequential manner by incrementing the task ID and does it always picks up new account task first and then proceeds with add access task?
Its based on task execution hierarchy defined in global config or it runs as per default task execution hierarchy
Task Execution Hierarchy | Use this setting to define the hierarchy to execute the tasks in EIC. This hierarchy represents the order (sequence) in which the task types are executed after running the WSRETRY job for a request. By default, EIC executes the task types in the following hierarchy:
Note The numerical values of the task types are internal values assigned in EIC and they cannot be modified. The default order in which the task types are executed in EIC is:
Note It is recommended to retain the default task execution hierarchy for the task types in EIC. To modify (customize) the default order in which the task types are executed in EIC, select the list of task types in the Task Execution Hierarchy field from Admin > Global Configurations > Request. Note When the Task Execution Hierarchy field is configured, it overrides the default task type execution hierarchy. EIC executes the task types in the same order in which the task types in this field were selected. The following options are available in the Task Execution Hierarchy field.
For more information about the data mapping, see Database Schema Reference in Enterprise Identity Cloud Schema Guide. |