---
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


---

# Service Catalog variable editors

# Service Catalog variable editors {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Service Catalog variable editors

Service Catalog variable editors in ServiceNow enable display and interaction with variable values collected from requesters during catalog item requests or record producer submissions.
These editors appear on fulfiller forms such as requested item (RITM) and catalog task forms, providing visibility and potential edit capabilities for fulfillers handling the requests.
Show full answer Show less  

## Types of Variable Editors

* **VEditor:** Used exclusively for catalog item requests on RITM and catalog task forms. It displays variable values from the Options \[scitemoption\] table. It supports catalog UI policies and client scripts targeted to requested items and catalog tasks. It cannot be used on other tables.
* **Default Variable Editor:** Applicable only for records generated by record producers on task-extended tables such as Incident and Change. It displays variable values from the Question Answer \[questionanswer\] table. Supports catalog UI policies, client scripts, data lookups, and reference qualifiers for task-extended tables.

## Variable Editor in Different Interfaces

* **Agent Workspace:** Automatically adds the variable editor to the Variables section if the formatter is available in the Workspace view. Some variable types (Macro, Macro with Label, UI Pages) are not displayed, while Multiple Choice, Numeric Scale, Lookup, and Multiple Choice variables appear as select boxes.
* **Service Portal:** Variable editor is available on forms configured with the variable editor formatter. Since Service Portal is requester-focused, it is recommended to use Agent Workspace for variable editors. For read-only editors, a configuration option can be set in the portal's Quick start config.

## Making Variable Editors Read-Only

* In ServiceNow AI Platform and Agent Workspace, use the GlideForm setVariablesReadOnly() method to make variable editors read-only on requested items, target records, and catalog tasks.
* In Service Portal, set the "readonlyvariableeditor": "true" flag in the portal configuration to make the variable editor read-only. Note that UI Page and Macro variables still render even in read-only mode.

## Important Considerations

* Do not activate the Variables column on the Task \[task\] table, as the variable editors depend on it being inactive.
* Avoid adding business rules to internal tables such as Options \[scitemoption\] and Question Answer \[questionanswer\], as these store the variable values.
* Configure catalog UI policies and client scripts appropriately by selecting the correct "Applies on" checkboxes depending on the editor (Requested Items, Catalog Tasks, or Target Record).
* The default variable editor can be configured for other task-extended tables beyond Incident and Change to support record producers.

## Practical Benefits for ServiceNow Customers

These variable editors enable fulfillers to view and interact with the variables submitted by requesters directly within their task forms, streamlining fulfillment processes and ensuring accurate data handling. Understanding when and how to configure and control these editors allows customers to tailor the fulfillment experience, enforce read-only conditions when needed, and support automation or UI policies effectively.  
Variable editor displays variable values in fulfiller forms. A requester, while
requesting the item, specifies these variable values in the catalog item questions.

Types of variable editors based on the catalog item type:

* For a catalog item, the VEditor (com.glideapp.servicecatalog.VEditor) displays the values of questions in the requested item and catalog task forms.
* For a record producer, the default variable editor (com.glideapp.questionset.DefaultQuestionEditor) displays the values of questions for records generated from a record producer for task-extended tables.

