How to Create Service Data Object SDO References How to Define Collections

Using Approval Management 26-21 Figure 26–15 Add Sequential Stage If you chose to create a parallel stage, the Assignment and Routing section looks like Figure 26–16 . Figure 26–16 Add Parallel Stage

3. Double-click the stage you just created, or select the stage and click the Edit icon.

The Edit dialog displays, as shown in Figure 26–17 . Figure 26–17 Edit Stage Dialog 26-22 Modeling and Implementation Guide for Oracle Business Process Management 4. Enter a name for the stage. 5. Choose one of these options: ■ Non Repeating - specifies that there is only one stage in parallel for each element in a collection ■ Repeat Stage in parallel for each item in a collection - specifies that the stage to repeat in parallel for each element in a collection. For example, if a purchase order contain 10 lines, the stage is repeated 10 times in parallel. 6. From the dropdown list, select a collection. 7. According to your selection, use one of these options: ■ If you selected Non Repeating, click OK to close the Edit dialog. ■ If you selected Repeat Stage in parallel for each item in a collection, additional options display, as shown in Figure 26–18 . Figure 26–18 Edit Stage Dialog: Repeat Stage Do the following: – Select a default outcome. – Select a consensus percentage. – Choose either to trigger the outcome immediately or wait until all the votes are in before triggering the outcome. – Click OK to close the Edit dialog.

26.3.6.2 How to Model Task Participants

Inside each stage you either can edit the default task participant or add new task participants. Task participants are assigned based on routing patterns, which can be any of the following: ■ Single ■ Parallel ■ Serial Using Approval Management 26-23 ■ FYI For information on participant types and assigning task participants to a stage, see How to Assign Task Participants in the Creating Human Task Definitions with the Human Task Editor section in the Designing Human Tasks chapter in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. After selecting a routing pattern, you also must select and model a list builder. This process is discussed in more detail in Section 26.3.6.3, How to Model and Configure List Builders.

26.3.6.3 How to Model and Configure List Builders

Stage uses a combination of list builders to generate the approver list. For more information, see Section 26.2.3, Stages and Section 26.2.4, List Builders. You can only use each type of list builder only one time per stage. You can arrange these approver list builders in either sequential or parallel order. The order you select governs the order in which those approvers included in approver lists that are generated by list builders are assigned an approval task. The following list builders are specific to AMX: ■ Approval Groups ■ Job Level ■ Position ■ Supervisory Table 26–2 describes the AMX-specific list builders and the options available to them. Note: For information about modeling other list builders, see Creating a Single Task Participant List in the How to Assign Task Participants section in the Creating the Human Task Definition with the Human Task Editor chapter in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. Table 26–2 List-Builder Options Option Name Description List Builder Value-based Specifies constraints to build the list of participants based on provided values. All Except Position Rule-based Specifies constraints to build the list of participants based on rules that are defined in the Rule Editor. All Name The name of the approval group to use. Approval Groups Allow Empty Groups Allows the use of approval groups with no members. Approval Groups List Ruleset Name of the ruleset specifying constraints for building participant list. All Starting Participant The first participant in a list, usually a manager. Job Level Position Supervisory 26-24 Modeling and Implementation Guide for Oracle Business Process Management If you do not configure the hierarchy provider plug-in, then the position list builder does not work. When you define a hierarchy extension, if you do not define the property mustUseSpecifiedProvider then its default value is true.. You can configure the Supervisory and Job Level list builders not to throw an exception when there is a problem with the hierarchy plug in. To configure the list builders, you must add the mustUseSpecifiedProvider property to the workflow-identity-config.xml configuration file, and set the value attribute to false . By default, the workflow-identity-config.xml file does not include the mustUseSpecifiedProvider property. If this property is present and its value is false , then, then the Supervisory and Job Level list builders use the LDAP management chain when there is a problem with the hierarchy plugin. Example 26–5 shows a workflow-identity-config.xml file that specifies the mustUseSpecifiedProvider property. The value of this property is set to true so that the Supervisory and Job Level builders fail when the hierarchy plug in is not available. Example 26–5 workflow-identity-config.xml Configuration File ISConfiguration xmlns=http:www.oracle.compcbpelidentityserviceisconfig Top Participant The last participant in the approval. Approval does not go beyond this participant in a hierarchy. Job Level Position Supervisory Number of Levels A positive number specifying the number of levels to traverse for Supervisory, or the number of job level for Job Level and Position. This number can be an absolute value, or a value relative to starting point or creator. Job Level Position Supervisory Relative to A positive number specifying the number of levels to traverse for Supervisory, or the number of job level for Job Level and Position. Possible values are: starting point, creator and absolute. Job Level Position Include all managers at last level If the job level equals that of the previously calculated last participant in the list then it includes the next manager in the list. Job Level Utilized Participants Utilizes only the participants specified in this option from the calculated list of participants. Available options are: Everyone, First and Last manager, Last manager. Job Level Position Auto Action Enabled Specifies if the list builder automatically acts on task based on the next option. Supervisory Job Level Position Auto Action Specifies the outcome to be set. It can be null if auto action is not enabled. Supervisory Job Level Position Table 26–2 Cont. List-Builder Options Option Name Description List Builder