Add a condition to check for dependencies in other business rules
D
David Kamps
I'd like the ability to create a condition in Business Rules that allows a rule to be applied only when another Business Rule has already been applied to the same person.
For example, some HR systems contain external users or interns who do not always require an account. In these cases, I can create a Business Rule for account provisioning that excludes external users. I can then create a separate Business Rule for exceptions, allowing specific external users who do require an account to be added manually.
The challenge arises when I create a rule such as "Enable Accounts". This rule attempts to run for all users, including those who will never receive an account. As a result, many users appear in Actions with a status of "Waiting".
To avoid this, I would need to create separate Business Rules for enabling accounts, assigning default rights, granting additional entitlements, and so on. This quickly increases the number of rules that need to be maintained.
It also increases administrative complexity because any changes must be replicated across multiple Business Rules.
By allowing a Business Rule to check whether a user has already been included in, or granted access through, another Business Rule, administrators could significantly reduce the number of required rules and the associated maintenance effort. This would simplify rule management, reduce administrative overhead, and prevent unnecessary pending actions for users who are not intended to receive accounts.
Niels Ballemans
Looks to be related to https://feedback.helloid.com/provisioning/p/create-set-of-entitlements-to-assign-it-to-different-rules.
Main differences what I see:
A rule having the entitlements (like account create) might be scheduled on another day. So you could create an account day(s) before enabling it.
It could also have a broader scope of users (cf. less specific conditions), so the 'mainstream' could be covered with this approach too, without another additional rule.
A 'managed set of entitlements' could solve the account creation only for those in the more specific rule. So you might add the 'exclusions' over there.
It will reduce the maintenance effort when this set changes, but does not really reduce the amount of business rules. (Probably one rule?)
So you could create an account and set other entitlements only for those needing one (in the specific rule)
Do you see other difference with both the approaches?