{#service-catalog-variable-editor__ul_ggr_ktq_zz}  
Warning:  
The variable editor depends on the Variables column of the Task \[task\] table. By default, this column is inactive, and you should not make it active.

## VEditor {#service-catalog-variable-editor__cat-VEditor}

The VEditor is applicable only for the requests created from catalog items.

In ServiceNow AI Platform, this editor is a formatter added on the requested item (RITM) form
(Default View) and the catalog task form (Default View).

The VEditor is applicable only for RITMs and catalog tasks. It cannot be used for any other
tables. To support catalog UI policies or catalog client scripts on the VEditor for the RITM and
catalog task form, select the Applies on Requested Items and
Applies on Catalog Tasks check boxes for the catalog UI policy or the
catalog client script.  
Note:  
The values in the VEditor are displayed from the Options \[sc_item_option\] table. This is an internal table and you should not add any business rules to this table.  
To make the VEditor read-only in ServiceNow AI Platform, activate the onLoad client script, Variable Editor Readonly, for the following tables:

* Requested Item \[sc_req_item\]
* Catalog Task \[sc_task\]
{#service-catalog-variable-editor__ul_ejt_sfd_gbb}  
Note:  
You can make the Variable Editor Readonly scripts conditional, by adding conditions to them.  
Figure 1. VEditor

## Default variable editor {#service-catalog-variable-editor__cat-default-variable-editor}

The default variable editor is applicable only for record producers. This editor is a
formatter added on records that are generated by a record producer for task-extended tables.
This editor displays the values of questions specified in the record producer.

By default, this editor is applicable for the Incident and Change tables. For other tables,
you can [configure this editor](https://www.servicenow.com/docs/djydUc31AprsGLzBM1QOSw "After you configure the default variable editor for a task-extended table, you can view and edit the values of questions specified by the requester in the record producer. Applicable only for records generated by a record producer.").  
Catalog UI policies, catalog client scripts, catalog data lookups, reference qualifiers, and dependent reference fields are supported on the default variable editor only for task-extended tables. To support a catalog UI policy or a catalog client script on this editor, select the Applies on the Target Record check box for the catalog UI policy or the catalog client script.  
Note:  
The values in the default variable editor are displayed in the Question Answer \[question_answer\] table. This is an internal table and you should not add any business rules to this table.  
Figure 2. Default variable editor

## Variable editor in Agent Workspace {#service-catalog-variable-editor__section_q1b_4v4_jkb}

In Agent Workspace, the following scenarios are possible:

* If the variable editor formatter is available in the Workspace view of the form, the variable editor is automatically added to the Variables section in the Agent Workspace UI.
* If the variable editor formatter is added inside a section in the Workspace view of the form, that section does not display the variable editor in the Agent Workspace UI.
{#service-catalog-variable-editor__ul_o5l_nhw_3mb}  
The following variable types are not displayed in the variable editor.

* Macro
* Macro With Label
* UI Pages
{#service-catalog-variable-editor__ul_u1r_pv4_jkb}  
The following variables are displayed as a select box in the variable editor:

* Multiple Choice
* Numeric Scale
* Lookup Multiple Choice
{#service-catalog-variable-editor__ul_ogq_1w4_jkb}

## Variable editor in Service Portal {#service-catalog-variable-editor__section_mv2_thw_3mb}

In the Service Portal UI, the variable editor is available for forms with the
variable editor formatter.  
Note:  
Since Service Portal is only for requester use cases, it is recommended to use the Agent Workspace UI for the variable editor.

## Making a variable editor read-only {#service-catalog-variable-editor__section_trr_c3w_3mb}

The following options are available to make a variable editor read only, depending on
application.

Service Catalog variable editors in the core UI
:   The GlideForm [setVariablesReadOnly()](https://www.servicenow.com/docs/zcx4HZKvPkTA8XqPso7MBg "Variable editor displays variable values in fulfiller forms. A requester, while requesting the item, specifies these variable values in the catalog item questions.") method is supported for ServiceNow AI Platform and Agent Workspace forms to make the variable editor read-only. This method is intended for requested item, target record, and catalog tasks.  
    Note:  
    This method is not applicable in Service Portal and is not recommended for catalog forms.

Service Portal variable editors
:   To make the VEditor read-only in Service Portal, navigate to Service PortalPortals, select Service Portal, and specify the following code in the Quick start config field.

        "readonly_variable_editor": "true"


    Note:  
    The UI Page, Macro, and Macro with Label variables are rendered even when the variable editor is read-only.
* **[Configure the default variable editor for a task-extended table](https://www.servicenow.com/docs/djydUc31AprsGLzBM1QOSw)**   
  After you configure the default variable editor for a task-extended table, you can view and edit the values of questions specified by the requester in the record producer. Applicable only for records generated by a record producer.

*[\>]: and then