1. In the Task Title field of the General section, select a method for specifying a task title:

   • Plain Text: Manually enter a name (for example, Vacation Request Approved).

   • Text and XPath: Enter a combination of manual text and a dynamic expression. After manually entering a portion of the title (for example, Approval Required for Order Id:), place the cursor one blank space to the right of the text and click the icon to the right of this field. This displays the Expression Builder for dynamically creating the remaining portion of the title. After completing the dynamic portion of the name, click OK to return to this field. The complete name is displayed. For example:

     Approval Required for Order Id: <%/task:task/task:payload/task:orderId%>
     

     The expression is resolved during runtime with the exact order ID value from the task payload.

   • Translation: Click the Lookup button and locate a translation bundle to use to specify the title.

   • Resource Xpath: Click the Lookup button and locate a resource bundle to use to specify the title.

2. If you enter a title in the Task Title field of the General tab of the Create Human Task dialog box described in Specifying the Task Title, the title you enter here is overridden.

Task outcomes capture the possible outcomes of a task. Oracle BPM Worklist displays the outcomes you specify here as the possible task actions to perform during runtime. Figure 29-3 provides details.

Figure 29-3 Outcomes in Oracle BPM Worklist

Description of "Figure 29-3 Outcomes in Oracle BPM Worklist"

You can specify the following types of task outcomes:

1. To the right of the Outcomes field in the General section, click the Search icon.

   The Outcomes dialog box shown in Figure 29-4 displays the possible outcomes for tasks. APPROVE and REJECT are selected by default.

   Figure 29-4 Outcomes Dialog

   
   Description of "Figure 29-4 Outcomes Dialog"
2. Enter the information shown in Table 29-3.

   Table 29-3 Outcomes Dialog

   Field	Description
   Select one or more outcomes	Select additional task outcomes or deselect the default outcomes.
   Add icon	Click to invoke a dialog box for adding custom outcomes. In the Name field of the dialog box, enter a custom name, and click OK. Your outcome displays in the Outcomes field. Notes: Be aware of the following naming restrictions: Do not specify a custom name that matches a name listed in the Actions tab of the Access section of the Human Task Editor (for example, do not specify Delete). Specifying the same name can cause problems at runtime. Do not specify a custom name with blank spaces (for example, On Hold). This causes an error when the custom outcome is accessed in Oracle BPM Worklist. If you must specify an outcome with spaces, use a resource bundle. For more information, see Introduction to Human Workflow Services. A custom task outcome must begin with a letter of the alphabet, either upper or lower case. It should contain only letters of the alphabet and the numbers zero (0) through nine (9).
   Outcomes Requiring Comment	Click to select an outcome to which an assignee adds comments in Oracle BPM Worklist at runtime. The assignee must add the comments and perform the action without saving the task at runtime.
   Default Outcome	Select the default outcome for this outcome.

   The seeded and custom outcomes selected here display for selection in the Majority Voted Outcome section of the parallel participant type.

3. For more information, see Specifying the Voting Outcome.

1. Select a method for specifying a task category in the Category field of the General section:

   • By Name: Manually enter a name.

   • By Expression: Click the icon to the right of this field to display the Expression Builder for dynamically creating a category.

   • Translation: If the composite contains a resource bundle file, then use the Lookup button to locate the resource bundle file and to specify a category.

1. Select a method for specifying the task owner:

   • Statically through the identity service user directory or the list of application roles

   • Dynamically through an XPath expression

     For example: If the task has a payload message attribute named po within which the owner is stored, you can specify an XPath expression such as:

     /task:task/task:payload/po:purchaseOrder/po:owner

     ids:getManager('jstein', 'jazn.com')

     The manager of jstein is the task owner.

1. Click the Data tab.
2. Click the Add icon and select a payload type:

   • String

   • Integer

   • Boolean

   • Other

   The Add Task Parameter dialog box is displayed, as shown in Figure 29-14.

   Figure 29-14 Add Task Parameter Dialog

   
   Description of "Figure 29-14 Add Task Parameter Dialog"
