Role is stuck after cancelling a change

[DannyBissett]

I Have a role where a user was added but then a decision was made before completing the request to cancel the request. The role is now stuck and no changes can be made. There is an action available to commit the role but that just recreates the request to add the user.

I checked the database and there are 12 entries in the t_av_roleversions for this role and 5 of them have the state value "C" which is where I think the issue is.

In order for this role to become action can someone advise what states all the roleversions states should be set to?

I have attached screenshot showing the current values

[wjmay]

What version are you on? We ran into a similar issue where the role got stuck in an Applied state if some items from the change request were approved and some were rejected. This is what we were able to do to get it unstuck:

A) STEPS to "Revert Changes to Roles":
A1) Go to "Roles > "Roles" > click the "Actions" button and on the drop down select "Revert Changes to Roles" to revert the Role back to the committed state.
A2) On the "Revert Changes to Roles" ensure that you have the "Role Name" selected that you want to revert and click the "Next" button.
A3) On the next screen click the radial dial for "Committed Version" and then click the "Finish" button.
A4) Now your Role should be back to the "Committed" state.

[CliveMorrish · Accepted solution]

This was resolved by turning off 'Generate Indirect Entitlements' on the Request Workflow and raising a request to remove the user from the role and applying changes.

The changes completed successfully and the role became editable again.