Example 6

You have a changed request type that contains the following custom fields:

  • Resolution (a drop-down list, that includes the value Automatic, to capture the resolution of the request)

  • Team Manager (an auto-complete)

  • Get feedback at completion (Yes and No options)

When Automatic is selected in the Resolution list, you want to hide the Team Manager field and display the Get feedback at completion option.

To accomplish this, do the following:

  1. Create an advanced "Apply on field change" rule with the dependency Resolution = "Automatic".

    Rule logic: setFieldVisible(true)Result Fields: Team Manager

  2. Create an advanced "Apply on field change" rule with the dependency Resolution = "Automatic".

    Rule logic: setFieldVisible(false)Result Fields: Get feedback at completion

    The first two rules are triggered when Resolution is set to Automatic.

  3. Create two additional rules to determine field behavior when the Resolution field is set to any value other than automatic, as follows:

    1. Create an advanced "Apply on field change" rule with the dependency Resolution != "Automatic".

      Rule logic: setFieldVisible(false)Result Fields: Team Manager

    2. Create an advanced "Apply on field change" rule with the dependency Resolution != "Automatic".

      Rule logic: setFieldVisible(true)Result Fields: Get feedback at completion

  4. For the appropriate fields to be visible or hidden when the request is reloaded, or when someone else views the request in a different session, create four "Apply on page load" rules using the same rule logic as you used in the first four rules.

    To accomplish this example use case, you would need a total of eight UI rules.