Edit Participant Type Dialog

3.28 Edit Participant Type Dialog - Single Page

Use to configure the single approver participant type.

This participant type requires a single user to act on a task. If the task is assigned to a role or group with multiple users, one of the members must claim the task and act on it. Based on the user's action, you define what the business process does.

For example, a vacation request is assigned to a manager. The manager must act on the request task within three days of the assignment. Once the manager approves or rejects the request, the single approver is finished and the task is marked as completed.

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.
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.
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. The Participant Names table contains the following columns: Identification Type: Displays your selection of user, group, or application role. To change your selection, click in this column to invoke a dropdown list. Data Type: 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: 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: (Management Chain)	Select Management Chain 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.
Auto assign task to a single	Select User, Group, or Application Role.
Value-based	Click the Add icon to assign a user, group, or application role to participate in this task. The Starting Participant table contains the following columns: Identification Type: See the online help for the Build a list of participants using: (Names and expressions) field of the single participant type for a description. Data Type: See the online help for the Build a list of participants using: (Names and expressions) field of the single participant type for a description. Value: See the online help for the Build a list of participants using: (Names and expressions) field of the single participant type for a description. Top Participant: Select a method for assigning a top participant: By Title: Select the title of the last (highest) approver in the management chain. XPath: Select to dynamically enter a top participant through the Expression Builder dialog. Number of Levels: Select a method for assigning the number of task participant levels: XPath: Select to dynamically enter a level through the Expression Builder dialog. By Number: Enter a value for the number of levels in the management chain to include in this task. For example, if you enter 2 and the task is initially assigned to user jcooper, both the user `jstein` (manager of `jcooper`) and the user `wfaulk` (manager of `jstein`) are included in the list (apart from `jcooper`, the initial assignee).
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 Management Chain 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	Select User, Group, or Application Role.
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 a specific amount, no approval is required by their manager.