---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Define conditions for your variant

# Define conditions for your variant {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can define conditions to determine when a page variant is shown. The conditions are based on setting an order, and declaring the criteria that must be met for the page variant to display.
This video shows you how to perform the following procedure.

## Before you begin

Role required: ui_builder_admin

## About this task

If you have multiple page variants that all have the same conditions, the variants go by the order setting.

## Procedure

1. Open the main page for your demo experience.
2. Select the experience you created, and select Default.  
   Figure 1. Demo Experience
3. On the Default variant under the All users record page, select the Menu icon (![Menu icon]()), and select Duplicate variant.
4. On the Tell us about your variant screen, enter Incident record page in the Name field.
5. Since the intent of this task is to restrict this page to users who are opening a record in the Incident table, enter the following under Conditions:
   1. In the Parameter field, select table.
   2. In the Operator field, select is.
   3. In the Value field, replace the text with <kbd class="ph userinput">incident</kbd>.  
      When you created this page earlier in the series, you set this condition to the Task table. Now, you are configuring the page to display only to users accessing a record from the Incident table.

   {#learn-by-example-define-conditions__substeps_ucj_gl4_sbc}  
   Figure 2. Condition fields
6. Select Create.  
   Figure 3. Incident record page  
   Note:  
   You can view the structure of your pages and variants in this experience. The Conditions column shows a View link for each page. You can select View to see the condition for that variant (that is, table=incident). The Audiences column for the Admin only variant shows a 1. You can select the 1 to view the role required to view that variant.
**Related tasks**   

* [Create a demo experience to explore UI Builder](https://servicenow-prod.fluidtopics.net/me7rt~2jwCB4rjFnNfTPZw "An experience in UI Builder is a collection of web pages for users to interact with an application. The experience includes routes, page variants, and the audience and conditions required for each variant, as well as experience settings.")
* [Create a blank page](https://servicenow-prod.fluidtopics.net/5l0P1FlFGSmZkSTyWMH8Vw "After creating a demo experience, you can create a blank page that you can then build on to define what the experience provides to your users.")
* [Create a record page using a template](https://servicenow-prod.fluidtopics.net/kVRGpJtPzuEj8046X1u~dw "After you've created your demo experience, you can create a record page from a template. A record page shows data from a table.")
* [Define an audience for your variant](https://servicenow-prod.fluidtopics.net/bIgJ7f5BfRYLH5CVbqY2Tw "An audience represents a group of users in your organization. You can define who can access this page variant by adding one or more predefined audiences.")
* [Customize forms within a form component](https://servicenow-prod.fluidtopics.net/xSQ7fsKao0U_hYnhWcr5yQ "Customize your form components by accessing Form Builder in UI Builder.")