After you have an understanding of the phases of the business process, you can begin building a graphical representation of your business process. The tasks required to build a business process can be done at different times during the design process. For example, you may want to identify and define services before you begin modeling your process. You may also want to create data transformation maps that you anticipate using in the process model. Conversely, you could lay out the high-level business logic using the Business Process Editor and later add services and create maps and rule sets.
Placeholder activities can be created by one user and defined later in the design phase. For example, one user could create a complex activity container as a placeholder in the process. This complex activity could contain a To Do list or resources that need context properties, keys, or probes defined. A second, probably more technical user, can later define the required resources.
After the business process design is complete and tested, it is packaged and is then available for configuration and deployment to the runtime instance.
The following is a high-level presentation of the tasks required to design your business process.
To design a business process:
Create any of the following resources and add them to your business process:
Define Context to identify source or target data.
Add and define Keys for each notification service.
Add and define Probes to monitor data, if desired.
End the business process using the End activity on the Logic Tool Palette.
Connect the resources and activities to create the process flow.
Validate the business process using the Tasks View and complete or fix listed tasks.
Package the project for runtime.