Rules can be configured for views, screens, and separately for each attribute and button located on these views or screens. For other types of WorkView objects, use scripts. For information about configuring scripts, see Scripts.
This procedure provides the basic steps to configure a rule for a WorkView application in OnBase Studio. You can find additional information about configuring rules in the following sections:
To configure rules:
-
In the WorkView application tree, select a view or screen to which the rule
applies. If the rule applies to a button or attribute on the selected view or
screen, select it from the Designer pane.
The Properties pane for the selected object is displayed.
- Select the Scripts tab.
-
Select an event from the Scripts drop-down list.
Note:
Only one rule can be defined for an event type. When a rule already exists, only the Script handler type is available to be added. If a rule already exists for an event type, you can add more operations to the existing rule.
A new rule can still be added for a different type of event.
For information about available events, see Configuring Events. - Make sure the Handler Type drop-down list is set to Rule.
-
Click Add.
Once the rule is added, a new tab is displayed in the Designer pane with a default group of operations for that rule.
- If you want your rules to log events to a Verbose log in the Diagnostics Console, toggle the Verbose Logging option on the upper-right side of the pane.
-
To rename the group, hover your mouse over the group name and click the pencil
icon.
A Rename Group box is displayed where you can rename the group or add an optional description.
- Click Save to confirm the changes.
-
Add an action or condition by clicking the Add Operation
button (+) below the group
name.
The Conditions and Actions sections are displayed on the left.
-
Select
a condition or action.
See Configuring Conditions and Configuring Actionssections for information about available conditions and actions.
The selected condition or action is displayed automatically in the Designer pane. Required fields are displayed in red.
- Enter the required information.
-
Use the plus icon to continue adding operations.
In the following example, the rule sets the IssueDescription field to required if the value of the Priority field is High.
Note:Actions and conditions can be nested under a condition, but they cannot be nested under an action.
- To add another group of operations, click the + Group button on the top of the pane.
-
To remove a group or any operations under it, hover your mouse over the object
you want to remove and click the Delete Operation icon.
The blue strip on the left indicates which parts of the rule will be
affected.
In the following example, only the Set Fields (1) to required action will be deleted.
CAUTION:Deleting cannot be undone. You can restore the previous state if you do not save the repository.
-
Save the repository to save the rule.
The rule is saved to the Scripts tab in the Properties pane.