Creating a Rule

Create a rule to define conditions for an orchestration.

To create a rule:

1. On the Orchestrator Studio Home page, click the Rules icon.

2. On the Rules side panel, click the New drop-down menu and select Standard.

3. Create and name the rule as described in Creating a Component.

4. On the Rules design page, enter a name for the rule in the Rule field. Do not include special characters in the name.

5. In the Match Type drop-down menu, select one of the following values:

   • Match All. Select this option if all the conditions in the rule must be met.

   • Match Any. Select this option if any of the conditions in the rule can be met.

6. 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, Boolean, 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: >, <, >=, <=, =, !=, starts with, ends with, contains, is between, is in list. The "is in list" operator must be a string of values delimited by the pipe character ( | ). Example values: v1|v2|v3.

   • Literal. Slide the toggle to the right to indicate a literal value.

   • Value 2. If you have enabled the Literal toggle, manually enter a value.

     Starting with Tools Release 9.2.6.3, from the Value 2 field drop-down menu, you can select:

     • <Null> if the Literal option is enabled and the value in the Operator field is = or !=.
     • <Blank> if the Literal option is enabled and the Rule Type is selected as String.

       A string is considered blank if it is an empty string ("") or if it contains only one or many spaces.

   • Literal Value Type. If you have enabled the Literal toggle, click the drop-down menu and select the format of the literal value: string, numeric, or date.

7. 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.

8. Click the Save button.

A new rule is saved for the first time as a "Personal" UDO. Thereafter, you can use the UDO links 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.