--- 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 UI policy # Service catalog UI policy {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 UI policy Service catalog UI policies in ServiceNow control the behavior and appearance of catalog item forms presented to users. These policies enable you to define custom process flows and improve the user experience by dynamically managing variables on catalog items or variable sets during service catalog ordering. Show full answer Show less ## Key Features * **Scope:** UI policies apply to specific catalog items or any item using a particular variable set. * **Variable Restrictions:** Policies can only reference variables defined for the targeted catalog item or variable set, and these variables must be visible on the form for conditions to evaluate correctly. * **Limited Applicability:** Mandatory and Read Only actions do not apply to variables like Break, Container Split, UI Macros, Labels, or UI Pages. The Set Visible action also excludes Break and Container Split types. * **Actions on Variable Sets:** Actions applied on a variable set affect all variables within it. When conflicting actions exist between a variable and its variable set, the action with the lowest order (highest priority) takes effect. * **Priority Order of Actions:** Mandatory has the highest priority, followed by ReadOnly and then Display. For example, a mandatory variable will override read-only or hidden settings. * **Visibility Behavior:** Variables set to mandatory become visible and editable even if previously hidden or read-only. Containers or variable sets containing mandatory variables cannot be hidden if those variables lack values. * **Service Catalog Wizard Support:** UI policies are supported when catalog items are viewed in the service catalog wizard interface. * **Policy Precedence:** Catalog item UI policies take precedence over variable set UI policies by default, but this can be changed via the glide.sc.uipolicy.variablesetrunfirst property. ## Practical Considerations for ServiceNow Customers * Use catalog UI policies to enforce required fields, control visibility, and set read-only states dynamically based on user input or conditions, improving form usability and data quality. * Apply policies carefully, considering variable types and priority order, to avoid conflicts and ensure that mandatory fields remain accessible. * Leverage variable sets with UI policies to efficiently manage groups of variables, but be mindful of how actions cascade across variables within sets. * Test UI policies in the service catalog wizard to validate expected behavior and adjust the glide.sc.uipolicy.variablesetrunfirst property if needed to customize policy execution order. UI policies can be used to define custom process flows for tasks. Catalog UI policies control the behavior of catalog item forms when presented to your users. Catalog UI policies can be applied to a catalog item or a variable set. [UI policies](https://www.servicenow.com/docs/access?context=t_CreateAUIPolicy&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) are useful when applied to service catalog items. Keep the following points in mind when creating service catalog UI policies: * A catalog UI policy applies to either a specific catalog item or any item that uses a specific variable set. * A catalog UI policy can only contain and reference variables that are defined for the catalog item or variable set. * Like UI policy conditions, the variables in a service catalog UI policy condition must be visible (even if hidden by UI policy or read-only) on the form for the condition to be tested. Also, ensure that the variables have names. For more information, see Create a catalog client script. * Limited UI policy functionality applies to following variables: * The Mandatory and Read Only policy do not apply to the following variable types: Break, Container Split, Container End, UI Macro, UI Macro with Label, Label, UI Page. * The Set visible policy does not apply to the following variable types: Break, Container Split, Container End. {#c_ServiceCatalogUIPolicy__ul_ubm_v1k_gs} * Service catalog UI policies are applied to variables and variable sets of catalog items ordered in the service catalog. Policies can also be applied when the variables are present in a Requested Item or Catalog Task form. Note: The Clear the variable value UI policy action is not applicable on variable sets and containers. * Catalog UI policy actions can be applied on a variable set. The actions on a variable set are applied on all variables within the variable set. If different catalog UI policy actions are applied on a variable or a variable set, the action with the lowest order is considered. * The priority order for UI actions types is: 1. Mandatory (highest) 2. ReadOnly/Display {#c_ServiceCatalogUIPolicy__ol_sxw_n1z_sbb} If a variable is set to mandatory and does not have value, readonly or hide do not work on that variable. If a variable is hidden or readonly, and then set to mandatory, the variable field becomes visible or editable. This priority order is also applicable for variable sets and containers. If a variable set or container has a mandatory variable without any value, then the container or variable set cannot be hidden. * Catalog UI policies are supported for catalog items viewed in a service catalog wizard. Note: The UI policy for catalog items always takes precedence over UI policy for variable sets. You can change this behavior by editing the glide.sc.ui_policy.variable_set_run_first property. {#c_ServiceCatalogUIPolicy__ul_djj_zxn_pq} * **[Create a UI policy for catalog items](https://www.servicenow.com/docs/QnrVl1kj68Yo0Iq5y7UqUQ#t_CreatUIPolicyForSvcCalgIt)** You can apply UI policies for catalog items ordered in the service catalog.