Designing Notification Upload Types
You will need one notification upload type for every type of notification your organization can receive from the various service providers. To "design" your notification upload types, you document the codes used by external systems to identify the transaction types on their notification upload staging records.
We have populated the Notification Upload Type column with a few classic examples that can be received by a distribution company:
|
WF Process Criteria Notif. Upload Type |
||
|
Retrieve a customer's consumption history |
||
|
Switch a customer to a different service supplier |
||
|
Switch customer to an interval meter |
It is recommended that the unique identifier of your Notification Upload Types match the "transaction types" that are referenced on incoming notifications. If it is not possible to do this, the process that creates the upload staging records must map the external transaction types to the notification upload types that you define in the system.
In addition, as described in System Conditions May Trigger Notification and Workflow, you should evaluate any condition that should cause an NUS to be created (to eventually create a workflow). A new NUS Type should be defined for each condition. For each of these, consider creating a new value for the upload condition flag so that the NUS type is not hard-coded in the system process that creates the NUS.