Old Stuck entries

[Sankar_Aravind]

Hi Team,

We are currently working on cleaning up stuck entries with status 37.

Please help on the below queries.

1) Say the stuck entry was there from 2015 onwards, so if i update the status to 2 for active users, , will it still update the old value that was in stuck state , i mean overwrite the existing vales (manually updated) with old value of the request made in 2015 ? The reason is, here it seems, they have updated the entries manually in destination (say active directory) instead of handling the stuck entries. So the status 2 should not again retrigger the old value which may create a mess.

2) is there anyway, instead of putting the status to 2, but i can put directly to 22 (Ok) to make sure no update process triggers again. Which means i want to clean stuck entries while there is no impact on existing values in destination repository. And will there be any impact doing so?

3) on the other context, is there anyway i can repush the " OK status " roles again to repositories. Its currently in Ok status but not reached to destination and we donot want to remove and reassign. Tried checking validity update or retry, but didn't retrigger. This happened for some known reason of dispatcher activity. So checking if there is any way to retrigger role assignments?

These are part of our planning from upgrading the idm from 7.2(current) to 8.0

Please advise.

Thank you,

Aravind.

[Sankar_Aravind]

These are actually QUEUED status entries in mxp_provision and wanted to update through UPDATE command.

[Sankar_Aravind]

Could you please help on this?

Thank you.

[Sankar_Aravind]

Hi Team,

Any help on this ?

Thank You.

[normann]

Hi Aravind,

1. Depending on the process. If it is a modify process, the current value that IdM knows is provisioned.

2. You can set all the related audits to state OK and delete the items from the queue if you want to avoid provisioning or you use the stored procedure to cleanup the queue (Answers: Clean Queue)

3. That depends on the type of repository. For ABAP or Java you could easily create such a job. For AD it's more complicated as the assignment provisioning is not based on the user but on the group.

Cheers

Norman