---
sourceDocument: Brazil ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform
Release :
- brazil
ft:locale :
- en-US
ft:publication_title :
- Brazil ServiceNow AI Platform Capabilities
ft:clusterId :
- platcap
bundleId :
- platcap
workflow :
- Platform
---
# Delegated request experience
# Delegated request experience {#ariaid-title1}
Release version: Brazil
Updated September 10, 2026
 7 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Delegated request experience
The Delegated Request Experience in ServiceNow allows users to submit catalog item requests on behalf of other users or multiple users by utilizing theRequested Forvariable.
This feature enhances flexibility in managing service catalog requests, enabling delegation and multi-user submissions primarily through the Service Portal.
Show full answer Show less
## Key Features
* **Requested For Variable and Field:** The Requested For variable on catalog items lets requesters specify who the request is for. This value is copied to a Requested For field on the requested item (RITM) record, which may require configuration if not present.
* **Access Type Configuration:** Controls whether requests can be submitted on behalf of users who lack access to specific catalog items. Access types include *Restricted* and *Delegated*, affecting item availability in order guides.
* **Multiple Users Request:** The Requested For variable can be configured to enable requests for multiple users simultaneously by activating the "Enable also request for" option and specifying allowed roles. Separate RITMs are created per user, but a single request tracks them all.
* **Service Portal Support:** Delegated requests and multi-user requests are supported in Service Portal but not in Now Mobile or Workspace. Some UI elements like wish lists and cart do not show the "Also request for" field.
* **Order Guides and Record Producers:** Delegated requests are supported in order guides only when all items include the Requested For variable, and access permissions align. For record producers, the Requested For variable maps to a target record field as configured.
* **Request Cloning:** When cloning requests, the Requested For values are updated to the new user's context. Cloning requires all RITMs to be for the same user and access permissions must be met.
* **Cart Behavior:** The cart supports adding multiple items for different users and submitting them as a single request, generating individual RITMs with appropriate Requested For values. Behavior varies depending on which items have the Requested For variable and their associated users.
* **Parameter Passing:** Default Requested For values can be set programmatically via URL parameters in the platform or widget instance options in Service Portal, facilitating pre-population of the Requested For field.
## Practical Considerations for ServiceNow Customers
* Ensure the Requested For field is configured on RITM forms to properly capture delegation data.
* Review and configure Access Type settings on catalog items to control delegated request permissions effectively.
* Use the multi-user request feature in scenarios where a requester needs to submit identical requests for multiple users, noting that this is only available in Service Portal.
* Be aware that two-step checkout disables delegated request functionality.
* Customize the default roles allowed to submit delegated requests using system properties to match your organizational policies.
* Understand how the Requested For variable cascades in order guides and impacts item inclusion based on user permissions.
* Use URL parameters or widget instance options to streamline the request process by setting default Requested For values where applicable.
## Expected Outcomes
By leveraging the Delegated Request Experience, ServiceNow customers can:
* Improve request management by enabling users to submit requests on behalf of others efficiently.
* Support bulk request scenarios with a simplified user interface and backend processing that creates multiple RITMs under a single request.
* Maintain clear tracking of who a request is for, improving fulfillment accuracy and auditability.
* Ensure order guides and record producers respect delegated access and Requested For configurations, maintaining security and request validity.
* Enable flexible and user-friendly catalog interactions in Service Portal, enhancing user satisfaction and operational efficiency.
You can request a catalog item on behalf of another user or multiple users using the
Requested For variable.
Delegated request experience comprises of the following entities:
* Requested For variable for a catalog item. For information about this variable, see [Requested For](https://www.servicenow.com/docs/Ck6RVxW~js9Z8D4I3ITvGw#requested-for__RequestedFor).
* Requested For field on a requested item (RITM)
Note:
The form views, list views, and email notifications are not updated to reflect the Requested For field on a RITM.
{#delegated-request-exp__ul_gnd_nzh_hmb}
## Configuration options {#delegated-request-exp__section_mdv_4l1_hmb}
The following configuration options are available:
* Specify who you want to submit the request for using the Requested For variable. You can also map the Requested For variable to a field on the table for record producers.
* If required, configure the Requested For field on the RITM form. This field automatically stores the value of the Requested For variable.
* Allow delegated requests for a catalog item using its Access Type field, where you can specify if a request can be submitted for a user who does not have access to the catalog item.
* Submit a single request for an item on behalf of multiple users in Service Portal
{#delegated-request-exp__ul_odx_bxx_qlb}
Important:
If two-step checkout is enabled, the delegated request experience is not supported.
## Request Management {#delegated-request-exp__section_wqs_ql1_hmb}
After you submit a catalog item request, the Requested For variable value is copied to the Requested For field of the RITM. In case this field is not available on the RITM form, you should configure it.
Note:
After you submit a catalog item, the Requested For field value is not automatically updated when the Requested For variable is modified, and vice versa.
In Service Portal,
* If RITMs have different Requested For users, the following information is displayed in the order status page.
* The Requested For column to display the RITM's Requested For user.
* When the user viewing the Order Status page is not the user who submitted the request, the Requestor information to display the request's Requested For user. This is also applicable in Now Mobile, when the user viewing the RITM is not the user who requested it.
{#delegated-request-exp__ul_exp_2jh_3mb}
* If the RITM's Requested For user is different from the request's (REQ) Requested For user, My Requests menu displays the RITM records to the user who the RITM is being requested for. If the RITM Requested for is the same as the REQ requested for user, My Requests menu displays REQs.
* When you create a bundle from the cart by adding a catalog item with a Requested For variable, the item preserves the variable value. When you later add it to the cart to request for another user, you should edit the Requested For variable value as required.
{#delegated-request-exp__ul_qjk_x3h_3mb}
## Request experience for a record producer {#delegated-request-exp__section_bkh_k3b_hmb}
After you submit a record producer, the Requested For variable value is copied to the target
record's field based on the Map To Field configuration.
## Request experience for an order guide {#delegated-request-exp__section_zkn_j3b_hmb}
This experience is supported in an order guide only if the following conditions are met:
* Order guide has a Requested For variable
* All items in the order guide have a Requested For variable
{#delegated-request-exp__ul_tn3_vjb_hmb}
A catalog item is included in an order guide based on the Requested For user's access to a catalog item.
* When the user has no access to the catalog item and its Access Type is set as Restricted, that item is not included in the order guide.
* When the user has no access to the catalog item and its Access Type is set as Delegated, that item is included in the order guide.
{#delegated-request-exp__ul_llz_zb3_hmb}
The Requested For variable value from the Describe Needs section is always cascaded to the Requested For variable of catalog items in rule bases.
* The cascading of the Requested For variable value depends just on the variable type, but not the variable name.
* The Requested For variable value is cascaded even when the Cascade Variables check box is not selected for the order guide.
* The Requested For variables in the included catalog item cannot be edited.
{#delegated-request-exp__ul_nyd_xl1_hmb}
## Submitting a catalog item request for multiple users {#delegated-request-exp__section_bcn_rm1_hmb}
To support submitting a request for multiple users, you can configure the Requested For variable of a catalog item.
1. From the Type Specifications tab, select the Enable also request for check box.
2. Specify the roles in the Roles to use also request for field that can submit a catalog item request for multiple users. If no role is specified, anyone who has access to the catalog item can submit the request.
{#delegated-request-exp__ol_qjc_t3j_hmb}
After you configure the Requested For variable of a catalog item, the Also request for field is displayed for that item in Service Portal. After you specify multiple users in this field, you can:
* Add the item to the cart
* Separate cart items are created for each user specified in the Also request for field.
* The Requested For variable of each cart item is populated with the corresponding user.
{#delegated-request-exp__ul_a4v_y3j_hmb}
* Submit the request
* A single request is created and assigned to the current logged-in user requesting the item
* Separate RITMs are created, one for each user specified in the Enable also request for field and the Requested For variable.
{#delegated-request-exp__ul_cty_z3j_hmb}
{#delegated-request-exp__ul_vw1_y3j_hmb}
Note:
* This experience is available in Service Portal.
* This experience is not available in Now Mobile and Workspace.
* This experience is not available for a record producer and order guide.
* The Also request for field is not displayed in the wish list and cart.
* Catalog client scripts, catalog UI policies, and g_form() APIs are not applicable for the Also request for field.
* The Also request for field is displayed only if the Requested For variable is editable. For example, the field is not displayed if the requesting user has no write permissions for the Requested For variable, or if the variable is made read-only via catalog client scripts.
* You can add up to a maximum of 50 users in the Also request for field.
* If any of the users does not have access to a catalog item with Access Level set as Restricted, then the item cannot be added to cart.
{#delegated-request-exp__ul_jts_wn1_hmb}
## Request cloning {#delegated-request-exp__section_rdz_lth_hmb}
When you clone a request:
* The Requested For value for the cloned request is updated with the user for whom the request is being cloned.
* The Requested For value for cloned RITMs (with or without a Requested For variable) is updated with the user for whom the request is being cloned for the following entities:
* RITM Requested For user
* Requested For variable value
{#delegated-request-exp__ul_ixv_whh_3mb}
{#delegated-request-exp__ul_o5q_g3h_3mb}
For information about cloning requests, see [Create up to ten copies of Service Catalog request](https://www.servicenow.com/docs/VBOz_CJ9vegF6ddF~ohl1w "Clone a request to create up to ten copies (clones) of the same Service Catalog request, for different users, without having to enter the same information multiple times. For example, you can request a new piece of equipment for several specified people, generating multiple individual requests quickly from a single initial request.").
Important:
* You can clone a request only when all RITMs are requested for the same user.
* You cannot clone a request for a user who does not have access (based on Access Type) to any item in the request.
* Variable dependencies on the Requested For variable are not considered when a request is cloned.
{#delegated-request-exp__ul_w2h_qth_hmb}
## Cart behavior {#delegated-request-exp__section_tqd_f41_hmb}
Using the Requested For variable, you can add multiple catalog items to the cart for different
users and submit the cart as one request. When you submit a request for a cart with multiple
items, a single request is created with separate RITMs, one for each catalog item. In this
case, the Requested for field of each RITM inherits the corresponding
Requested For variable value.
When you add multiple items to the cart for different users and submit the request, a single
request is created with a separate RITM for each catalog item with the corresponding Requested
For user.
{#delegated-request-exp__table_vxg_q41_hmb__entry__2}
| Scenario | Cart behavior |
|-|-|
| All items in the cart have a Requested For variable and are requested for the same user | * Requested For value of the RITM is the Requested For variable value. * Requested For value of the request is the Requested For variable value. {#delegated-request-exp__ul_whw_1p1_hmb} |
| All items in the cart have a Requested For variable and are requested for different users | * Requested For value of the RITM is the Requested For variable value. * Requested For value of the request is the logged-in user or the default Requested For user specified in the cart. {#delegated-request-exp__ul_qcq_cp1_hmb} |
| No items in the cart have a Requested For variable | * Requested For value of the RITM is the default Requested For user specified in the cart. * Requested For value of the request is the logged-in user or the default Requested For user specified in the cart. {#delegated-request-exp__ul_rtm_sp1_hmb} |
| Few items in the cart have a Requested for Variable while others do not | * Requested For value of the RITM is one of the following: * If a Requested For variable exists, it is the variable value. * If no Requested For variable value exists, it is the logged-in user or the default Requested For user specified in the cart {#delegated-request-exp__ul_wjb_2q1_hmb} * Requested For value of the request is the logged-in user or the default Requested For user specified in the cart. {#delegated-request-exp__ul_rny_xp1_hmb} |
[Table 1. Cart submission scenarios]
{#delegated-request-exp__table_vxg_q41_hmb}
## Passing parameters for the Requested For variable {#delegated-request-exp__section_bgt_jwh_hmb}
You can use parameters in ServiceNow AI Platform and Service Portal to specify the default Requested For variable value for a catalog item.
* In Platform, pass a user's sys_id as the sysparm_requested_for value in the URL.
* In Service Portal, specify the requested_for_id and requested_for_display parameters in widget instance options.
For example, navigate to a catalog item widget, press Ctrl+click to select Instance in Page Editor, and specify the following parameters in the Additional options, JSON format field.
"requested_for_id": "a8f98bb0eb32010045e1a5115206fe3a
"requested_for_display": "Abraham Lincoln"
{#delegated-request-exp__ul_img_yxh_hmb}
Note:
The Requested For value is set after the catalog form is loaded.
* **[Configure the default behavior to request items for other users](https://www.servicenow.com/docs/BoquD3v1hmVdHO~mirPxzg)**
Define the default behavior when no roles are specified in the glide.sc.req_for.roles property.
**Related reference**
* [Types of service catalog variables](https://www.servicenow.com/docs/mcb3fGuhg89dXpW5UDt7mQ "Variables allow you to specify questions for a catalog item. Several types of service catalog variables are provided. Some variable types accept variable attributes.")