Select Route task to all participants, in order specified from the list. Select the Complete task when a participant chooses: outcome checkbox.

Designing Human Tasks 27-47 ■ If the total amount of the expense request is less than 100, approval is only required from one of the participants. Otherwise, it must be approved by all three. ■ If an expense request is rejected by any of the participants, it must be returned to the previous participant for re-evaluation. If it is rejected by the first participant, the expense request is rejected and marked as completed. This behavior is implemented using the following rules. Note that when a rule dictionary is generated for advanced routing rules, it is created with a template rule that implements the default GO_FORWARD behavior. You can edit this rule, and make copies of the template rule by right-clicking and selecting Copy Rule in the Oracle Business Rules Designer. If the amount is greater than 100 and the previous assignee approved the task, it is not necessary to provide a rule for routing a task to each of the assignees in turn. This is the default behavior that is reverted to if none of the rules in the ruleset are triggered: ■ Early approval rule Figure 27–46 : Figure 27–46 Early Approval Rule ■ Push back on the rejected rule Figure 27–47 : Figure 27–47 Push Back On The Rejected Rule ■ Complete the Assignee1 rejected rule Figure 27–48 : 27-48 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite Figure 27–48 Completion of the Assignee1 Rejected Rule For information about iterative design, see the workflow-106-IterativeDesign sample available at the Oracle Technology Network: https:soasamples.samplecode.oracle.com

27.3.7.2.5 Linked Dictionary Support For human workflow, business rule artifacts are

now stored in two rules dictionaries. This is useful for scenarios in which you must customize your applications. For example, you create and ship version 1 of an application to a customer. The customer then customizes the rulesets in the application with Oracle SOA Composer. Those customizations are now stored in a different rules dictionary than the base rules dictionary. The rules dictionary that stores the customized rulesets links with the rules in the base dictionary. When you later ship version 2 of the application, the base rule dictionary may contain additional changes introduced in the product. The ruleset customization changes previously performed by the customer are preserved and available with the new changes in the base dictionary. When an existing application containing a task using rules is opened, if the rules are in the old format using one dictionary, they are automatically upgraded and divided into two rules dictionaries: ■ Base dictionary ■ Custom dictionary For more information about customizations, see Chapter 43, Customizing SOA Composite Applications.

27.3.7.2.6 Creating Advanced Routing Rules

To create advanced routing rules: 1. In the Assignment section, click the icon to the right of Task will go from starting to final participant .

2. Select Use Advanced Rules from the list.

3. To the right of Rules Dictionary, click the Edit icon, as shown in

Figure 27–49 .