Originally posted on November 21 2020 at 01:35 UTC
- What was the need to trigger chain provisioning job?
- When customers have a need to provision or deprovision one application after another application in a sequential and synchronous manner
- When customers have a need to provision or deprovision an application after another job executes, then they can trigger chain multiple jobs one after another in Trigger chain job
- Existing Provisioning job (WSRetry) is multi-threaded and asynchronous, so could not be chained, but new job - WSBlockingRetry is single threaded and synchronous, so it can be chained
- How can you configure trigger chain provisioning job?
- Turn on config from Admin>Global Configuration
- Create a new job for WSBlockingRetry Job and include in Trigger Chain Job
- Can WSRetry and BlockingWSRetry Job be configured together?
No, only either WSRetry or WSBlockingRetry Job can be configured at a given point in time
- Is BlockingWSRetry single or multi-threaded?
WSBlockingRetry Provisioning job is single threaded
- Can multiple BlockingWSRetry jobs be included in Trigger Chain Job?
Yes
- When was this feature made available SSM?
This is available from 5.5.sp3.1 onwards
This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.