Create a Universal Request in Service Operations Workspace
As an agent, you can create universal requests from the Universal Request application on behalf of the requester to track and resolve issues.
Before you begin
Role required: itil, sn_uni_req.routing_agent, or admin
Procedure
-
Navigate to All > Workspaces > Service Operations Workspace.
-
From the navigation list, select List.
-
Navigate to Universal Request > Open.
-
Select New.
-
On the form, fill in the fields.
|
Field |
Description |
|---|---|
|
Number |
The unique number generated for the universal request. |
|
Opened |
The date and time when the universal request was created. |
|
Opened by |
The agent who created the universal request. |
|
Opened for |
The user who requested for this universal request. |
|
Primary task |
The task number, for example, an incident or HR case number that is associated with the universal request. |
|
Contact type |
The contact medium from which the universal request was created. |
|
Priority |
It identifies how quickly the service desk should address the request. |
|
State |
State of the universal request. |
|
Impact |
Impact value indicates a measure of the effect of an incident, problem, or change on business processes. |
|
Assignment group |
Group assigned to the universal request. |
|
Assigned to |
User assigned to the universal request. |
|
Needs resolution review |
When checked, and when the department agent closes the primary ticket, the Universal Request doesn’t get closed. Universal Request state remains in In Progress and the state reason changes to Confirm Response. This notifies the tier 1 agent (Routing agent) to either Accept or Reject the resolution provided in the primary ticket before closing the Universal Request for the requester. |
|
Short description |
A brief description of the request. |
|
Description |
Detailed description of the request. |
|
Notes section | |
|
Watch list |
Users to receive notifications when work notes are added. |
|
Work notes list |
Users to receive notifications when work notes are added.Note: The administrator must create an email notification for the work notes list. |
|
Additional comments (Customer visible) |
More information about the change. |
|
Work notes |
Information about how to resolve the universal request or steps taken to resolve it, if applicable. This note is for internal use. The work notes information isn’t visible to your customer. |
|
Closure Information section | |
|
Closed |
The date and time when the universal request was closed. |
|
Closed by |
The agent that closed the request. |
|
Close notes |
How or why the universal request was closed. |
Parent Topic:Universal Request in Service Operations Workspace
--- title: Create a Universal Request in Service Operations Workspace description: As an agent, you can create universal requests from the Universal Request application on behalf of the requester to track and resolve issues. locale: en-US canonical_url: https://www.servicenow.com/docs/r/it-service-management/service-operations-workspace/create-ur-sow.html release: brazil product: Service Operations Workspace classification: service-operations-workspace topic_type: task last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Universal Request in Service Operations Workspace, Managing IT services in your organization, Service Operations Workspace for ITSM, IT Service Management] --- # Create a Universal Request in Service Operations Workspace As an agent, you can create universal requests from the Universal Request application on behalf of the requester to track and resolve issues. ## Before you begin Role required: itil, sn\_uni\_req.routing\_agent, or admin ## Procedure 1. Navigate to **All** > **Workspaces** > **Service Operations Workspace**. 2. From the navigation list, select **List**. 3. Navigate to **Universal Request** > **Open**. 4. Select **New**. 5. On the form, fill in the fields. <table id="table_un2_dyl_n3b"><thead><tr><th> Field </th><th> Description </th></tr></thead><tbody><tr><td> Number </td><td> The unique number generated for the universal request. </td></tr><tr><td> Opened </td><td> The date and time when the universal request was created. </td></tr><tr><td> Opened by </td><td> The agent who created the universal request. </td></tr><tr><td> Opened for </td><td> The user who requested for this universal request. </td></tr><tr><td> Primary task </td><td> The task number, for example, an incident or HR case number that is associated with the universal request. </td></tr><tr><td> Contact type </td><td> The contact medium from which the universal request was created. </td></tr><tr><td> Priority </td><td> It identifies how quickly the service desk should address the request. </td></tr><tr><td> State </td><td> State of the universal request. </td></tr><tr><td> Impact </td><td> Impact value indicates a measure of the effect of an incident, problem, or change on business processes. </td></tr><tr><td> Assignment group </td><td> Group assigned to the universal request. </td></tr><tr><td> Assigned to </td><td> User assigned to the universal request. </td></tr><tr><td> Needs resolution review </td><td> When checked, and when the department agent closes the primary ticket, the Universal Request doesn’t get closed. Universal Request state remains in **In Progress** and the state reason changes to **Confirm Response**. This notifies the tier 1 agent \(Routing agent\) to either Accept or Reject the resolution provided in the primary ticket before closing the Universal Request for the requester. </td></tr><tr><td> Short description </td><td> A brief description of the request. </td></tr><tr><td> Description </td><td> Detailed description of the request. </td></tr><tr><td class="sub-head" colspan="2"> Notes section </td></tr><tr><td> Watch list </td><td> Users to receive notifications when work notes are added. </td></tr><tr><td> Work notes list </td><td> Users to receive notifications when work notes are added.**Note:** The administrator must create an email notification for the work notes list. </td></tr><tr><td> Additional comments \(Customer visible\) </td><td> More information about the change. </td></tr><tr><td> Work notes </td><td> Information about how to resolve the universal request or steps taken to resolve it, if applicable. This note is for internal use. The work notes information isn’t visible to your customer. </td></tr><tr><td class="sub-head" colspan="2"> Closure Information section </td></tr><tr><td> Closed </td><td> The date and time when the universal request was closed. </td></tr><tr><td> Closed by </td><td> The agent that closed the request. </td></tr><tr><td> Close notes </td><td> How or why the universal request was closed. </td></tr></tbody> </table>6. Select **Submit**. **Parent Topic:**[Universal Request in Service Operations Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-service-management/service-operations-workspace/using-ur-sow.md)
| title | Create a Universal Request in Service Operations Workspace |
| description | As an agent, you can create universal requests from the Universal Request application on behalf of the requester to track and resolve issues. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/it-service-management/service-operations-workspace/create-ur-sow.html |
| release | brazil |
| product | Service Operations Workspace |
| classification | service-operations-workspace |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | Universal Request in Service Operations WorkspaceManaging IT services in your organizationService Operations Workspace for ITSMIT Service Management |