The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Submit Resource Assignment for Review

Peter Grabovszk
Tera Contributor

3 weeks ago

Currently in progress of switching to Next Experience Resource Management from the legacy one with my client. The official ServiceNow Resource Management process guide (Yokohama release) states the following:

 

Process step RSM 1.7: Submit Resource Assignment for Review

"Following the finalization of the resource assignment, submit the assignment to the applicable resource manager of the resource(s) being requested. Once requested, the resource assignment is locked for editing by the resource requester."

 

I've been trying to validate the above process step with a test user having it_project_manager role, but could not achieve the described behavior. There isn't any UI action that would trigger  a "submission" of any kind, and setting the "Ready for review" field to "Yes" does not change anything on the resource assignment record, nor on who can or cannot modify it.

 

Am I missing something, or the process guide is incorrect? Or maybe this is a functionality that is planned to be released in the future? This is important for us to understand in order to decide whether to invest time and effort into a custom solution that would make the product work as described.

 

Thank you for your response in advance.

Labels:
0 Helpfuls
  • 501 Views
1 REPLY 1

M Iftikhar
Mega Sage

2 weeks ago

Hi @Peter Grabovszk 

You can test the “Submit Resource Assignment for Review” behavior like this: 

Impersonate with a Project Manager (resource requester) 

  • Needs roles: it_project_manager , resource_user. 
  • Can create the resource assignment. 
  • Once they submit the resource assignment via submit button, they should no longer be able to make changes to it. At that point, the record is locked from editing by the requester. 

(New Resource Assignment form-fields description) 

MIftikhar_0-1757515677830.png 

MIftikhar_1-1757515677835.png

 
Impersonate Resource Manager 

(View, allocate, and approve unassigned work using Resource Management Workspace) 

  • Needs role: resource_manager. 
  • Only the resource manager can then take the next action, reviewing and updating the status of the resource assignment (e.g., Approve, Unapprove, etc.). 

MIftikhar_2-1757515677836.png

 

 

If you’re not seeing that locking behavior in your test, it might be: 

  • Role configuration (ensure your test user has both it_project_manager and resource_user). 
  • Instance not updated with the latest Next Experience changes  

So the process guide isn’t incorrect, you just need to understand how the functionality ties to the specific roles. 

Thanks & Regards, 
Muhammad Iftikhar 
 
If my response helped, please mark it as the accepted solution so others can benefit as well. 

0 Helpfuls