Is there anyway in RSA IGL to limit the number of Change Requests that will get generated by a Rule?
For Example if we have a Rule which checks the condition "whenever a New User is found" with an Action "Generate CR", Can we limit the Number of Change Requests that can potentially be generated if the Rule's Condition is satisfied?
- Access & Change Requests
- Community Thread
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
i know we can do the grouping when it comes to Access Request.
however i don't see this as something possible from a rule.
whats the reason behind grouping, why would you not want a new CR for each new joiner sorry? In my experience, having these as individual jobs helps with tracking and the overall process
I am not sure what the poster means by "limit". Do they mean split the change request up into smaller sizes and process it, or do they want some kind of circuit breaker for Rules based change requests that stops the request from being processed.
There are several suggestions on RSA Ideas to extend the scope of circuit breakers in the product past the current implementation for Collectors. Rules have not been mentioned as a candidate yet.