Activity 4: Adding Alternative Paths
You now have a good part of the functionality of the most expected
path of the project. It is time to consider alternative paths. These paths are
also expected, but they are expected to be less frequent than the happy path.
Alternative paths can be more, equally, or less desirable than the most
expected path. In this activity we will adopt the convention of adding more
desirable, or "happier", paths
above the most expected path, and less desireable or "less happy"
below the most expected path.
- Defining the Check Company Policy Task
The first activity after the instance is created is Check Company Policy. This is an automatic activity where you will code a simple rule that will handle pre-defined approval and rejection criteria.
- Adding a Conditional Transition
The instance is routed through a conditional transition when a given condition is met. Here we will add a conditional transition so that the report skips the approval activity if the total amount is low.
- Adding the Edit Report Activity
If an Expense Report is rejected either automatically or by another participant, we want the employee to be able to edit the report to correct mistakes or to add clarifying information. To allow the employee to do this, we add the Edit Report activity.
- Adding Conditional Transitions to Edit Report
You now have the Edit Report activity, but there is no path that will take the instance to it. In this task we add two conditional transitions which are are taken when the expense report is not accepted the Check Company Policy activity, or not approved at the Review Report activity.
- Defining the Review Report Presentation
We now have a conditional transition to be used in case the supervisor does not approve the expense report. However, we have not defined the Review Report activity. To do so, you will first need to create the Review Report presentation.
- Defining the Review Report Activity
We now have a conditional transition to be used in case the supervisor does not approve the expense report. However, we have not defined the Review Report activity. You will define this activity as a screenflow similar to the Submit Report screenflow.
- Designing the Review Report Screenflow
Here you design the Review Report screenflow to complete the functionality of the Review Report activity.
- Adding the Not Confirmed Transition
In this task you add the last conditional transition of the Expense Report process. This transition is to be used when the treasurer has not confirmed one or more receipts.
- Creating the Confirm Receipts Presentation
You have not yet defined a task for the Confirm Receipts activity. As with the other interactive activities, Confirm Receipts will use a screenflow. As before, you must first define the presentation this screenflow will use.
- Defining the Confirm Receipts Activity & Screenflow
We now have a conditional transition to be used in case one or more receipts are missing or incorrect. However, we have not defined the Confirm Receipts activity. You will define this activity as a screenflow.
- Running the Process
The Expense Report process is now complete.