Approving a RITM after manually assigning approver requires reopening the record multiple times

[DanielR41508060]

Hello Community,

I am validating approval workflows in ServiceNow (Zurich)  and noticed a user experience that seems inefficient when a Request Item (RITM) requires a manually assigned approver.

In our current temporary process, the approver is not automatically populated. The fulfiller must:

1. Open the RITM.
2. Manually set the approver.
3. Click Update.
4. The system returns to the previous list/view.
5. Reopen the RITM.
6. Navigate to the approval task and complete any required fulfilment activity.
7. After updating the task, the system again returns to the previous list/view.
8. Reopen the RITM a third time.
9. Navigate to the approval record and approve it.

As a result, a single approval may require opening the same RITM multiple times because each update redirects the user away from the request.

My questions are:

• Is this the expected out-of-box behavior?
• Are there standard UI configurations that allow the user to remain on the record after updating?
• Are there recommended approaches to streamline this workflow when approvers are assigned manually?
• Has anyone implemented a more efficient method while staying close to OOTB functionality?

I am primarily interested in understanding whether this is the standard ServiceNow experience or whether common configuration options exist to reduce the number of record reopenings required.

Thank you.

[brianlan25]

Update always returns you to the previous screen. If they click Save which can be found in the context menu it will keep them on the current record.