Rule types overview
Quick answer
The main SailPoint IdentityIQ rule types, when each runs, and how to choose the right rule for the job.
Key takeaways
- Rules are reusable BeanShell stored as Rule objects
- Each rule type runs at a fixed extension point with fixed inputs
- Know BuildMap, Transformation, Correlation, Provisioning, Field Value
- Pick a rule by when it runs and what it returns
What a rule is
A rule is a reusable snippet of BeanShell (Java-like) script stored as a Rule object. IdentityIQ calls rules at defined extension points during aggregation, correlation, provisioning and refresh.
Why rule type matters
Each rule type runs at a specific point with a specific set of input variables and an expected return value. Using the wrong type means the inputs you need are not in scope.
Common rule types
BuildMap, Transformation, Correlation, Creation, Provisioning, Field Value, Before/After Provisioning, Listener and Task rules cover the bulk of real projects.
Choosing a rule
Ask when it must run and what it must return. Attribute shaping during read is a Transformation or BuildMap; matching accounts to identities is Correlation; changing a plan is Before Provisioning.
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
What determines the inputs available to a rule?
- A. The connector
- B. The rule type
- C. The identity
- D. The UI
Show answer
B. The rule type
Each rule type runs at a specific extension point with a defined set of inputs.