Changing Approver on Existing Approval

kshaw
Giga Guru

Trying to find out the correct procedure to change the user/approver on an existing Approval Request. In the below,example, Erica is the current approver. But she is not correct, a diffferent user needs to be choosen.

 

apprvval_list.png

 

Also (as some searches said change the approval record), the approval record is read only and controlling policy can not be found.

 

approval_request.png

Going back to the approval list, clicking on the Edit button allows a new user to be added to the approver list. 

edit_approver.png

Editing the State of the new approver from Not Yet Requested to Requested is next.

 

edit2.png

edit3.png

 

SO... the big question I have is what to do next with the original requestor. Choosing Approved or Rejected will either move the approval ahead by the wrong approver or will cause the approvel to be rejected which affects the workflow.

Of the remaining 3 choices I am not sure which to choose. I think over time I have choosen each and some just advance to workflow and the new approver (Ken Shaw in example) does not need to approve. If I leave the old approver as Requested, even if Ken approves, the approval is still waiting for Erica to approve before the workflow advances.

 

I am trying to figure out the correct steps to take to change approvers

edit 4.png

Thanks in advance for help.

Ken

11 REPLIES 11

TrevorK
Kilo Sage

When we have run into this situation for Change Request, our thought was that we want to change the approval record itself. The approval record is audited so the change to the record is captured in the history (who made Ken the approver over Erica and when they did so). Once we change the approver we flip the state to Not Yet Requested and then flip it to Requested, which retriggers the email to the new approver. 

 

We do have a custom action for this, however the reason we had a custom action was more because we have a list of approvers attached to services and we want to limit the selection to one of those approvers. In your case, if you are running into an issue of it being locked down you could just do a custom action if it's an issue. The advantage to the custom action is that it takes care of moving the state for you, our users often forgot to do this when they manually moved approvers (and occasionally clicked wrong and approved / rejected records). We thought having a nice front end where they are not modifying the list view is preferred to avoid these errors.

 

Some may say this is a bit of a hack, but I would point out that it meets the need where we are changing the approver rather than adding a new one. In terms of a process for the end user, it makes more sense from their perspective to change the approver as that is intuitive and expected. Our code can handle how to make this happen, but visually I think the user expects a changed record and not a new record plus the existing record, that can cause confusion.

 

Hopefully that helps with an idea.

Hi @TrevorK , can share a bit more about how the custom action was built? 

Our custom action is a UI Page called by a UI Action. This is using the old interface, but you could easily do this in workspace. Here is what the page looks like (the approval in this case has already been sent, hence the approvers greyed out):

TrevorK_0-1682483582586.png

We create a page that displays the pertinent change information. You'll notice the Impact field on the page. That maps to our CMDB where we have an approver for each of the different Impact levels (Minor, Significant, Major). We then limit our list of approvers to only those people at the Impact level for the change or above (so you can pick a Major approver or Significant approver for a Significant change). We use buttons to make it easier and allow our Change Managers to do the tasks like change approvers, resend the approval email, mark as no longer required (some of our changes do not have a business approver). 

 

The nice part is that this page takes care of everything for the Change Managers. When they change the approver using the button, it goes into the record and updates the approver and marks as not yet requested. Then after save it goes back and marks the approval as requested. The email then fires. Sure I could retrigger an event, do something else, etc. but I wanted to mimic their exact behaviour.

 

Happy to answer any questions.

Hi @TrevorK ,

Hope you are doing well!

We are kind of looking to implement this for one of the tables, we have 

Could you please elaborate more on this?

If possible can you please share the logic built here?

I 'm a little novice in this area, it would be of great help if you could share your views on this 

Thank you 🙂