Hello All,
We have a Leavers Rule in RSA which on satisfying a specific Condition, Disables the AD Account for a User.
Is there any way in RSA to limit the number of Disablement that may potentially happen because of the Rule.
Hello All,
We have a Leavers Rule in RSA which on satisfying a specific Condition, Disables the AD Account for a User.
Is there any way in RSA to limit the number of Disablement that may potentially happen because of the Rule.
To answer your question, there isn't anyway you can limit the number of changes generated from a Rule run. It only depends on the rule configuration and the amount of changed data since the last rule run. So maybe if you schedule your rules weekly, consider switching to daily to have a less bulk changes on the same day?
Could you give us more insight into why you want to limit the number of changes generated from a Rule?
Hey Mostafa,
The Goal of the Ask is,
The Leaver Rule currently checks for a particular Condition from our Source of Truth and Generates CR as its action which disables the AD Account immediately.
If by any chance, certain discrepancies are in the Source of Truth Data, and our Rule Condition gets satisfied and it raises thousands of Change Requests to Disable the AD Account, can we somehow prevent or limit our CR's from processing so that we do not disable thousands of accounts because of a small data disparity.
Kindly check out this question for more context : https://community.rsa.com/thread/204350
In that case, I believe you should be looking into using a different value for Circuit Breaker in your collectors to stop such changes that may be caused by bad source data.
There are also many suggestions on the RSA Ideas page to include additional circuit breaker types for other activities besides collections.
For example:
Circuit Breaker for Outbound Changes
For a complete list of suggestions search RSA Ideas for the work "circuit".
https://community.rsa.com/search.jspa?q=circuit&place=%2Fplaces%2F154960&depth=ALL
Hey Thanks Ian, The Idea proposed is exactly what i was looking for. Hope to see RSA releasing such a feature to proactively limit such huge number of CR's getting processed.
There are also many suggestions on the RSA Ideas page to include additional circuit breaker types for other activities besides collections.
For example:
Circuit Breaker for Outbound Changes
For a complete list of suggestions search RSA Ideas for the work "circuit".
https://community.rsa.com/search.jspa?q=circuit&place=%2Fplaces%2F154960&depth=ALL