Force remove entitlements ordered in IT Shop when create attestation instance

Person requests are stored in the table called PersonWantsOrg.  Once you have the uid_person of the Person from AttestationCase table then go to the PersonWantsOrg and find / process their requests.

Hi, Paul I did it. But I have error like this: [810033] PersonWantsOrg: You do not have delete permission for this object (IAM-tOI_PRBRPB - Smolof, Petr  - 3/6/2019 6:19:48 PM).

Hi, Paul I did it. But I have error like this: [810033] PersonWantsOrg: You do not have delete permission for this object (IAM-tOI_PRBRPB - Smolof, Petr  - 3/6/2019 6:19:48 PM).

You may want to take a look at the ootb process that removes entitlements or business role assignments, even when requested.

By the way, are you talking about aborting everything a person has requested before the attestation case has been denied? 

Hello Markus.

 Yes, I need to aborting everything a person has requested before the attestation case has been denied.

Can you explain what's the business case behind this? Otherwise, removing the Person from the customer's nodes in the shop should be the easiest thing to do.

When an employee comes to the certification to the head. I need that the Manager should not see any entitlements from the employee that he requested himself.

And because of that, you are trying to remove all entitlements? And if the certification is working through and the user is approved he has to re-request the additional entitlements? Is that what you are saying?

If the certification is working through and the user is approved,  he will be certified and thats all. And we forgot about his additional entitlements. He should be clean, like a new person.

Oh boy. If that is the case, then aborting the requests it is. Just remember that the script only works if it is run by the job service as you normally (means not everybody) do not have the permission to abort the requests. That's the reason for the error message.

I did it. I use custom block in my process.

Have you give a try to use "Unsubscribe" method instead "Abort"? For an unsubscribe process, you may use auto approval or a single CM workflow for it.