Creating a Rule
Create a rule to define conditions for an orchestration.
Click here to view a recording of this
feature.
To create a rule:
On the Orchestrator Home page, click the Rules icon. And then on the Rules design page, click the New Rule button.
Alternatively, access the Orchestrations design page and add a Rule step to an orchestration. At the end of row with the Rule step, click Edit (pencil icon) and select Rule from the pop-up box.
On the Rules design page, enter a name for the rule in the Rule field. Do NOT include special characters in the name.
Click the Product Code drop-down list to select a product code to associate with the rule.
This gives an administrator the option to manage UDO security for orchestration components by product code.
In the space provided, enter a short description with a maximum of 200 characters. This description appears below the rule name in the component list.
Click the Edit Long Description button to add a long description to provide more detail about the purpose of the component.
Select the Match Value drop-down menu and select one of the following values:
Match All. Select this option if all conditions in the rule must be met.
Match Any. Select this option if any conditions in the rule can be met.
In the first row in the grid, complete the following columns to add a condition:
Rule Type. Click the drop-down menu and select String, Numeric, or Date depending on the format of the input.
Value 1. Enter a variable for the input name.
Operator. In the drop-down menu, select from the list of operands which include: >, <, >=, <=, =, !=, startsWith, endWith, contains, between, inList.
Literal. Click this check box to indicate a literal value.
Value 2. If you selected the Literal check box, manually enter a value.
Literal Value Type. If you selected the Literal check box, click the drop-down menu and select the format of the literal value: string, numeric, data.
Add additional conditions to the rule as needed. If you add a condition by mistake, you can delete it by clicking the Remove button at the end of the row with the condition.
Click the Save button.
The first time a new rule is saved, it is saved as a "Personal" UDO. Thereafter, you can use the UDO buttons described in the User Defined Object (UDO) Features in the Orchestrator Studio section to move the rule to the appropriate status.
After adding a rule and a service request to an orchestration, in the Orchestration design page, you must define the action for the rule to invoke the service request. See Defining the Actions Between a Rule and Dependent Components for more information.