---
sourceDocument: Yokohama Mobile Configuration and Navigation
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/mobile

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - evelopment, Data and Analytics


---

# Create a mobile UI rule

# Create a mobile UI rule {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 13, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Create a mobile UI rule to apply styling or field calculations for your mobile UI elements.

## Before you begin

Role required: admin

## Procedure

1. Navigate to AllSystem MobileMobile UIMobile UI Rules.
2. In the Mobile UI Rules list, select New.
3. In the Mobile UI Rule form, fill in the fields.  
   {#create-mobile-ui-rule__table_r5w_qhw_knb__entry__2}

   | Field | Value |
   |-|-|
   | Name | Name of the mobile UI rule. |
   | Active | Whether the mobile UI rule is active. |
   | Condition | Condition under which the mobile UI rule is used. The rule executes if the condition evaluates as true. Mobile UI rules with no condition always evaluate as true. To use a field in a condition, the field must be displayed on the mobile card, or it must be added to the Card fields tab on the card \[sys_sg_view_config\] record for that card. If the field is a reference field, you can also access information in the related record using dot-walking. See [Dot-walking to data in related tables](https://www.servicenow.com/docs/access?context=c_DotWalking&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). Conditions can also use variables defined in the mobile scratchpad. These variables are created and evaluated using the script in the Mobile Scratchpad Script field in the card \[sys_sg_view_config\] record. Note: For details on the operators available for your condition, see [Operators available for filters and queries](https://www.servicenow.com/docs/access?context=r_OpAvailableFiltersQueries&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US). |
   | Parent Table | The parent table that the mobile UI rule applies to. Select either: * Input Form Screen * Mobile View {#create-mobile-ui-rule__ul_t3m_ssq_lnb} |
   | Parent | The input form screen or mobile view record to which your mobile UI rule is applied. |
   | Triggers | The condition that triggers the mobile UI rule. Select one or both of the following options. * onLoad: The mobile UI rule triggers when the record loads. * onChange: The mobile UI rule triggers when the record is changed. * onUserAction: The mobile UI rule triggers when the user performs the specified action. Note: To use the onUserAction trigger, a User Action Id must be associated with the UI rule. * onSubmit: The mobile UI rule triggers when the input form is submitted. {#create-mobile-ui-rule__ul_trt_qtq_lnb} |
   | User Action Id | A unique value that identifies this action record. It is needed to associate the action with a UI rule. |
   | Order | Order in which the mobile UI rule executes. If there are multiple rules affecting the same element, the rules execute according to this value. Lower numbered rules execute before higher numbered rules. |
   | Reverse If False | When this field is selected, the mobile UI rule actions are reverse if the condition evaluates as false. Important: When this field is selected for high order mobile UI rules, it inactivates prior rules that address the same target and operation. |
   [Table 1. Mobile UI Rule form]

   {#create-mobile-ui-rule__table_r5w_qhw_knb}
4. Select Submit

## What to do next

After creating your mobile UI rule, you must create mobile UI rule actions to execute when your rule is used.

*[\>]: and then