...
- expirations: Run Expiration Policies.
- In most cases, it makes sense to run expirations once per day, as this task is primarily useful for expirations driven by calendar dates. However, if your deployment includes business processes that manually manage criteria for expiration (eg: expiration driven by moving a record to a different COU) you may wish to run expirations more frequently.
- forcesyncorgsources: Sync Organizational Identity Sources. Available as of Registry v3.2.0.
- groupvalidity: Reprovision records to due Group Validity. Available as of Registry v3.2.0.
- When a CO Group Member valid from or valid through date takes effect, this task is used to reprovision affected records. When executed, the task will reprovision any record associated with a CO Group Membership whose valid from or valid through date is within the last x minutes, where x is set via the CO Setting Group Validity Sync Window. The default value for this setting is 1440 minutes (or 1 day), and so typically it would make sense to run this task once per day, perhaps just after midnight. However, it may make sense to run this task more frequently, depending on how your deployment uses these dates.
- syncorgsources: Sync Organizational Identity Sources.
Monitoring
Job status maybe monitored via the web interface by CO Administrators, via the Jobs menu item. An in progress job may be canceled via the Job details view.
...