Before/After provisioning rule
Quick answer
Before and after provisioning rules that adjust the plan or react to results around a connector operation in IdentityIQ.
Key takeaways
- Before rule modifies the plan pre-connector
- After rule reacts to the provisioning result
- Can be global on the application or per operation
- Test carefully: they affect every request through the app
Before provisioning
A before provisioning rule runs just before the connector executes, letting you inspect and modify the provisioning plan, for example adding attributes or transforming values the target expects.
After provisioning
An after provisioning rule runs once the operation completes, letting you react to the result, trigger follow-up actions, or clean up.
Scope
These rules can be set globally on an application or targeted to specific operations, giving precise control over the provisioning path.
Cautions
Keep them focused and fast; plan changes here affect every request through that application, so test carefully.
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 does a before provisioning rule run?
- A. After the connector finishes
- B. Just before the connector executes the plan
- C. During aggregation
- D. At login
Show answer
B. Just before the connector executes the plan
The before provisioning rule runs just before the connector executes, so it can modify the plan.