Assigned to / requested by person cannot approve its own Normal change request

[Pooja Khatri]

Hi All ,

I have a requirement , where the person who is an assigned to or requested by for Normal change request , the person should not be able to approve its own normal change in any level of approval process and it should show as not required for the assigned to / requested by person.

I have written an after insert update Business rule on the sysapproval_approver table , but it is allowing the user at the third level of approval to approve/reject the change request 

Script : 

Code : 

var changeRequest = new GlideRecord('change_request');

if (changeRequest.get(current.document_id)) {

    if (current.sysapproval.requested_by.sys_id == current.approver.sys_id || current.sysapproval.assigned_to.sys_id == current.approver.sys_id) {

        current.state = 'not_required';

        current.update();

    }

}

Snippet for a scenario where the assigned to person is allowed to approve/reject the change request at the third level of approval.

[Mark Manders]

Which approval step is the third level? How is that set? 

Next to that: does the 'not required' also prevents the approver from approving (can he lookup the approval record and set it to 'approved')? If that's the case, you will need some extra logic (or maybe even just delete the approval record).

[Community Alums]

Hi Pooja,

Even though you set the state to "no longer required", the approver will still be able to change the state to approve, and the flow proceeds further. I believe a notification will also be triggered to the approver.

I encountered the same use case earlier and, as a solution, we aborted the creation of the approval record using a before-insert BR. This way, we can stop the notification without changing OOTB logic.

I started answering community questions recently. If my answer helped you in any way, please mark it as helpful or correct. It would be a great boost.