3. Enter the details described in Table 29-5:

   Table 29-5 Add Task Parameter Dialog Fields and Values

   Field	Description
   Parameter Type	Select Type or Element and click the Search icon to display the Type Chooser dialog box for selecting the task parameter.
   Parameter Name	Accept the default name or enter a custom name. This field only displays if Type is the selected parameter type.
   Editable via worklist	Select this check box to enable users to edit this part of the task payload in Oracle BPM Worklist. For example, for a loan approval task, the APR attribute may need to be updated by the user reviewing the task, but the SSN field may not be editable. You can also specify access rules that determine the parts of a task that participants can view and update. For more information, see Specifying Access Policies and Task Actions on Task Content.
   Use Collections	If a task uses collections, then define this parameter to use collections. Click the Add button to provide the collection name and the Xpath expression for the collection type. Use Expression Builder to look up the collection type from the schema.

   Note:

   You can only define payload mapped attributes (previously known as flex field mappings) in Oracle BPM Worklist for payload parameters that are simple XML types (string, integer, and so on) or complex types (for example, a purchase order, and so on). If you must search tasks using keywords or define views or delegation rules based on task content, then you must use payload parameters based on simple XML types. These simple types can be mapped to flex columns in Oracle BPM Worklist.

4. Select the type, as shown in Figure 29-15.

   Figure 29-15 Parameter Type

   
   Description of "Figure 29-15 Parameter Type"
5. Click OK to return to the Human Task Editor.

   Your selection displays in the Data section.

6. To edit your selection, select it and click the Edit icon in the upper right part of the Data section.

1. Double-click the name. The Edit dialog box displays.
2. In the Edit dialog box, enter the following details and click OK.

   • Stage: The name of the stage.

   • Non Repeating: Do not stage in parallel for each item in the collection.

   • Repeat Stage in parallel for each item in a collection: Choose one collection from the drop-down list to specify which collection type to use for the repeated stages.

3. Drag and drop the type of participant from the Participant palette on the right onto the stage.
4. Drag Stage from the Participant Palette on the right and drop it on the green dot of the existing stage.

   When you bring the new stage closer to the current stage, four green dots display around the current stage. Choose the green dot that is to right to the current stage. A second stage is added in parallel to the first stage, as shown in Figure 29-17.

   Figure 29-17 Parallel Stage

   
   Description of "Figure 29-17 Parallel Stage"
5. Drag Stage from the Participant Palette on the right and drop it on the green dot of the existing stage

   When you bring the new stage below the current stage, four green dots display around the current stage. Choose the green dot that is below the current stage.

   A sequential stage is added below the selected block.

   Figure 29-18 Sequential Stage

   
   Description of "Figure 29-18 Sequential Stage"

   You create participant types within these blocks.

1. In the Assignment section, perform one of the following tasks:

   • Drag and drop Participants from the Components window onto Stage. The first time you create a task participant, the box is labeled <Edit Participant>.

   • Double-click the participant box.

   The Edit Participant Type dialog box appears. This dialog box enables you to select a specific participant type.

2. From the Type list, select a participant type shown in Figure 29-19.

   Figure 29-19 Type List

   
   Description of "Figure 29-19 Type List"
3. See the section shown in Table 29-6 based on your selection.

   Table 29-6 Participant Types

   Participant Type	For a Description of this Participant Type, See...	For Instructions on Configuring this Participant Type, See...
   Single Parallel Serial FYI	Task Assignment and Routing	How to Configure the Single Participant Type How to Configure the Parallel Participant Type How to Configure the Serial Participant Type How to Configure the FYI Participant Type

Figure 29-20 shows the Edit Participant Type dialog box for the single participant type. Figure 29-21 shows the expanded Advanced section.

Figure 29-20 Edit Participant Type — Single Type

Description of "Figure 29-20 Edit Participant Type — Single Type"

Figure 29-21 Edit Participant Type — Advanced Tab

Description of "Figure 29-21 Edit Participant Type — Advanced Tab"

To be dynamically assigned to a task, a single participant can be selected from a group, an application role, or a participant list.

1. In the Label field, enter a recognizable label for this participant. This label must be unique among all the participants in the task definition (for example, Approval Manager, Primary Reviewers, and so on).

   Instructions for configuring the following subsections of the Edit Participant Type dialog box for the single participant type are listed in Table 29-7:

   Table 29-7 Edit Participant Type — Single Type

   For This Subsection...	See...
   Participant List	Creating a Single Task Participant List
   Limit allocated duration to (under the Advanced section)	Specifying a Time Limit for Acting on a Task
   Allow this participant to invite other participants (under the Advanced section)	Inviting Additional Participants to a Task
   Specify skip rule (under the Advanced section)	Bypassing a Task Participant
   Assignment Control (under the Advanced section)	If this participant is associated with a particular assignment context, then add that name here. Use the Add button to add new entry. Use the drop-down list to select the assignment context Name and provide a value for this assignment context.
   Let participants manually claim task (under the General section)	Creating Participant Lists Consisting of Value-Based Names and Expressions
   Auto assign task to a single user/group/application role (under the General section)	Creating Participant Lists Consisting of Value-Based Names and Expressions

