Activity 4: Adding Alternative Paths

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 desirable or "less happy" paths below the most expected path.

1. Defining the Check Company Policy Task
   The first activity after the instance is created is Check Company Policy. This is an automatic activity in which you code a simple rule to handle pre-defined approval and rejection criteria.
2. Adding a Condition Transition
   The instance is routed through a condition transition when a given condition is met. Here we will add a condition transition so that the report skips the approval activity if the total amount is low.
3. Adding the Edit Report Activity
   If an Expense Report is rejected either automatically or by another participant, the employee must be able to correct mistakes or add clarifying information. To enable the employee to make such edits, we add the Edit Report activity.
4. Adding Condition Transitions to Edit Report
   You now have the Edit Report activity, but there is no path to take the instance to it. In this task we add two condition transitions: one for when the expense report is not accepted at the Check Company Policy activity, and the other for when it is not approved at the Review Report activity.
5. Defining the Review Report Presentation
   We now have a condition transition that the process instance flows through if the supervisor does not approve the expense report. We must now define the Review Report activity in which the Supervisor can approve or reject the report.
6. Defining the Review Report Activity
   You have a conditional transition to be used in case the supervisor does not approve the expense report, and you have the presentation that the supervisor is to use. Here we implement the Review Report activity as a screenflow like the one we created for the Submit Report activity.
7. Designing the Review Report Screenflow
   Here you design the Review Report screenflow to complete the functionality of the Review Report activity.
8. 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 does not confirm one or more receipts.
9. Creating the Confirm Receipts Presentation
   You must implement a task for the Confirm Receipts activity. As with the other interactive activities, the Confirm Receipts activity uses a screenflow. As before, you must first create the presentation this screenflow uses.
10. Defining the Confirm Receipts Activity & Screenflow
    You have a condition transition to be used in case one or more receipts are missing or incorrect. We implement the Confirm Receipts activity as a screenflow.
11. Running the Process
    The basic Expense Report process is now complete, though we will add some features to it in Activity 5.
12. Activity 4 Summary
    Congratulations! You have completed the main elements of the Expense Report process.