Hi,
We are planning to on-board a new business B (which uses different HR source and different AD/Exchange domains) into L&G. The existing business A in L&G, uses an attribute change rule (which triggers when new users are detected) to trigger WF's for provisioning default birthright access.
If we on-board the new business, the above rule will get triggered (for business A) even if a new user on-boards in the new business B (and vice versa if the same config is applied for the new business). One way to stop this doing any provisioning is to filter it out in the WF, but still it would trigger an unwanted change request.
What would be the best way to sort this out.?
I assume you are using "When new users are detected" option.
You are limited with that design.
You might get away with changing the WF, but it might get out of hand when there will be new business C,D,E...
A more flexible approach might be to use roles to grant default birthright access