When editing order and task data in an editor, you can right-click data node behaviors and select Open Properties View to access the behavior properties.You use the Properties view tabs to model Relevant behaviors.
Note:
The level at which you create a behavior (at the data element level, task level, or order level) determines where you access and configure the behavior's properties. See "Creating New Behaviors" for more information.To define Relevant behavior properties:
From the Design perspective, right-click the behavior and select Open Properties View.
The Behaviors Properties view is displayed.
Click the Details tab.
The Behaviors Properties view Details tab is displayed. The Name, Type, and Path field values are read-only, and cannot be modified on this tab. See "Defining Behavior Detail Properties" for more information about the options that you can define on this page.
Click the Conditions tab.
Use the Conditions tab to add conditional logic to the Relevant behavior. See "Defining Behavior Condition Properties" for more information about defining conditions for behaviors.
Click the Notes tab.
Use the Notes tab to describe the functionality or include internal documentation about the Relevant behavior.
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.