Create screen UI policies to dynamically change which fields are mandatory or visible on screens in the ServiceNow Agent mobile app.

1. Navigate to System Applications > Studio.
2. In the Select Application pop-up window, select your mobile application.
3. In the Application Explorer pane, point to Mobile Studio > UI Policies and click the pop-out icon() that appears.
4. On the Screen UI Policies list, click New to create a new screen UI policy.
5. On the form, fill in the fields.

   Table 1. Screen UI Policy form

   Field	Description
   Name	Name of the screen UI policy.
   Short description	Short summary of the screen UI policy.
   Order	Processing sequence, from the lowest to the highest number. If two policies conflict, the screen UI policy with the higher number executes. For inherited UI policies, the extended (child) table UI policies are executed first. Next, the base table UI policies are executed from the lowest to the highest specified value.
   Table	Table for the screen that you want to modify.
   Condition	Conditions that must be fulfilled to apply this screen UI policy. Conditions are built with the condition builder. For details about this tool, see Condition Builder Conditions are only rechecked if a user manually changes a field on a screen. If the change is made by a UI action, context menu action, or through the list editor, it is not evaluated. Note: Some UI policy conditions are not supported in mobile screen UI policies. See the table below for supported conditions.
   Reverse if false	Check box for specifying that the screen UI policy action should be reversed when the conditions of its policy evaluate as false. When the conditions are true, actions are taken and when they change back to false, the actions are reversed (undone).
   Active	Check box for enabling the screen UI policy.

   Table 2. UI Policy condition support

   Supported UI policy conditions	Unsupported UI policy conditions
   Equal and Not Equal (= , !=) ISEMPTY, ISNOTEMPTY Less than (or equals)	starts with ends with is anything is different is empty string is one of, is not one of Conditions on DateTime fields "Read only" UI policies

Example: Use a screen UI policy when the state field is not On Hold

This example shows how you can configure a screen UI policy to apply on screens using data from the Incident [incident] table. You can build a condition that checks the values of fields on this table, in this case, the State field. When [State] [is not] [On Hold], the UI policy applies the associated UI policy rules. When you select the Reverse if false check box, a field made invisible when the state field is not On Hold is made visible when the state is On Hold.

Create UI policy rules to control whether the fields that your users see are visible or mandatory with the ServiceNow Agent mobile app, according to the conditions in your screen UI policy actions.

1. Navigate to System Applications > Studio.
2. In the Select Application pop-up window, select your mobile application.
3. In the Application Explorer pane, point to Mobile Studio > UI Policies and click the pop-out icon() that appears.
4. Select the UI policy that you want to create rules for.
5. In the UI Policy Rules related list, click New.
6. On the form, fill in the fields.

   Table 3. UI Policy Rule form

   Field	Description
   UI policy	Screen UI policy that this rule is associated with. The field is automatically populated when you create rules from the UI policy rules related list on a screen UI policy form.
   Field name	Name of the field to apply the rule to.
   Visible	Options that change the visibility of a field on a screen. If the field is not available on the screen, you cannot configure a rule to make it appear. Leave Alone: Rule that has no effect on the visibility of this field. True: Rule that makes this field visible. False: Rule that hides this field on the screen.
   Mandatory	Options that change whether the field is mandatory. Leave Alone: Rule that has no effect on this field. True: Rule that makes this field mandatory. False: Rule that makes this field non-mandatory.

Example: Use a UI policy rule to hide a field

This example shows how you can control the visibility of the On hold reason field. On hold reason is selected in the Field name field, and the Visible field is set to False. If the screen UI policy conditions are met, the On hold reason field is hidden on the screen.