|Oracle® BPEL Process Manager Developer's Guide
Part Number B28981-03
This appendix provides an overview of changes to workflow services between releases 10.1.2 and 10.1.3.1.
This appendix contains the following topics:
"Oracle BPEL Process Manager Workflow Services 10.1.2 and 10.1.3.1.0 Compatibility" for additional details
Oracle BPEL Process Manager Installation Guide for additional details about migrating projects that use the workflow service
Workflows designed with the workflow wizard in 10.1.2 can be deployed and run in 10.1.3.1. You just have to redeploy the process. However, the instance tables for 10.1.2 and 10.1.3.1 are different. Therefore, 10.1.2 items do not show up in the 10.1.3.1 Oracle BPEL Worklist Application. To access tasks created from 10.1.2 processes, visit the old Oracle BPEL Worklist Application at
The identity service configuration file must be modified as described "Migrating Workflow Definitions from 10.1.2 to 10.1.3.1". This modification is required even if you do not make any changes to your 10.1.2 processes. If you want to use any new 10.1.3.1 workflow features, you must manually migrate the process to use the 10.1.3 task definition. The changes to the task editor, form deployment, worklist, and configuration files are documented in later sections of this appendix.
For release 10.1.3.1, the Workflow Wizard that you used to design workflows in previous releases has been replaced with the Human Task Editor. You can still deploy 10.1.2 processes that include workflow functionality from Oracle JDeveloper. However, you cannot edit these workflows with the Human Task Editor. To use the 10.1.3.1 functionality, you must manually migrate the workflow task scope and recreate the human task.
Table E-1 describes the functionality of the 10.1.2 Workflow Wizard pages and the location of this functionality in the Human Task Editor.
Table E-1 Location of Workflow Wizard Functionality in 10.1.3.1
|10.1.2 Workflow Wizard Page||Location in 10.1.3.1 Human Task Editor||See Section|
|Welcome — For creating a workflow model, performing advanced task configuration, and extending the functionality of an existing workflow
Note: The pages that display if you select advanced task configuration are described later in this table.
|To create a human task:
To extend an existing workflow:
|"Accessing the Human Task Editor" to create a human task
"Including the Task History of Other Human Tasks" to extend an existing workflow
|Workflow Pattern — For selecting a workflow pattern to design, specifying a workflow name, and specifying a variable name
Note: Workflow patterns are known as participant types in 10.1.3.1.
|To select a workflow pattern to design.
To specify a workflow name:
To specify a variable name:
|"Assigning Task Participants" to select a workflow pattern to design
"Accessing the Human Task Editor" or "Associating a Human Worklist Task with a BPEL Process" to specify a workflow name
"Specifying Task Parameters" to specify a variable name
|Task Notifications — For selecting the status for sending a notification message to a recipient||
||"Specifying Participant Notification Preferences"
|Task Details — For selecting task details such as task title, payload, payload display format, task creator, and expiration duration||To specify a task title:
To specify a payload:
To specify a payload display format:
To specify a task creator:
To specify the expiration duration:
|"Specifying a Task Title and Priority" or "Specifying the Task Title" to specify a task title
"Specifying the Task Payload Data Structure" to specify a payload
"Selecting a Task Display Form" to specify a payload display format
"Specifying the Task Initiator and Task Priority" to specify a task creator
"Specifying a Time Limit for Acting on a Task" to specify the expiration duration for a single approver
"Specifying a Time Limit for Acting on a Task" to specify the expiration duration for a group vote
"Specifying a Time Limit for Acting on a Task" to specify the expiration duration for a management chain
"Specifying a Time Limit for Acting on a Task" to specify the expiration duration for a sequential list of approvers
|Task Outcomes — For selecting a possible outcome for the task||
||"Specifying a Task Outcome"
|Assignees — For manually or dynamically selecting the user or group to whom to assign a task||
||"Assigning Participants to the Single Approver Task"
|Escalation policy — For selecting the method for escalating a task||
||"Overview or Escalation and Expiration Policy" and "Escalate After Policy"|
|Renewal policy — For selecting a task renewal policy||
||"Renew After Policy"
|Assignment policy — For selecting if a specific person or a specific number of people must act on the task. This lets you route tasks to multiple users in a sequence||
||"Assigning Participants to the Sequential List of Approvers Task"
|Routing policy — For selecting the method by which to route the task||
||"Notifying Recipients of Changes to Task Status"
|Outcome determination policy — For selecting a task outcome policy, such as the percentage for final outcome, default outcome, and early completion configuration||
||"Specifying Group Voting Details"
|Management Chain Parameters — For selecting the management chain (initial assignee and other users such as a manager) to sequentially review this task||
||"Specifying the Number of Approvers"
|Reviewers — For manually or dynamically selecting the user or group to review this task
(appeared only if the parallel workflow with final reviewer pattern was selected)
|Model a parallel participant followed by a simple participant, which acts as the reviewer.|
|(Advanced Options) Optional Task Details — For selecting the task priority, task owner, and task identification key||To specify the task priority:
To specify the task owner:
To specify the identification key:
|"Specifying the Task Title, Priority, Outcome, and Owner" or "Specifying the Task Initiator and Task Priority" to specify the task priority
"Specifying a Task Owner" to specify the task owner
"Specifying an Identification Key" to specify the identification key
|(Advanced Options) Task Flex Fields — For extending the functionality of a task to capture data in addition to the payload||Flex fields are configured in the Oracle BPEL Worklist Application. You can promote any task parameter that uses simple types to flex fields. To use this functionality, log into the Oracle BPEL Worklist Application with administrator privileges. By default, the
||"Flex Field Mappings"
|(Advanced Options) Restricted Task Actions — For restricting some common actions performed from Oracle BPEL Worklist Application during runtime||
||"Overriding Default System Actions"
|(Advanced Options) Version Tracking Attributes — For selecting the attributes to be version tracked||Version attribute configuration is not supported. The workflow service by default creates the task version when:
When comments are added, the task is not versioned.
Table E-2 describes the differences between configuration files. These files are located in the
Table E-2 Configuration File Changes
|Configuration||File||Changes Between 10.1.2 and 10.1.3.1|
||This file includes a new property called
<EmailAccounts xmlns="http:// xmlns.oracle.com/ias/pcbpel/NotificationService" EmailMimeCharset="" NotificationMode="NONE">
Set this property as follows (
The note in this file explains the settings in detail.
||This file now includes workflow property settings that previously appeared in
|Global configuration properties||
||This file now defines only the global configuration properties. All workflow property settings are now defined in
||The containment hierarchy has changed. This file now defines support for multiple realms and separate authentication and authorization providers.
<?xml version = '1.0' encoding = 'UTF-8'?><ISConfiguration xmlns= "http:// www.oracle.com/pcbpel/identityservice/isconfig"> <configurations> <configuration realmName="jazn.com"> <provider providerType="JAZN" name="XML" service="Identity"> <property name="usersPropertiesFile" value="users-properties.xml"/> </provider> </configuration> </configurations> </ISConfiguration>
The 10.1.2 format had only one realm:
<BPMIdentityServiceConfig xmlns="http:// www.oracle.com/pcbpel/identityservice/isconfig"> <provider providerType="JAZN" name="xml"> <property name="userPropertiesFile" value="users-properties.xml"/> </provider> </BPMIdentityServiceConfig>
See Also:Oracle BPEL Process Manager Administrator's Guide for additional details about these configuration files
In 10.1.3.1, a new set of APIs is provided for interacting with workflow services. These APIs only support 10.1.3.1 workflow tasks, and cannot be used to query or update 10.1.2 tasks or task definitions.
For interaction with 10.1.2 tasks, the 10.1.2 APIs are still provided. These APIs can query and update 10.1.2 tasks and task definitions. However, they cannot be used for 10.1.3.1 tasks.
Table E-3 describes the worklist API changes between 10.1.2 and 10.1.3.1.
Table E-3 API Worklist Changes
|API Clients||Different APIs to support local Java client and remote EJB client are provided.||Several API clients (Java, local and remote EJB, and SOAP) are provided.
Local and remote EJBs are now unified in a single API. To use the same API, modify the
See Also: "Building Clients for Workflow Services"
|Packages that contain the APIs:||
Table E-4 describes the task display form deployment changes between 10.1.2 and 10.1.3.1.
Table E-4 Task Display Form Deployment
|Specifying the task display form||You specify the task display form to use during workflow design in the Worklow Wizard - Task Details window:
||You specify the task display form to use after completing human task design:
|Contents of the autogenerated JSP task form||Automatically creates two files to display the payload:
||The default layout is based on a three-region template:
|Contents of the custom JSP task form||You write a JSP for payload presentation display in Oracle BPEL Worklist Application||Task display forms are generated using three templates and two default JSPs:
The two default JSPs are as follows:
See Also: "Generating a Custom Task Display Form"
|Directory structure of task form||JSP and mapping files appeared at the same level as the process.||Task display forms are packaged in an EAR file in the
|Deployment target||Forms are deployed only if the process is deployed from Oracle JDeveloper.
The autogenerated JSP is copied to the server during process deployment.
|Forms are deployed with either Oracle JDeveloper or
See Also: "Deploying Task Display Forms"
|Location of deployed task forms||All task display forms are deployed inside the sample worklist application under
||Each task display form is a separate application and is deployed under
Table E-5 lists the URLs for accessing the old and new Oracle BPEL Worklist Application. You access tasks created from 10.1.2 processes by visiting the old Oracle BPEL Worklist Application URL. You access designed in 10.1.3.1 with the Human Task editor by visiting the new URL.
Table E-5 Old and New Oracle BPEL Worklist Application URLs
|Issue||10.1.2 Worklist Application URL||10.1.3.1 Worklist Application URL|
|Worklist code location||
See Also:"Customizing the Worklist Application"
In 10.1.2, the workflow definition was defined in the following locations:
A configuration file
As BPEL code inside the workflow scope
The generated BPEL code varied based on the workflow pattern you selected to design the process. The BPEL code in the process also used the task manager process for some of its functionality. Therefore, for every process that included human workflow, the audit trail showed the activities executed inside the scope. Also, every instance of the task included a corresponding instance of the TaskActionHandler BPEL process.In 10.1.3.1, workflows are completely metadata-driven. Therefore, the generated BPEL code is much simpler; it consists of several assigns followed by invoke and receive activities from the task manager service. The task manager is no longer implemented as a BPEL process. Therefore, the audit trail shows a simplified view of the task. Also, the audit trail has been enhanced to show the task history. Therefore, clicking the task activity queries the current state of the task and displays the status and assignees.
Identify the scope activities that include human workflows.
Create a new human task definition for each of the workflows identified in Step 1.
Give it the same name as the old scope.
Drag and drop a human task activity in your BPEL process.
This creates a new 10.1.3.1 scope activity and switch activity.
Remove the 10.1.2 scope activity. However, do not remove the 10.1.2 switch statement.
Copy the case statements from the 10.1.3.1 switch to the 10.1.2 switch and retain any of the code that you have in the case blocks.
Remove the 10.1.3.1 switch activity.
Remove the 10.1.2 global task variable. When the human task is created in 10.1.3.1, a new variable is created.
Identify task forms used for the workflow by looking for the
In 10.1.2, task forms are displayed by using the autogenerated JSP form, the XSLT template, and the user-defined JSP URL. For the autogenerated JSP form, you can use the 10.1.3.1 autogenerated simple task form. For the XSLT template and user-defined JSP, URL you can use the 10.1.3.1 custom task form.
With the 10.1.3.1 custom task form, you must select the three region JSP template, which includes the header, payload, and footer regions. For the header and footer regions, you can use the default header and footer JSP, respectively. For the payload, you can use the XSLT or JSP type based on the 10.1.2 task form display.
Regenerate the task forms.
Redo any customizations that were performed on the old task forms.