Preventing Delegate Approval for Specific Request

[Nathan Stevic]

I have a use case for a specific request that needs to have only the listed approver to be able to approve. For compliance reasons, we cannot have a delegate approve for this one request. All other requests in the environment are permitted to have delegate approval. Is there a way to achieve this?

[Romario DPO]

Nathan, in this case you could create a group to approve the desired demand and configure redirection to the group when the type of request in question is opened.
Then just insert the person into the group and every time something is opened that only that group can approve, they will be notified so they can approve it.

At least that's more or less what I understood from your question.
But if that's not the case, could you explain it better so I can try to help you.

[Nathan Stevic]

Ill try to provide more specific details as the form requires a total of 4 approvals. The approvers entered on the form can vary from submission to submission, but only the exact combination listed on that exact request can be the approver. One of the 4 approvers will remain static regardless of who submits. 

- User enters the request. There is a field on this request where they enter their Firm Manager (one of the approvers). We allow manual entry instead of lookup as sometimes there is a specific Manager that needs to be used based on availability. 

- Request comes to our team to review for accuracy. Based on the user's office number, we look up and enter the next two approvers (both are regional and can vary) based on who is on the list at that particular time for the agency. 

- We close the request and it goes to the first three approvers, Firm Manager and the two regional ones. 

- Once those three approvals are completed, it goes to the 4th and final static approver. 

I'm not sure if a group will work, as we do not want other regions to be able to approve. Also, the SN team at our company does not have the time to create and maintain this group. It has to be the exact 3 that are manually entered, plus the one static. 

[Romario DPO]

What I would do in this case then would be to control the request stages with approvals.
I have something like this configured in a service catalog that works as follows:

The user opens a request on the portal that generates a rhythm.
This rhythm, when approved, generates a task that only a specific person approves.
After approval
The task is closed and generates another task that is passed on to 2 other people to approve.
After these are analyzed and approved.
Generates a third task directed to a director (in this case you can choose another hierarchy).
Oh, this director approves.
Generates a final task containing process steps for a specific sector.
Thus passing through the levels of approvals I desire.
I don't know if this meets what you need, but maybe it's a way:

EX:
User OPEN REQ IN Portal

Of course, for your purpose, this process can be improved if it meets your needs.
I believe this can also be done via script.
There are other ways to control the approval flow. It is interesting to consult the official documentation.
I hope I helped and I'm at your disposal for anything.

[Jaspal Singh]

Hi Nathan,

Why not create a BR on the Approval table that will performs all checks to see if the delegated person is approving or the actual approver and accordingly allow approval/rejection processing.