Click the Add icon. Select Approval Group. Click OK.

Using Approval Management 26-67 Figure 26–78 Task Configuration: Event Driven, Edit Mode

3. Make your changes and click Apply to save them

4. Click Deploy to deploy your changes.

26.5.4.1.1 How to Specify Routing Settings The Event Driven tab contains a limited set of

the routing options available in the Human Task Editor. Approval aggregation requirements can be any of the following, as shown in Figure 26–79 : ■ None ■ Once per task ■ Once per stage WARNING: An improper or incomplete rules definition in a list-creation rule set can cause run-time errors. Errors can be caused by the following: ■ No rule was defined in the rule set. ■ None of the conditions defined in the rule was met. Ensure that rules are properly defined to handle all conditions. 26-68 Modeling and Implementation Guide for Oracle Business Process Management Figure 26–79 Routing Settings

26.5.4.1.2 How to Define Expiration and Escalation Policies Defining expiration and

escalation policies in the Worklist Application is very similar to how it is done in the Human Task Editor. For more information, see the section How to Escalate, Renew, or End the Task in the chapter Designing Human Tasks in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. Figure 26–80 Expiration and Escalation Policies

26.5.4.1.3 How to Specify Notification Settings Creating or updating notification settings

for a task in the Worklist Application s very similar to how it is done in the Human Task Editor. For more information, see the section How to Specify Participant Notification Preferences in the chapter Designing Human Tasks in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. Figure 26–81 Notification Settings

26.5.4.1.4 How to Allow Task Access Access-rule settings can be set to control the actions

a user can perform, and is very similar to how it can be done in the Human Task Editor. Content and action permissions can be specified based on the logical role of a user, such as creator inititator, owner, assignee, and reviewers. For more information, see Section 26.3.9.2, How to Define Security Access Rules.