Provisioning rule
Quick answer
Provisioning rules that customise how account changes are pushed to a target system in SailPoint IdentityIQ.
Key takeaways
- Customise how a plan is applied to a target
- Scripted/manual connectors implement operations in a rule
- Translate plan operations into target-specific calls
- Return clear, retryable results for recovery
Where they fit
Provisioning rules customise how a connector carries out a provisioning plan, filling gaps where the standard connector behaviour is not enough.
Connector vs rule
Most provisioning is handled by the connector from the plan. A provisioning rule (often for scripted or manual connectors) implements the actual create, modify, enable or delete operations.
Working with the plan
The rule receives the provisioning plan and account request and translates each operation into calls the target understands, returning a result.
Error handling
Return clear results and retryable errors so the provisioning engine and workflows can report and recover correctly.
Want to learn this properly?
Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.
Check your understanding
When is a provisioning rule most needed?
- A. For every connector
- B. For scripted or gap-filling connectors
- C. Only during aggregation
- D. Only for reporting
Show answer
B. For scripted or gap-filling connectors
Provisioning rules mainly implement operations for scripted or manual connectors.