Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
devel:documentation:scheduled_task [2017/11/04 08:54] poulm [Devel tutorials] |
devel:documentation:scheduled_task [2024/07/02 06:38] (current) neznajf Added link to Scheduled task for automatic role(s) recalculation |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | <- .: | ||
+ | ====== Scheduled Tasks ====== | ||
+ | Scheduled task is a task the start of which is planned in advance and when started it runs at the background of the application. Examples of scheduled tasks are identity lifecycle processes. The run of the scheduled task can be planned as one time action or run periodically. | ||
+ | |||
+ | We usually use scheduled task for task that: | ||
+ | * last long time - we donť want the user to wait for the reaction | ||
+ | * must be started in predefined time - synchronizations, | ||
+ | * its runs depends on each other - dtto | ||
+ | * runs periodically - notification, | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In CzechIdM task can have dependencies on each other. It means that specific scheduled task is started every time dependent scheduled task end. Thus one can plan running identities synchronization before every contracts synchronization run. | ||
+ | |||
+ | ====== Read more ====== | ||
+ | |||
+ | ===== Admin tutorials ===== | ||
+ | * [[tutorial: | ||
+ | * [[tutorial: | ||
+ | * [[tutorial: | ||
+ | |||
+ | ===== Admin guide ===== | ||
+ | * [[.adm: | ||
+ | * [[.adm: | ||
+ | * [[.adm: | ||
+ | |||
+ | ===== Devel guide ===== | ||
+ | * [[.application_configuration: | ||
+ | * [[.application_configuration: | ||
+ | * [[.synchronization: | ||
+ | |||
+ | ===== Devel tutorials ===== | ||
+ | * [[tutorial: |