Share all details related to your problem, including any error messages you may have received.
Here’s the scenario:
John Doe currently has an F3 Exchange License assigned but needs an E5 Exchange License.
He put the request through IdentityIQ.
Currently, we don’t have any process to remove the F3 license from the user. As a result, they can’t operate if they have both licenses assigned.
What we are looking for is whether there’s a way to automatically remove the F3 Exchange License entitlement before assigning the E5 License to the user through this access request.
@pbobadil If you are looking for solution for two specific entitlements only (like as in your example - F3 Exchange License and E5 Exchange License) then a 'Entitlement SOD Policy works in this case.
But yes, provide more details of your condition to get more answers.
If it is only for this use-case (Remove F3 as E5 is requested and vise versa), I would go for a before provisioning rule. The before provisioning rule can check if the account has a F3 assigned and add the removal of the entitlement directly to the plan (if needed also a role de-assignment).
In one of our project we want to automate this functionality on a greater scale and we will create a custom QuickLink to have the requestor select the license/profile/approval-limit from a list build out of a Custom Object and do the magic in the workflow
