Converging Branches of a Process Flow
The And AgileShape enables you to converge all incoming activities to the AgileShape, or to exclude the activities that are bypassed by the process flow. This example shows a scenario where the AgileShape waits for all incoming activities to complete the processing.
Instructional Goals
- Demonstrate how to moderate a process flow using the And AgileShape or the Wait All Incoming property.
Example Process: Respond to Utility Customer Power Outage Report
Problem Statement
Fix a power outage for a utility company consumer.
Business Requirements
- The process is initiated when a utility customer calls in to the customer service department at a utility company to complain of a power outage.
- Fixing the power outage can occur on 2
simultaneous paths:
- Manual path - A technician is called to fix the power outage.
- Automated path - A web service is called to check an external monitoring system, which reports whether the power in the area of complaint is live.
- The utility company wants to set the And AgileShape so that the process flow proceeds only when both the automated path and the human path have completed.
Navigation
- In AgilePoint Envision, open a process template.
- Navigate to the Generic BPM stencil.
- On the Generic BPM stencil, drag the And AgileShape, and drop it on the process template.
- To view the entire list of properties, in the Design Tasks pane, click Show Properties.
Instructions
- In the Dynamic list, click False.
In this example, the And AgileShape waits to move forward until both theSite Visit Complete email notification is complete and Power Condition Check Web Service responds Yes.
Alternately, you could not have an And AgileShape at all and achieve the same effect. In this approach, set Wait All Incoming to True (Static) on the Power On Confirmation Email AgileShape.
