Understanding Nested Rules (and Nested Service Requests)

If the input to an orchestration does not meet the "true" condition defined in the orchestration Rule, then it is "false." Typically at this point, the orchestration stops and no further action is taken. However, you can add a "false" condition to the original rule that you can use to invoke another rule, referred to as a nested rule. The nested rule can have an additional condition that when met, invokes a different service request.

The following image shows an orchestration with a nested rule and nested ServiceRequest. The action in the first ServiceRequest is set to "True" because it is invoked when the true condition of the parent rule is met. The action in the first nested Rule is "False" because it is invoked when the false condition of the parent rule is met. The nested Rule then contains a true condition that invokes another ServiceRequest (to perform a task in an EnterpriseOne form), therefore the action in the nested ServiceRequest is "True." You can repeat the nesting of rules and service requests as required by the design of your orchestration.