Using Rules

You can specify conditional rules for how fields behave. Your screens can display different fields, or make them mandatory or optional depending on dynamically changing conditions you specify.

You can learn more about using dynamic logic in this video tutorial. (Please note: this video tutorial is from an older version of ASM, vFire, but is still relevant)

Configure a Rule

  1. Select the Rules tab.

  2. Double click on an existing rule if you wish to update it, or select Create New to create a new rule.

    The Field Rule Configuration window appears.

  3. Provide a name for the rule if you are creating a new rule.

  1. Select the Boolean Rules Builder editing box.

    1. Scroll to view a list of all possible values from a multi-tiered list, and choose the field for which you want to create a rule.

    2. In the next field, select an operator. The operators you can pick depend on the item you selected. You can pick from standard boolean values: =, <>, <=, contains, starts with, ends with, and so on.

    3. Select the value or criteria for the field from the drop-down list in the next field.

The items you can select are filtered to show relevant fields of the same data type as the selected field. If an item is not available for selection it is shown in italics allowing you to expand the next tier in a multi-tier list to choose an item from a lower tier.

For Example, here we can see Closed Analyst is not a valid selection, but if we drill in to it using the black arrow, the Closed Analyst's Default Group is.

Items in italics are not viable data types, but dependent items often are,
Available data from within the italicized option
  1. Add further criteria by selecting the And, Or or Not buttons and repeat step 4.

NOT statements will be evaluated before AND, and AND before OR.

  1. Group your criteria if necessary using the Group button. This will insert parentheses around the selected part of a statement.

  2. When you are done select Save.

About Grouping Criteria and the Order of Operations

Order of Operations

Those criteria contained within the parentheses (Grouped) are evaluated first and the result then processed as part of the entire statement with NOT having the highest priority, followed by AND, and then OR.

For example, if we wanted to compose a rule that evaluated true when 2 conditions are true: 1. the call logged was not critical and 2. it did not come from either the BAU Support or the Cloud Support pipelines, we will have to group the statement to get it to evaluate in the correct order.

EXAMPLE:

NOT ({:Call Priority} = "1 Critical"

AND NOT ({:Call Source} = "BAU Support"

OR {:Call Source} = "Cloud Event"))

We can see here that there is a group inside of a group. *All criteria in parentheses are evaluated first and within that, the order of operations begins with the NOT statements.

Let's break it down:

  1. NOT ({:Call Priority} = "1 Critical"

In this case, the first thing evaluated is the first grouping "Call Priority is not equal to critical"

  1. AND NOT

Next the AND is evaluated according to the order of operations, and because the statements that follow are also grouped, they will be evaluated on the whole.

  1. ({:Call Source} = "BAU Support"

    OR {:Call Source} = "Cloud Event"))

Because this line is preceded by "AND NOT", we are evaluating for everything not equal to BAU Support OR Cloud Event.

The final result is that this rule is looking at non-critical tickets where the call source is not BAU Support or Cloud Events.

To Group Criteria

  1. Select the content to group using your keyboard or mouse

  2. Click "Group"

Apply a Rule to a Field or Section

  1. Apply the rule to the relevant field by selecting the field. The Field Settings tab is automatically displayed.

  2. In the Field Settings, use the drop-down lists to select where to apply the rule. Different field types display the option to apply a rule in slightly different ways.

  1. Scroll to the bottom of the screen if necessary and select Save to save the changes.

FAQ

Can I apply many rules to a single screen element?

No just one. If you want to apply two rules, just create a third rule that contains both of the others.

Are rules available on other screens?

Yes - you can see rules from parent screens.

If I clone a screen with rules, are the original rules available on the new screen?

Yes

Does this affect the behavior of the Unique field property?

No – that continues to work as before.

Last updated

Was this helpful?