Edit Participant Type Dialog

3.33 Edit Participant Type Dialog - Parallel Page

Use to configure the parallel participant type.

This participant type is used when multiple users, working in parallel, must take action simultaneously, such as in a hiring situation when multiple users vote to hire or reject an applicant. You specify the voting percentage required for the outcome to take effect, such as a majority vote or a unanimous vote.

For example, a business process collects the feedback from all interviewers in the hiring process, consolidates it, and assigns a hire or reject request to each of the interviewers. At the end, the candidate is hired if the majority of interviewers vote for hiring instead of rejecting.

You can define multiple participant types in parallel blocks. After creating an initial parallel participant type, click the Add icon in the Assignment page of the Human Task Editor, and select Parallel participant block. This creates a second participant block in parallel.

Element	Description
Label	Enter a recognizable label for this participant or accept the default value of Stagenumber.Participantnumber. This label must be unique within this workflow (for example, Approval Manager, Primary Reviewers, and so on). This label shows up in other parts of the Human Task Editor, such as the configuration of access rules and the specification of advanced routing rules.
Vote Outcome	You can specify a voted-upon outcome that overrides the default outcome selected in the Default Outcome list. This outcome takes effect if the required percentage is reached. Outcomes are evaluated in the order listed in the table.
Voted Outcomes table	Click the Add icon to add additional columns.
Voted Outcomes column	Select an outcome for the task (for example, Any, ACCEPT, REJECT, or any other outcome specified in the Outcomes dialog). The Any outcome enables you to determine the outcome dynamically at runtime. For example, if you select Any and set the outcome percentage to 60, then at runtime, whichever outcome reaches 60% becomes the final voted outcome. If 60% of assignees vote to reject the outcome, then it is rejected.
Outcome Type column	Select a method for determining the outcome of the final task. By Expression: Dynamically specify the details with an XPath expression. By Percentage: Specify a percentage value that determines when the outcome of this task takes effect.
Value column	Specify a value based on your selection in the Outcome Type column. If you selected By Expression, click the Browse icon to the right of the field to display the Expression Builder dialog for creating an expression. If you selected By Percentage, enter a percentage value required for the outcome of this task to take effect (for example, a majority vote (51) or a unanimous vote (100)). For example, assume there are two possible outcomes (ACCEPT and REJECT) and five subtasks. If two subtasks are accepted and three are rejected, and the required acceptance percentage is 50%, the outcome of the task is rejected. Note that this functionality is nondeterministic. For example, selecting a percentage of 30% when there are two subtasks does not make sense.
Default Outcome	Select the default outcome for this task to take effect if the consensus percentage value is not satisfied. This happens if there is a tie or if all participants do not respond before the task expires. The default outcomes that display are based upon your selections in the Outcomes dialog in the General page of the Human Task Editor. You can also select By Expression to use the XPath Expression Builder.
Immediately trigger voted outcome when minimum percentage is met	If selected, the outcome of the task can be computed early with the outcomes of the completed subtasks, enabling the pending subtasks to be withdrawn. For example, assume four users are assigned to act on a task, the default outcome is APPROVE, and the consensus percentage is set at 50. If the first two users approve the task, the third and fourth users do not need to act on the task, since the consensus percentage value has already been satisfied. This option is automatically selected.
Wait until all votes are in before triggering outcome	If selected, the workflow waits for all responses before an outcome is initiated.
Share attachments and comments	Select this checkbox if you want all group voters or workflow participants to share comments and attachments for this task. This option is typically used when users must collaborate, such as collectively producing a proposal or a design. This information typically displays in Oracle BPM Worklist.
Build a list of participants using: (Names and expressions)	Select Names and Expressions as a method for assigning a user, group, or application role to participate in this task.
Let participants manually claim the task	If you select this, then the task is assigned to all participants in the list. It becomes assigned to a particular participant when that participant manually claims it. To find out more about each assignment pattern, and to select and configure it, click Assignment Pattern. The Assignment Pattern dialog box appears.
Auto assign task to a single	Select Auto-assign to a single list, select User, Group, or Application Role, then select an assignment pattern. To find out more about each assignment pattern, and to select and configure it, click the Assignment Pattern icon. The Assignment Pattern dialog box appears.
Value-based	Click the Add icon to assign a user, group, or application role to participate in this task. Users who are members of the specified group or application role are assigned this task. For a user to act on a task assigned to a group or an application role, they must first claim the task in Oracle BPM Worklist during runtime. This enables a task to be assigned to a user who is, for example, passed the payload of a BPEL process or computed in a prior activity of a BPEL process. Application roles consist of users or other roles grouped logically for application-level authorizations. These roles are application-specific and are defined in the application Java policy store rather than the identity store. These roles are used by the application directly and are not necessarily known to a Java EE container. Application roles define policy. Java permissions can be granted to application roles. Therefore, application roles define a set of permissions granted to them directly or indirectly through other roles (if a role is granted to a role). The policy can contain grants of application roles to enterprise groups or users. In the `jazn-data.xml` file of the file-based policy store, these roles are defined in <`app-role`> elements under <`policy-store`> and written to `system-jazn-data.xml` at the farm level during deployment. You can also define these roles after deployment using Oracle Enterprise Manager Fusion Middleware Control Console. You can set a task owner or approver to an application role at design time if the role has been previously deployed.
Participant Names table
Identification Type column	Displays your selection of user, group, or application role. To change your selection, click in this column to invoke a dropdown list.
Data Type column	Click your selection to invoke a dropdown list to assign a value: By Name: If your identification type is a user or group, click the Browse icon on the right to display a dialog for selecting a user or group configured through the identity service. The identity service enables the lookup of user properties, roles, and group memberships. User information is obtained from an LDAP server such as Oracle Internet Directory. You can use wild cards (*) to search for IDs. If your selection is an application role, click the Browse icon to display a dialog for selecting an application role. To search for application roles, you must first create a connection to the application server. When searching, you must specify the application name in order to find the name of the role. Note that the task definition can refer to only one application name. You cannot use application roles from different applications as assignees or task owners. By Expression: For user, group, or application role, click the Browse icon to dynamically select a task assignee in the Expression Builder dialog. Use the `bpws:getVariableData(...)` expression or the `ids:getManager()` XPath function.
Value column	Displays the value you specified with the Browse icon in the Data Type column. You can also manually enter a value in this field.
Rule-based	Enter a ruleset created with the Oracle Business Rules Designer in the List Ruleset field. In this case, the rules define parameters of the Names and Expressions list builder. A ruleset provides a unit of execution for rules and decision tables. In addition, rulesets provide a unit of sharing for rules; rules belong to a ruleset. Rulesets can push other rulesets on the ruleset stack. In rulesets, the priority of rules applies to specify the order of firing of the rules in the ruleset. Rulesets also provide an effective date specification that identifies that the ruleset is always active, or that the ruleset is restricted based on a time and date range, or a starting or ending time and date.
Build a list of participants using: (Rule-based)	Enter a rule in the List Ruleset field. In this case, rules define the list builder and the list builder parameters. The list itself is built using rules.
Let participants manually claim the task	If you select this, then the task is assigned to all participants in the list. It becomes assigned to a particular participant when that participant manually claims it.
Auto assign task to a single	Enter a rule in the List Ruleset field. In this case, rules define the list builder and the list builder parameters. The list itself is built using rules.
Limit allocated duration to	Select the amount of time a user or group receives to act on a task. If the user or group does not act in the time specified, the global escalation and renewal policies are applied. For example, if the global policy is set to escalate the task and this participant does not act in the duration specified, the task is escalated to the manager or another user, as appropriate.
Allow this participant to invite other participants	Select this checkbox if you want the task assignee to have the ability to invite other participants into the workflow before routing it to the next assignee in this workflow. For example, assume the approval workflow goes from James Cooper to John Steinbeck. If this option is checked, James Cooper can decide to first route it to Irving Stone before it goes to John Steinbeck by using the route action dialog in the task details page.
Specify skip rule	Select this checkbox if you want the user, group, or application role to be bypassed if a specific condition is satisfied. This action displays an icon for accessing the Expression Builder dialog for building a condition. For example, if a user submits a business trip expense report that is below the specific limit, no approval is required by their manager.