The parallel participant type is used when multiple users, working in parallel, must act simultaneously, such as in a hiring situation when multiple users vote to hire or reject an applicant. You specify the voting percentage that is needed for the outcome to take effect, such as a majority vote or a unanimous vote. In case of parallel routing with parallel participants, the voting and the percentage rule takes precedence to decide the final outcome of the parent task.

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.

Figure 29-32 and Figure 29-33 display the upper and lower sections of the Parallel dialog box.

Figure 29-32 Edit Participant Type — Parallel Type (Upper Section of Dialog)

Description of "Figure 29-32 Edit Participant Type — Parallel Type (Upper Section of Dialog)"

Figure 29-33 Edit Participant Type — Parallel Type (Lower Section of Dialog)

Description of "Figure 29-33 Edit Participant Type — Parallel Type (Lower Section of Dialog)"

1. In the Label field, enter a recognizable label for this participant. This label must be unique among all the participants in the task definition (for example, Approval Manager, Primary Reviewers, and so on).

   Instructions for configuring the following subsections of the Edit Participant Type dialog box for the parallel participant type are listed in Table 29-8:

   Table 29-8 Edit Participant Type — Parallel Type

   For This Subsection...	See...
   Vote Outcome	Specifying the Voting Outcome
   Participant List	Creating a Parallel Task Participant List
   Limit allocated duration to (under the Advanced section)	Specifying a Time Limit for Acting on a Task
   Allow this participant to invite other participants (under the Advanced section)	Inviting Additional Participants to a Task
   Specify skip rule (under the Advanced section)	Bypassing a Task Participant
   Add Assignment Context (under the Advanced section)	If this participant is associated with a particular assignment context, then add that name here. Use the Add button to add a new entry. Use the drop-down list to select an assignment context Name and to provide a value for this assignment context.

This participant type enables you to create a list of sequential participants for a workflow. For example, if you want a document to be reviewed by John, Mary, and Scott in sequence, use this participant type. For the serial participant type, they can be any list of users or groups.

Figure 29-35 displays the Serial dialog box. Figure 29-36 shows the expanded Advanced section.

Figure 29-35 Edit Participant Type — Serial Type

Description of "Figure 29-35 Edit Participant Type — Serial Type"

Figure 29-36 Edit Participant Type — Serial Type (Advanced Tab)

Description of "Figure 29-36 Edit Participant Type — Serial Type (Advanced Tab)"

1. In the Label field, enter a recognizable label for this participant. This label must be unique among all the participants in the task definition (for example, Approval Manager, Primary Reviewers, and so on).

   Instructions for configuring the following subsections of the Edit Participant Type dialog box for the serial participant type are listed in Table 29-9.

   Table 29-9 Edit Participant Type — Serial Type

   For This Subsection...	See...
   Participant List	Creating a Serial Task Participant List
   Limit allocated duration to (under the Advanced section)	Specifying a Time Limit for Acting on a Task Note that if you specify the task expiry time at the level of a serial participant, then, when that time expires, the task does not move to the next participant in the series. Rather, the entire task expires.
   Allow this participant to invite other participants (under the Advanced section)	Inviting Additional Participants to a Task
   Specify skip rule (under the Advanced section)	Bypassing a Task Participant
   Assignment Context (under the Advanced section)	If this participant is associated with a particular assignment context, then add that name here. Use the Add button to add a new entry. Use the drop-down list to select assignment context Name and to provide a value for this assignment context.

This participant type is used when a task is sent to a user, but the business process does not wait for a user response; it just continues. FYIs cannot directly impact the outcome of a task, but in some cases can provide comments or add attachments.

For example, a magazine subscription is due for renewal. If the user does not cancel the current subscription before the expiration date, the subscription is renewed. This user is reminded weekly until the request expires or the user acts on it.

Figure 29-37 displays the Edit Participant Type dialog box for the FYI type. This dialog box also includes a Participants Exclusion List at the bottom that is not displayed in Figure 29-37.

Figure 29-37 Edit Participant Type — FYI Type

Description of "Figure 29-37 Edit Participant Type — FYI Type"

To configure the FYI participant type, in the Label field, enter a recognizable label for this participant. This label must be unique among all the participants in the task definition (for example, Approval Manager, Primary Reviewers, and so on).

Use advanced routing rules to create complex workflow routing scenarios. The participant types (single, parallel, serial, and FYI) are used to create a linear flow from one set of users to another with basic conditions such as abrupt termination, skipping assignees, and so on. However, there is often a need to perform more complex back and forth routing between multiple individuals in a workflow. One option is to use the BPEL process as the orchestrator of these tasks. Another option is to specify it declaratively using business rules. This section describes how you can model such complex interactions by using business rules with the Human Task Editor.

