This forum has helped me lot times so thought to reach out once again for an identityiq issue after trying few possibilities
Problem
When Access Request is getting failed while throwing an exception from beforeprovisioning rule, A sticky entitlement as well as attribute assignment is being occurring on identity. To remove this the flow is not even going till afterprovisioning rule where we can remove the attribute assignment
Sticky entitlement is getting removed on perform identity request main task but attribute assignment is causing many problems - throwing create provisioning form again in workitems for reprovisioning.
Do you have a partial provisioning in this case? Is the failure in before provisioning rule handled with catch blocks or did you throw an exception inside the catch block in case of an error?
In my case, we did throw an exception after handling it from the catch block, it didn’t result in any sticky entitlements and attributeAssignments. Can you provide more details of your case and the connector in this case.
Yes we were trying to throw an exception from before provisioning rule where exactly it was occuring.
As a solution, instead of throwing an exception we’re setting a provisioning result in after provisioning rule with an error message that’ss been identified in before rule.
@Shivaleela If I understand correctly, IQ is behaving as expected; however, can you explain more about the use case? Are you provisioning the business role or entitlement?.
