Designing Workflow Processes To Process Incoming Notifications
The next step involves populating each cell in the matrix with the workflow events that should be executed when the system receives a notification identified with a given notification upload type. If override criteria aren't relevant for a given notification upload type, we will mark the cell as "N/A".
|
WF Process Criteria Notif. Upload Type |
Default |
Industrial Customer |
|
Retrieve a customer's consumption history |
Validate notification - consumption history request Confirm requester is a valid service provider for the customer's service. Create notification download - send consumption history |
N/A (meaning that industrial customers use the Default criteria) |
|
Switch a customer to a different service supplier |
Validate notification - supplier switch Confirm requester is a valid service provider for the customer's service. Check with current supplier if the switch is allowed. Switch suppliers. |
N/A (meaning that industrial customers use the Default criteria) |
|
Switch customer to an interval meter |
Validate notification - change customer to an interval meter Create notification download - reject request (only industrial customers can have an interval meter) |
Validate notification - change customer to an interval meter Confirm requester is a valid service provider for the customer's service. Create field activity to exchange current meter. Change rate on exchange date. |
Notice that the first event in each cell typically validates the notification upload staging record.
At this point, the matrix is complete. Before you're ready to design your workflow process templates you must design the processes described in the next section.