Introduction to Progress OpenEdge Business Process Modeler

Design a business process using the worksteps, connectors, and other features provided in the Business Process Modeler user interface. A process must contain a Start workstep, intermediate worksteps that can include Activity, Adapter and Subprocess worksteps, and one or more End worksteps.

Define performers for the new process. These process-level performers are available for each instance of the process.

Assign performers to worksteps. Types of performers include individual users, groups of users, or queues that perform Activity worksteps; adapters that perform Adapter worksteps; and other processes that act as performers of Subprocess worksteps.

Define the information flow for the new process by creating dataslots, which can provide information into (inputs) or out of (outputs) worksteps.

Configure and run simulations of the process to analyze performer and resource usage, to identify repetitive loops and inefficient bottlenecks, and to predict process performance. Business Process Modeler also allows you to generate an HTML report on the simulation results.

Save the process to your local server after completing process design, or save it to the Process Repository, where it can be accessed by other Business Process Modeler users. You can also retrieve the latest version of other processes that have been stored in the Process Repository, and use them as templates when preparing a new process.

Open the saved process in Progress Developer Studio for OpenEdge, a Business Process Server component that enables users to expand the process design by adding such features as conditions that execute Decision gateways, rules that further define the process, and advanced workstep properties that include excluding performers and setting overdue actions. From Progress Developer Studio for OpenEdge, the process can be published to Business Process Portal, where it is available to users as an installed application.