About Service Action Spawning Conditions
Service action spawning conditions determine whether a service action executes. When you map service bundles to service actions, Design Studio assigns to each service action a spawning condition of Always (no conditions prevent the action from executing). The conditions associated with the service action must evaluate to true for the service action to execute.
The labels used in the evaluation of the service action spawning condition are those that are derived as a result of the upstream parameters to service action parameter mapping. Use the service action labels in your spawning expression.
You define the spawning conditions on the Service Bundle editor Service Actions tab. For example, you can specify that an action always execute or only if a specified parameter is present.
Also, you can define a logical expression that is used with one of the delivered spawning conditions, where ASAP executes the service action if both the out-of-the-box expression and your user-defined expression evaluate to true. The range of options available enables a service action to be executed if the service action parameter value is within a set range of values, or if the service action parameter is greater than, less than, or equal to, a specified value. You can combine multiple expressions using an AND or OR operator.
Logical Expression Components
To define your own spawning logic, enable the Include Expression check box on the Service Bundle editor Service Actions tab and define a logical expression in the associated text box.
The logical expression mechanism works in cooperation with one of the out-of-the-box spawning expressions. For example, if you have specified a service action condition of Equals and have created a logical expression, both of these conditions must evaluate to true in order for the service action to be executed. If you want only the logical expression to trigger the execution of the service action, then use the action condition of Always and specify a logical expression.
The following operators can be used to define logical expressions:
| Operators | Description |
|---|---|
|
AND, OR, NOT |
Operators used to create compound expressions. For example:
|
|
ISDEF, NOTDEF |
Operators that can be used with single parameters. For example:
Note: Always use brackets with these operators. |
|
>, <, >=, =<, =, != |
The parameter values must be able to be converted to integers. For example:
|
|
LIKE, !LIKE |
String operators. The strings being evaluated must be placed inside quotation marks. It is also possible to use wildcard syntax such as the % (to specify one or more characters) and ? (acts on a single character). For example:
Note: Always use brackets with these operators. |
Logical expressions are limited to a length of 255 characters.
Logical Expression Operational Order
To specify the order of operations, use as many parentheses as needed; for example:
((A < 8) OR ((NOTDEF B) AND ((C != 3) OR (NOT (D = 9)))))
Logical Expression Error Conditions
The following error conditions that may arise as a result of the use of logical expressions:
-
Using the integer operator when the input parameter cannot be converted to an integer (all SRT parameters are strings initially)
-
The specified parameter label is not present
The evaluation of an expression fails and a SYS_ERR message is generated in the diagnostics. These errors do not fail the work order; however, the atomic action is not executed.
Note:
The syntax of complex expressions is not currently checked by Oracle Communications Design Studio but is checked by ASAP at run time.
Related Topics