In this scenario, a BPEL process exists and has been deployed. A business analyst or developer uses IBM® Process Designer to define a process requiring manual steps and a screen flow. In the procurement sample, the human task is part of an exception handling process. The first developer integrates that exception handling into the BPEL process.
This set of tasks corresponds in a general way to the getting started procurement sample for Business Process Manager Advanced. See Instructions for running the Procurement sample for additional information about this sample.
In this scenario, an automated process, which was created using IBM Integration Designer, already exists. Using IBM Process Designer, a developer or a business analyst creates a task for human intervention to handle exceptions.
The work described here is set up to be done using two different authoring environments, each optimized to contribute its part of the total process. The developers both contribute their work to a common repository.
The Process Center repository contains all the BPM assets. The high level assets are process applications, toolkits, tracks, and snapshots. Both designers contribute to the same process applications and toolkits. Process Designer contributes business processes and data types. Integration Designer contributes modules, libraries, and BPEL business logic.
The Process Center console provides a central user interface where you can manage multiple process development efforts across the entire process lifecycle. From the Process Center console, you can create process applications and toolkits and grant other users access to those process applications and toolkits. In the Process Designer, you can create process models, services, and other assets within process applications.
To make the BPEL process available for adaptation in Process Designer, the process needs to be associated with a process application and published in the Process Center.