---
sourceDocument: Xanadu Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/employee-service-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Using Universal Request in Agent Workspaces

# Using Universal Request in Agent Workspaces {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 7 minutes to read

As a Routing Agent, use the Universal Request in Agent Workspaces to view, create, edit and resolve universal
requests.  
You can start working on Universal Request in the Agent Workspaces from one of these areas:

* Landing page
* List queue
* Global search
{#use-UR-workspace__ul_zft_nwt_llb}

For additional information on working within Agent Workspace, see [Using workspace](https://www.servicenow.com/docs/access?context=using-workspace&version=xanadu&pubname=xanadu-platform-user-interface&ft:locale=en-US).

## Create a universal request in Agent Workspace {#ariaid-title2}

The Universal Request is a task that a requester creates from any of the following
sources, such as mobile application, service portal, agent workspace, or using a virtual
agent chat. As a routing 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: sn_uni_req.routing_agent or admin

### Procedure

1. Navigate to AllWorkspace ExperienceWorkspacesAgent Workspace Home.
2. From the navigation list, click Universal RequestOpen.
3. Click New.
4. On the form, fill in the fields.  
   {#create-universal-request-ws__table_un2_dyl_n3b__entry__2}

   | 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 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. By default, the state is New. |
   | 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 does not 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 | 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 is not 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. |
   [Table 1. Universal Request form]

   {#create-universal-request-ws__table_un2_dyl_n3b}

## Create a Universal Request from an Interaction Record {#ariaid-title3}

Convert an Interaction Record to a Universal Request from the Universal Request Agent Workspace.

### Before you begin

Role required: sn_uni_req.routing_agent or admin

### About this task

Consider the following scenario. An IT service desk agent with a routing agent role receives a phone call on a request and creates a new call record or an Interaction Record with the notes. After reviewing the record, the agent realizes that the request belongs to HR and not IT. In this case, the IT Agent can create a Universal Record from the interaction record and assign it to the HR assignment group.  
Note:  
Universal Request is not automatically created when a fulfiller creates a department ticket from an Interaction Record. You have to perform few manual steps to get this. For more information, see [Create universal request automatically for department tickets via other channels](https://www.servicenow.com/docs/jyGylMK7ZQytV8MNiH_E_g "Universal request is not automatically created when a fulfiller or employee creates a department ticket from channels other than the Service Portal or Virtual Agent topics. Create universal request automatically by adding the business rule to the specific service table, such as an Incident or a HR service.").

### Procedure

1. Navigate to AllWorkspace ExperienceWorkspacesAgent Workspace Home.
2. From the navigation list, click InteractionsMy Interactions.
3. Open the interaction record for which you want to create a Universal Request.
4. Click the Create UR button  
5. Click Save.

## Cancel a universal request in Agent Workspaces {#ariaid-title4}

Change the state of the universal request to Canceled to
cancel the request if the issue is resolved already or you no longer require the
request.

### Before you begin

Role required: admin

### About this task

You can cancel a universal request only if there are no active or closed primary
tickets attached to it. Also, the state of UR must be either
New or In Progress. When the UR is
canceled, email notifications are sent to the stakeholders associated with the
request.

### Procedure

1. Navigate to AllWorkspace ExperienceWorkspacesAgent Workspace Home.
2. From the navigation list, click Universal RequestOpen.
3. From the list of open universal requests, select the request you want to cancel.
4. Select Canceled from the State field.  
   Note:  
   If the person in Opened for tries to cancel the request, then they must enter the reason for canceling.
5. Click Update.
{#cancel-ur-aws__steps_nvx_vzh_spb}

## Use Agent Assist in Agent Workspace {#ariaid-title5}

Find similar Universal Requests that are open and closed, Knowledge articles, Catalog
items, and Pinned articles using the Agent Assist capability in the Agent Workspace.

### Before you begin

Role required: sn_uni_req.routing_agent or admin

### Procedure

1. Navigate to AllWorkspace ExperienceWorkspacesAgent Workspace Home.
2. From the navigation list, click Universal RequestOpen.
3. Click the universal request from the list or create a request.
4. In Agent Assist, click the settings icon (![Agent Assist settings]()) and select your resource from the list.
   * Similar Closed Universal Request: To display all similar Universal Requests that are closed.
   * Universal Request: To display all similar Universal Requests that are available.
   * Knowledge and Catalog: To display all related knowledge articles and catalog items.
   * Knowledge Articles: To display all related knowledge articles.
   * Catalog Items: To display all related catalog items.
   * Pinned articles: To display all related pinned articles.
   {#agent-assist-in-ur-aws__choices_psp_zgh_3mb}

## Transfer primary ticket in Agent Workspaces {#ariaid-title6}

You can transfer a primary ticket back to Universal Request, service set
(department), or service either with resolution or without resolution.

### Before you begin

Role required: No specific role is required. Agents part of the assignment group or assigned-to agents on the primary ticket can perform this task.

A routing agent can either resolve and close a primary ticket or
transfer it to back to UR or another department for review and closure. When a
primary task is transferred back to UR, the ticket is no longer a primary ticket and
the primary ticket field of the universal request becomes empty.

When
transferring the ticket, the routing agent can choose the department and a specific
service within the department or can just choose <kbd class="ph userinput">I'm not sure</kbd>
when they are not sure of the department or service to transfer to.  
When you transfer a ticket back to universal request, you can transfer it with one of the following reasons:

Transfer with resolution
:   The request is resolved and transferred back to UR, a specific
    department, or service. Agents can choose this option when another
    department's help is required to fulfill the request.

Transfer without resolution
:   The request is not resolved or does not belong to the specific
    department, and is transferred back to UR.

Configure the sn_uni_req.transfer_type property
in the Universal Request properties page to determine how to
handle the primary ticket transfers. For more information, see [Universal Request properties](https://www.servicenow.com/docs/dGzLKt8AE0CH_MjqDmbjRQ "Administrators can use Universal Request properties to determine and configure the application behavior.").

### Procedure

1. Navigate to AllWorkspace ExperienceWorkspacesAgent Workspace Home.
2. Open the primary task that you want to route to UR.
3. Click Transfer.
4. In the Transfer Ticket dialog, provide the following details.  
   Note:  
   Based on your transfer type configuration, the given fields are displayed. For more information, see [Universal Request properties](https://www.servicenow.com/docs/dGzLKt8AE0CH_MjqDmbjRQ "Administrators can use Universal Request properties to determine and configure the application behavior.").
   * Department: Select the department from the list.
   * Service: Select the specific service of the chosen department.
   * Transfer reason: Select the reason from the list.
   * Transfer notes: A brief description for routing the primary ticket that you want to pass to the UR Routing agent.
   * Copy additional comments and attachments: Deselect if you do not want to transfer the ticket with additional comments and attachments. By default, all attachments and comments are transferred.  
     Note:  
     Work notes are not copied while transferring.
   {#route-primary-task-aws__ul_jpg_skg_3mb}
5. Click Transfer.  
   The ticket is transferred based on the transfer and transfer type configuration. For more information, see [Transfer configuration](https://www.servicenow.com/docs/I3LKtaVBOkVa1l~bFW4nAA "You can enable agents to transfer department-specific tickets, such as an incident ticket or an HR case back to the Universal Request (UR), to another department, or service. This transfer configuration allows you to determine what happens to the departmental ticket when the request is transferred to another department or back to UR.").

## Restrict universal request access in Agent Workspace {#ariaid-title7}

Mark a universal request as restricted when you identify the request contains
sensitive information.

### Before you begin

Role required: routing agents, sn_uni_req.sensitiveinfo_agent or service specific
assignment group members

### Procedure

1. Navigate to AllWorkspace ExperienceWorkspacesAgent Workspace Home.
2. From the navigation list, click Universal RequestOpen.
3. Navigate to the universal request that you want to mark as restricted.
4. On the form, click the Restrict button.  
   The restricted fields are hidden, and the form is only for view purpose.  
   Note:  
   To mark the request as unrestricted only agents with the access role can modify.

## Mark universal request as unrestricted in Agent Workspace {#ariaid-title8}

You can unrestrict a restricted universal request if you identify that the request
does not have any sensitive information.

### Before you begin

Role required: sn_uni_req.sensitiveinfo_agent or service specific assignment group
members

### Procedure

1. Navigate to AllWorkspace ExperienceWorkspacesAgent Workspace Home.
2. From the navigation list, click Universal RequestOpen.
3. Navigate to the universal request that you want to mark as unrestricted.
4. On the form, click the Unrestrict button.  
   The hidden restricted fields are now visible, and any agent can view the content.  
   Note:  
   To mark the request as unrestricted only agents with the access role can modify.

*[\>]: and then