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 Event 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 Event behavior properties:
From the Design perspective, right-click the behavior and select Open Properties View.
The Behaviors Properties view is displayed.
Click the Events tab.
Specify when the OSM server should apply the Event behavior.
Select:
Save to apply the event when the user clicks the Task web client Save button.
Refresh to apply the event immediately after the user leaves the field associated with the Event behavior.
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 Event 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 Event behavior.
Event Behavior Properties View Event Tab
The Event behavior specifies an action to perform when a given event occurs. Currently, there is one supported event: value-changed. When data associated with the node for which an event rule is defined is changed, the event rule signals the OSM server to re-render the view and return the new results to the Task web client.
For example, you can combine the Event behavior with Relevant Behaviors to display certain fields in an Task web client based on user selection. Consider that you use a Payment Type field with Cash and Credit Card as options. You can create an Event behavior for the Payment Type to re-render the view after the user tabs out of the field. You can create Relevant rules for Credit Card Number, Expiration, and so forth, so that fields relevant to a credit card payment appear in an Task web client when a user selects the Payment Type of Credit Card.
Note:
See OSM Concepts for more information about behavior default values, inheritance, and declarative syntax.Defining Event Behavior Properties
On the Properties view Event tab, you can specify how the OSM server should re-render an Task web client view when an event behavior occurs.
| Field | Use |
|---|---|
| Save | Select to signal the OSM server to re-render the Task web client view only after the user clicks the Task web client Save button. |
| Refresh | Select to signal the OSM server to re-render the Task web client view immediately after the user moves out of the field associated with the behavior. |