About Relevant Behaviors

Use the Relevant behavior to make fields hidden or visible, depending on the content of other fields. You can apply a Relevant behavior to a group node to hide all of its children when the behavior evaluates to false.

The Relevant behavior is usually combined with an Event behavior. When you associate a Relevant behavior to a field, the fields in the Web client can only be hidden or revealed upon an OSM server refresh.

For example, if a user selects the value Check in the Payment Method field, the Credit Card Number and Type fields become non-relevant, and should be hidden. In this example, you define an Event behavior to refresh the Web client window when the user tabs out of the Payment Method field. Additionally, you define Relevant behaviors for the Credit Card Number and Type fields to evaluate to false when the user selects Check as the payment method.

Note:

See OSM Concepts for more information about behavior default values, inheritance, and declarative syntax.