Screen UI policies for ServiceNow Mobile

Screen UI policies for ServiceNow Mobile

Use screen UI policies to control which field is mandatory or visible on a mobile app
screen, depending on the conditions that you define for the policy. By creating screen UI
policies, you can improve readability on your screens, giving your users the information they need
to do their tasks more efficiently.

Screen UI policies are similar to the UI policies that are used on forms in the instance, but
screen UI policies are designed for the mobile app. Policies contain a set of conditions that you
can use to determine when the policy applies. When a screen UI policy is triggered by a condition
that you defined for the policy, all UI policy rules that are associated with that policy are
applied.

Differences from UI policies for forms

Screen UI policies are similar to the UI policies that are used on forms with the following
exceptions:

Screen UI policies cannot control whether a field is read-only.

Screen UI policy conditions cannot be scripted.

Reference and date/time field types cannot be used in screen UI policy conditions.

Create a screen UI policy for the mobile app

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

Before you begin

Role required: ui_policy_admin or admin

About this task

A screen UI policy condition evaluates all fields on a
table even if they are not visible on the screen.

In the Application Explorer pane, point to Mobile Studio > UI Policies and click the pop-out icon() that appears.

On the Screen UI Policies list, click New to create a
new screen UI policy.

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.

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.

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.

What to do next

Create UI policy rules in the related list. The screen UI
policy applies these rules when the data on a screen matches the policy conditions. For
details on creating these rules, see Create a UI policy rule.

Create a UI policy rule

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.

In the Application Explorer pane, point to Mobile Studio > UI Policies and click the pop-out icon() that appears.

Select the UI policy that you want to create rules for.

In the UI Policy Rules related list, click New.

On the form, fill in the fields.

Table 2. 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.

Screen UI policies for ServiceNow Mobile

Screen UI policies for ServiceNow Mobile

Use screen UI policies to control which field is mandatory or visible on a mobile app
screen, depending on the conditions that you define for the policy. By creating screen UI
policies, you can improve readability on your screens, giving your users the information they need
to do their tasks more efficiently.

Screen UI policies are similar to the UI policies that are used on forms in the instance, but
screen UI policies are designed for the mobile app. Policies contain a set of conditions that you
can use to determine when the policy applies. When a screen UI policy is triggered by a condition
that you defined for the policy, all UI policy rules that are associated with that policy are
applied.

Differences from UI policies for forms

Screen UI policies are similar to the UI policies that are used on forms with the following
exceptions:

Screen UI policies cannot control whether a field is read-only.

Screen UI policy conditions cannot be scripted.

Reference and date/time field types cannot be used in screen UI policy conditions.

Create a screen UI policy for the mobile app

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

Before you begin

Role required: ui_policy_admin or admin

About this task

A screen UI policy condition evaluates all fields on a
table even if they are not visible on the screen.

In the Application Explorer pane, point to Mobile Studio > UI Policies and click the pop-out icon() that appears.

On the Screen UI Policies list, click New to create a
new screen UI policy.

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.

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.

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.

What to do next

Create UI policy rules in the related list. The screen UI
policy applies these rules when the data on a screen matches the policy conditions. For
details on creating these rules, see Create a UI policy rule.

Create a UI policy rule

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.

In the Application Explorer pane, point to Mobile Studio > UI Policies and click the pop-out icon() that appears.

Select the UI policy that you want to create rules for.

In the UI Policy Rules related list, click New.

On the form, fill in the fields.

Table 2. 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.

Share this page

Feedback

Please rate the usefulness of this page

What would you like to tell us about this specific page?

Provide your email if you'd like us to respond

Provide your email if you'd like us to respond

Confirm

We were unable to find "Coaching" in
Jakarta.
Would you like to search instead?

SubscribeSubscribedUnsubscribeLast updated:Tags:JanuaryFebruaryMarchAprilMayJuneJulyAugustSeptemberOctoberNovemberDecemberNo Results FoundVersionsSearch preferences successfully updatedMy release version successfully updatedMy release version successfully deletedAn error has occurred. Please try again later.You have been unsubscribed from all topics.You are now subscribed toand will receive notifications if any changes are made to this page.You have been unsubscribed from this contentThank you for your feedback.Form temporarily unavailable. Please try again or contact
docfeedback@servicenow.com
to submit your comments.The topic you requested does not exist in therelease. You were redirected to a related topic instead.The available release versions for this topic are listedThere is no specific version for this documentation.Explore productsClick to go to thepage.Release notes and upgradesClick to open thedropdown menu.DeleteRemoveNo selected versionReset