1. Drag and drop External Routing Service from the Workflow Editor Components window.

   The Use External Routing edit box displays.

2. Click the Edit icon.

   The External Routing dialog box appears, as shown in Figure 29-45.

   Figure 29-45 Use External Routing Dialog

   
   Description of "Figure 29-45 Use External Routing Dialog"
3. In the Class Name field, enter the fully qualified class file name (for example, the org.mycompany.tasks.RoutingService class name). This class must implement the following interface:

   oracle.bpel.services.workflow.task.IAssignmentService
   

4. Add name and pair value parameters by name or XPath expression that can be passed to the external service, as shown in Table 29-14.

   Table 29-14 External Routing

   Field	Description
   By Name	Enter a name in the Name field and a value in the Value field.
   By Expression	Enter a name and dynamically enter a value by clicking the icon to the right of the field to display the Expression Builder dialog box.

5. Click the Add icon to add additional name and pair value parameters.

1. Click the Add icon to assign reviewers or error assignees, as shown in Figure 29-46.

   Figure 29-46 Error Assignment Details

   
   Description of "Figure 29-46 Error Assignment Details"
2. Click the Add icon and select a user, group, or application role to participate in this task.

   The Identification Type column of the Starting Participant table displays your selection of user, group, or application role.

3. See Step 5 through 7 of Creating a Single Task Participant List for instructions on selecting a user, group, or application role.
4. If you are using parallel participant types, you can specify where to store the subtask payload with the following options.

   • Use server settings

     The SharePayloadAcrossAllParallelApprovers System MBean Browser boolean property in Oracle Enterprise Manager Fusion Middleware Control determines whether to share the payload of subtasks in the root task. By default, this property is set to true. If set to true, the All task participants share the same payload (better performance and less storage space) option is used. If this property is set to false, the Each parallel participant has a local copy of the payload option is used. To change the settings, see How to Change Server Settings.

   • All task participants share the same payload (better performance and less storage space)

     The payload for the subtasks is stored in their root task. This situation means that the payload of the root task is shared across all its subtasks. Internally, this option provides better performance and storage space consumption. Less storage space is consumed because the payload of the root task is shared across all its subtasks.

   • Each parallel participant has a local copy of the payload

     Each subtask has its own copy of the payload. Internally, this option provides lesser performance and storage space consumption because more storage space is consumed.

5. Click OK.

1. In the Stylesheet for Attachments list of the Presentation section, select one of the following options:

   • Word ML: This option dynamically creates Microsoft Word documents for sending as email attachments using a WordML XSLT style sheet. The XSLT style sheet is applied on the task document.

   • Other: This option creates email attachments using an XSLT style sheet. The XSLT style sheet is applied on the task document.

2. Click the Search icon to select the style sheet as an attachment.

1. In the Presentation section, click the Add icon across from Resource Bundle.

   The Resource Details dialog box shown in Figure 29-48 appears.

   Figure 29-48 Resource Details Dialog

   
   Description of "Figure 29-48 Resource Details Dialog"
