Process Design

The Expense Report process is implemented in the ExpenseManagement sample project, which is included in the Studio installation. This tutorial shows how this Expense Report process is developed.

Once it is complete, the Expense Report process diagram will look like this in the Studio editor:

Figure 1. Expense Report process diagram

To examine the Expense Report process in Studio, you may import the ExpenseManagement.exp project file included in your Studio installation. By default, it is installed in the following directory: OraBPMStudioHome\samples\basic\ExpenseManagement.exp. However, to actually perform the tutorial we recommend that you start from scratch.

Process Elements

The Expense Report process contains the elements described in this section. You do not need to memorize this list. Before moving to the next section, review this list briefly to get a general notion of the process:
  • Three roles, Employee, Supervisor, and Treasurer. Each role has one swimlane in the process diagram, and there are also two unlabeled swimlanes for automatic activities.
  • The Begin and End activities, present in every Oracle BPM process.
  • A global creation activity, named Create Expense Report. This is the activity that the employee uses to create a new report. In business process terms, this is the activity that creates a new instance.
  • Four interactive activities: Review Report, Confirm Receipts, and Edit Report. These activities require input from a participant, and are described in detail in Interactive Activities.
  • Three automatic activities: Check Company Policy, Process Expense, and Send Reminder. These activities are performed automatically by the system, with no user interaction. Each automatic activity in this process is described in Automatic Activities.
  • Transitions, which establish the flow of the process. These transitions are used: Unconditional, Conditional, and Due. For detailed descriptions of each, see Transitions.