Can a rule call another rule directly?

• A. Yes
• B. No
• C. Only if certain conditions are met
• D. Only in specific modules

Answer: (B)

In the context of SailPoint Identity Governance, rules are designed to encapsulate specific logic and functionality that serve identity management processes. The appropriate method for composing complex behaviors in rules is through indirect referencing – such as having one rule trigger an event that is then handled by another rule through event listeners or workflows, rather than invoking another rule directly.

Directly calling another rule could lead to complexities and challenges in managing the execution order, as well as in debugging and maintaining a clear flow of logic across rules. This design encourages a more modular and loosely coupled approach to rule creation, which aligns with best practices in software design, enhancing maintainability and scalability.

In situations where rules require interaction or shared logic, developers are encouraged to encapsulate common functionalities in reusable components or functions that can be called by multiple rules, rather than enabling direct calls between rules. This modular approach keeps the rule set organized and efficient, promoting better practices in identity governance lifecycle management.