2. In the Resource Name field, enter the name of the resource used in the resource bundle. This should be a .properties-based resource bundle file.
3. In the Resource Location field, click the Search icon to select the JAR or ZIP resource bundle file to use. The resource bundle is part of your system archive (SAR) file.

   If the resource bundle is outside of the composite project, you are prompted to place a local copy in SCA-INF/lib.

   If the resource bundle file is not in the composite class loader (directly under SCA-INF/classes or in a JAR file in SCA-INF/lib), you must specify its location. For example, if the resource bundle is accessible from a location outside of the composite class loader (for example, an HTTP location such as http://host:port/bundleApp/taskBundles.jar), then this location must be specified in this field.

4. Click OK to return to the Human Task Editor.

   For more information, see How to Configure Notification Messages in Different Languages.

This section provides an overview of how specifying the expiration duration at this level makes this setting the expiration duration of the task across all the participants.

For example, participant LoanAgentGroup and participant Supervisor have three days to act on the task between them, as shown in Figure 29-50:

Figure 29-50 Expire After Policy

Description of "Figure 29-50 Expire After Policy"

If there is no expiration specified at either the participant level or this routing slip level, then that task has no expiration duration.

If expiration duration is specified at any level of the participants, then for that participant, the participant expiration duration is used. However, the global expiration duration is still used for the participants that do not have participant level expiration duration. The global expiration duration is always decremented by the time elapsed in the task.

The policy for interpreting the participant level expiration for the participants is described as follows:

• Serial

  Each assignment in the management chain gets the same expiration duration as the one specified in the serial. The duration is not for all the assignments resulting from this assignment. If the task expires at any of the assignments in the management chain, the escalation and renewal policy is applied.

• Parallel:

  • In a parallel workflow, if the parallel participants are specified as a resource, a routing slip is created for each of the resources. The expiration duration of each created routing slip follows these rules:

    The expiration duration equals the expiration duration of the parallel participant if it has an expiration duration specified.

    The expiration duration that is left on the task if it was specified at the routing slip level.

    Otherwise, there is no expiration duration.

  • If parallel participants are specified as routing slips, then the expiration duration for the parallel participants is determined by the routing slip.

1. In the drop-down list of the Deadlines section, select Expire after, as shown in Figure 29-51.
2. Specify the maximum time period for the task to remain open.

   The expiration policy for parallel participants is interpreted as follows:

   • If parallel participants are specified as resources in parallel elements, there is no expiration policy for each of those participants.

   • If parallel participants are specified as routing slips, then the expiration policy for the routing slip applies to the parallel participants.

   Figure 29-51 indicates that the task expires in three days.

   Figure 29-51 Expire After Policy

   
   Description of "Figure 29-51 Expire After Policy"

   Note:

   The escalation time is limited to future times that are before the year 2286. Using a value that is greater results in runtime errors. The technical limit of the future value is 9,999,999,999,999 milliseconds since January 1, 1970, 00:00:00 GMT.

1. In the drop-down list of the Deadlines section, select Renew after, as shown in Figure 29-52.
2. Specify the maximum number of times to continue renewing this task.

   In Figure 29-52, when the task expires, it is renewed at most three times. It does not matter if the task expired at the LoanAgentGroup participant or the Supervisor participant.

   Figure 29-52 Renew After Policy

   
   Description of "Figure 29-52 Renew After Policy"

1. In the drop-down list of the Deadlines section, select Escalate after, as shown in Figure 29-53.
2. Specify the following additional values. When both are set, the escalation policy is more restrictive.

   • Maximum Escalation Levels

     Number of management levels to which to escalate the task. This field is required.

   • Highest Approver Title

     The title of the highest approver (for example, self, manager, director, or CEO). These titles are compared against the title of the task assignee in the corresponding user repository. This field is optional.

   The escalation policy specifies the number of times the task can be escalated on expiration and the renewal duration. In Figure 29-53, when the task expires, it is escalated at most three times. It does not matter if the task expired at the LoanAgentGroup participant or the Supervisor participant.

   Figure 29-53 Escalate After Policy

   
   Description of "Figure 29-53 Escalate After Policy"

1. Implement the following interface:

   oracle.bpel.services.workflow.assignment.dynamic.IDynamicTaskEscalationFunction
   

   This implementation must be available in the class path for the server.

2. Log in to Oracle Enterprise Manager Fusion Middleware Control.
3. Expand the SOA folder in the navigator.
4. Right-click soa-infra, and select SOA Administration > Workflow Config > Task tab.

   The Workflow Task Service Properties page appears.

5. Add a new function. For example:

   • Function name: DepartmentSupervisor

   • Classpath: oracle.bpel.services.workflow.assignment.dynamic.patterns.DepartmentSupervisor

   • Function parameter name

   • Function parameter value

6. In the Custom Escalation Java Class field of the Deadlines section, enter the function name as defined in the Workflow Task Service Properties page for the escalation rule.

   For more information, see Custom Escalation Function.

1. In the Deadlines section, select the Action Requested Before check box.
2. Select By Duration to enter a time duration or select By Expression to dynamically enter a value as an XPath expression.

   Note the following details:

   • The due date can be set on both the task (using the Create ToDo Task dialog box in Oracle BPM Worklist) and in the .task file (using the Human Task Editor). This is to allow to-do tasks without task definitions to set a due date during initiation of the task. A due date that is set in the task (a runtime object) overrides a due date that is set in the .task file.

   • In the task definition, the due date can only be specified at the global level, and not for each participant.

   • If the due date is set on the task, the due date in the .task file is ignored.

   • If the due date is not set on the task, the due date in the .task file is evaluated and set on the task.

   • If there is no due date on either the task or in the .task file, there is no due date on the task.

1. Click the Notification tab.
2. Select one of the Task Status types from the list:

   • Alerted

     When a task is in an alerted state, you can notify recipients. However, none of the notification recipients (assignees, approvers, owner, initiator, or reviewer) can move the task from an alerted state to an error state; they only receive an FYI notification of the alerted state. The owner can reassign, withdraw, delete, or purge the task, or ask the error assignee to move the task to an error state if the error cannot be resolved. Only the error assignee can move a task from an alerted state to an error state.

     You configure the error assignee on the Assignment tab of the Configure Assignment dialog box under the Task will go from starting to final participant icon in the Assignment section. For more information, see How to Configure the Error Assignee and Reviewers.

   • Assign

     When the task is assigned to users or a group. This captures the following actions:

     • Task is assigned to a user

     • Task is assigned to a new user in a serial workflow

     • Task is renewed

     • Task is delegated

     • Task is reassigned

     • Task is escalated

     • Information for a task is submitted

   • Complete

   • Error

   • Expire

   • Request Info

   • Resume

   • Suspend

   • Update

     • Task payload is updated

     • Task is updated

     • Comments are added

     • Attachments are added and updated

   • Update Outcome

   • Withdraw

   • All Other Actions

     • Any action not covered in the above task types. This includes acquiring a task.

   Notifications can be sent to users involved in the task in various capacities. This includes when the task is assigned to a group, each user in the group is sent a notification if there is no notification endpoint available for the group.

3. Select the recipient from the Recipient from the list of possible recipients for the notification message for the Task Status type:

   • Assignees

     The users or groups to whom the task is currently assigned.

   • Initiator

     The user who created the task.

   • Approvers

     The users who have acted on the task up to this point. This applies in a serial participant type in which multiple users have approved the task and a notification must be sent to all of them.

   • Owner

     The task owner

   • Reviewer

     The user who can add comments and attachments to a task.

   For more information, see How to Configure the Notification Channel Preferences.

4. Save the changes.

   Note:

   To configure notifications for additional Task Status types, click the + icon above the Task Status section and to remove notification for a Task Status type, select the task status row and click the X icon.

1. In the Notification section, click the General tab.
2. In the Notification Header column, click the Edit icon to modify the default notification message.

   The Edit Notification Message dialog box shown in Figure 29-56 appears.

   Figure 29-56 Edit Notification Message Dialog

   
   Description of "Figure 29-56 Edit Notification Message Dialog"

   This message applies to all the supported notification channels: email, instant messaging (IM), and SMS. Email messages can also include the worklist task detail defined in this message. The channel by which the message is delivered is based upon the notification preferences you specify.

3. Modify the message wording as necessary.
4. Click OK to return to the Human Task Editor.

1. In the Notification section, click the Advanced tab.
2. From the list, select the number of reminders to send.
3. If you selected to remind the assignee one, two, or three times, select the interval between reminders, and whether to send the reminder before or after the assignment.

1. In the Notification section, click the Advanced tab.
2. From the Encoding list, select Specify by Java Class.
3. Enter the Java class to use.

1. In the Notification section, click the Advanced tab.
2. Select Make notifications secure (exclude details).

   If selected, a default notification message is used. There are no HTML worklist task details, attachments, or actionable links in the email. Only the task number is in the message.

   For more information, see How to Send Secure Notifications.

1. In the Notification section, click the Advanced tab.
2. Select the Show worklist URL in notifications check box to display the Oracle BPM Worklist URL in email notification messages. If this check box is not selected, the URL is not displayed.

1. In the Notification section, click the Advanced tab.
2. Select Make notification actionable. This action enables you to perform task actions through email.

   Note:

   FYI tasks are not actionable and cannot be acknowledged from email messages.

   For more information about additional configuration details, see How to Send Actionable Messages.

   For more information about configuring outbound and inbound emails, see Administering Oracle SOA Suite and Oracle Business Process Management Suite.

1. In the Notification section, click the Advanced tab.
2. Select Send task attachments with email notifications.

1. In the Notification section, click the Advanced tab.
2. From the Group notification configuration list, select one of the following options.

   • Send individual emails

     Each user in the group or application role receives an individual email notification. This is the default selection.

     In addition, the Use separate task forms based on locale check box is automatically selected. When selected, this sends individual emails with a separate task form based on the language locale. When not selected, this sends individual emails and reuses (shares) the task form.

   • Send one email containing all user addresses

     A shared notification email is generated once for a user locale in a group or application role, thereby saving time in notification email content generation. The email is sent to all users in the group or application role.

     Note:

     • Since all (or a subset of) users receive the same email, the users in the group or application role are expected to have the same privilege. This ensures that the user does not see task details to which they are not entitled.

     • When sending one email to all users, the maximum number of characters allowed in the address field is 2000. If the limit is exceeded, email is sent to only those user addresses contained within the maximum limit.

1. In the Notification section, click the Advanced tab.
2. Expand Notification Header Attributes.
3. Add name and pair value parameters by name or XPath expression.

   For more information about preferences, see the following sections:

   • How to Send Inbound and Outbound Attachments

   • How to Create Custom Notification Headers

   • Developing Applications with Oracle User Messaging Service

Access rules are computed based on the following details:

• Any attribute configured with access rules declines any permissions for roles not configured against it. For example, assume you configure the payload to be read by assignees. This action enables only assignees and nobody else to have read permissions. No one, including assignees, has write permissions.

• Any attribute not configured with access rules has all permissions.

• If any payload message attribute is configured with access rules, any configurations for the payload itself are ignored due to potential conflicts. In this case, the returned map by the API does not contain any entry for the payload. Write permissions automatically provide read permissions.

• If only a subset of message attributes is configured with access rules, all message attributes not involved have all permissions.

• Only comments and attachments have add permissions.

• Write permissions on certain attributes are meaningless. For example, write permissions on history do not grant or decline any privileges on history.

• The following date attributes are configured as one in the Human Task Editor. The map returned by TaskMetadataService.getVisibilityRules() contains one key for each. Similarly, if the participant does not have read permissions on DATES, the task does not contain any of the following task attributes:

  • START_DATE

  • END_DATE

  • ASSIGNED_DATE

  • SYSTEM_END_DATE

  • CREATED_DATE

  • EXPIRATION_DATE

  • ALL_UPDATED_DATE

• The following assignee attributes are configured as one in the Human Task Editor. The map returned by TaskMetadataService.getVisibilityRules() contains one key for each of the following. Similarly, if the participant does not have read permissions on ASSIGNEES, the task does not contain any of the following task attributes:

  • ASSIGNEES

  • ASSIGNEE_USERS

  • ASSIGNEE_GROUPS

  • ACQUIRED_BY

• Mapped attributes do not have individual representation in the map returned by TaskMetadataService.getVisibilityRules().

• All message attributes in the map returned by TaskMetadataService.getVisibilityRules() are prefixed by ITaskMetadataService.TASK_VISIBILITY_ATTRIBUTE_PAYLOAD_MESSAGE_ATTR_PREFIX (PAYLOAD).

An application can also create pages to display or not display task attributes based on the access rules. This can be achieved by retrieving a participant's access rules by calling the API on oracle.bpel.services.workflow.metadata.ITaskMetadataService. as shown in the example below:

public Map<String, IPrivilege> getTaskVisibilityRules(IWorkflowContext context,
                                      String taskId)
   throws TaskMetadataServiceException;

For more information about this method, see Workflow Services Java API Reference for Oracle SOA Suite.

1. Click the Access tab.
2. Click the Content tab.
3. Select the task content for which to specify access privileges, as shown in Figure 29-57.

   Figure 29-57 Configure Task Content Access

   
   Description of "Figure 29-57 Configure Task Content Access"
4. Assign privileges (read, write, or no access) to users to act upon task content. A user cannot be assigned a privilege above their highest level. For example, an ADMIN user cannot be assigned write access on the PAYLOAD task content. Table 29-17 shows the maximum privilege each user has on task content.

   Table 29-17 Highest Privilege Levels for Users of Task Content

   Task Content	Individual with Read Access	Individual with Write Access
   Assignees	Admin, Approvers, Assignees, Creator, Owner, Reviewers	--
   Attachments	Admin, Approvers	Assignees, Creator, Owner, Reviewers
   Comments	Admin, Approvers	Assignees, Creator, Owner, Reviewers
   Dates	Admin, Approvers, Assignees, Creator, Owner, Reviewers	--
   Flexfields	Admin, Approvers, Reviewers	Assignees, Creator, Owner
   History	Admin, Approvers, Assignees, Creator, Owner, Reviewers	--
   Payload	Admin, Approvers, Reviewers	Assignees, Creator, Owner
   Reviewers	Admin, Approvers, Assignees, Creator, Owner, Reviewers	--
   Payload elements	Inherited from payload	Inherited from payload

   For example, if you accept the default setting of ASSIGNEES, CREATOR, and OWNER with write access, ADMIN, APPROVERS, and REVIEWERS with read access, and PUBLIC with no access to the PAYLOAD task content, the dialog box appears as shown in Figure 29-57.

5. Select the method for displaying task content in this dialog box. Choosing the currently unselected option causes all settings to reset to their default values.

   • Coarse grained (default)

     Displays the task content as a whole (for example, displays only one payload or reviewer).

   • Fine grained

     Displays the content as individual elements (for example, displays all payloads (such as p1, p2, and p3) and all reviewers assigned to this task (such as jstein, wfaulk, and cdickens).

1. Click the Access tab.
2. Click the Actions tab.
3. Select the task action for which to specify users, as shown in Figure 29-58.

   Figure 29-58 Selection of Add Action Access Rule

   
   Description of "Figure 29-58 Selection of Add Action Access Rule"
4. Select if participants can or cannot perform the selected actions.
5. Select the method for displaying task actions in this dialog box. Choosing the currently unselected option causes all settings to reset to their default values.

   • Coarse grained (default)

     Displays the task actions as a whole (for example, displays only one approval or rejection).

   • Fine grained

     Displays the content actions as individual elements. (for example, displays all approvals or rejections).

1. Click the Access tab.
2. From the Signature Policy list, select Configure Policy, as shown in Figure 29-59.

   Figure 29-59 Digital Signatures

   
   Description of "Figure 29-59 Digital Signatures"
3. Specify the signature policy for task participants to use:

   • No signature required

     Participants can send and act upon tasks without providing a signature. This is the default policy.

   • Password required

     Participants specify a signature before sending tasks to the next participant. Participants must reenter their password while acting on a task. The password is used to generate the digital signature. A digital signature authenticates the identity of the message sender or document signer. This ensures that the original content of the sent message is unchanged.

   • Digital certificate required

     Participants must possess a digital certificate for the nonrepudiation of digitally-signed human tasks. A digital certificate establishes the participant's credentials. It is issued by a certification authority (CA). It contains the name, a serial number, expiration dates, a copy of the certificate holder's public key (used for encrypting messages and digital signatures), digital signature of the certificate-issuing authority so that message authenticity can be established

     The CA names and CA CRL and URLs of the issuing authorities must be configured separately.

4. Click OK.

1. In the Access section, click Configure Restricted Assignments.

   The Configure Restricted Assignment dialog box appears.

2. Enter the class name. The class must implement the oracle.bpel.services.workflow.task.IRestrictedAssignmentCallback interface.
3. Click the Add icon to add name and value pairs for the property map passed to invoke the callback.
4. Click OK.

1. In the State column of the Events section, select a task state. Leave the Java Class field empty.
2. Select the Trigger Workflow Event check box. This action disables the Java Class column, as shown in Figure 29-61. Each callback, such as OnAssigned, corresponds to a business event point. When a business event is fired, the event details contain the task object and a set of properties that are populated based on the context of the event being fired.

   Figure 29-61 CallBack Details Dialog with Business Events Selected

   
   Description of "Figure 29-61 CallBack Details Dialog with Business Events Selected"

   A pre-seeded, static event definition language (EDL) file (JDev_Home\jdeveloper\integration\seed\soa\shared\workflow\HumanTaskEvent.edl) provides the list of available business events to which to subscribe. These business events correspond to the callbacks you select in the Callback Details dialog box. You must now create an Oracle Mediator service component in which you reference the EDL file and subscribe to the appropriate business event.

   Note:

   A file-based MDS connection is required so that the EDL file can be located. The location for the file-based MDS is JDev_Home\jdeveloper\integration\seed.

3. Create an Oracle Mediator service component in the same or a different SOA composite application that can subscribe to the event.
4. In the Template list during Oracle Mediator creation, select Subscribe to Events.
5. Click the Add icon to subscribe to a new event.
6. To the right of the Event Definition field, click the Browse icon to select the EDL file.

   The SOA Resource Browser dialog box appears.

7. Select the previously created file-based MDS connection.
8. From the list at the top, select Resource Palette.
9. Select SOA > Shared > Workflow > HumanTaskEvent.edl.

   Click OK.

   The Event Chooser is now populated with EDL file business events available for selection.

10. In the Event field, select the event to which to subscribe. Figure 29-62 provides details.

    Figure 29-62 Event Callbacks

    
    Description of "Figure 29-62 Event Callbacks"

    You can have multiple human tasks available for subscribing to the event. For example, assume you performed the following:

    • Configured a human task named TaskA to subscribe to the event (for example, OnAssigned)

    • Configured a human task named TaskB to subscribe to the same event

    To distinguish between events for TaskA and TaskB and ensure that an event is processed only by the intended Oracle Mediator, you can add a static routing filter:

    xpath20:compare(med:getComponentName(), 'TaskA')
    

    This only invokes this routing when the sending component is TaskA.

11. If the EDL file was not selected from the file-based MDS connection, accept to import the dependent XSD files when prompted, and click OK. If the EDL file was selected from the file-based MDS connection, you are not prompted.

    The Oracle Mediator service component is now populated with the business event to which to subscribe. You can also subscribe to other business events defined in the same EDL file now or at a later time.

1. In the Events section, select the Allow task and routing customization in BPEL callbacks check box.
2. Return to Oracle BPEL Designer.
3. Open the task activity dialog box.
4. Click OK.

1. In the Events section, deselect the Disable BPEL callbacks check box.
2. Click OK.