I added a new method inside an existing Rule Library method (fetchJoinerApps).
The new method internally uses two additional rule libraries, which means fetchJoinerApps now requires two new rule references.
Since fetchJoinerApps is already being used (directly or indirectly) in around 20 other rules, SailPoint is now expecting those rules to also include references to these two newly introduced rules.
This creates a dependency chain problem:
Any time I update a rule library method to include new rule references, all upstream rules that call it must also be updated.
I want to know if there is any clean way to avoid updating all upstream rules whenever I add new rule references inside a Rule Library method, or if there’s a recommended best practice for handling this kind of rule dependency propagation in IIQ.