How Are Workflow Processes Created?

A workflow process may be created as follows:

• The Notification Upload background process (WFPRINIT) creates a workflow process when a notification is interfaced into the system. The workflow process has one or more workflow event(s). Workflow processes created as a result of a notification upload staging record will reference the NUS ID that created it. Refer to The Big Picture Of Notification Processing for more information about notifications.
• An operator may create an ad hoc workflow process at will.
• If you customize the system accordingly, the system will create a workflow process when a significant event occurs. The purpose of this type of workflow process is to send outgoing notifications to other interested parties to apprise them of the event. For example, assume you are a distribution company, you probably have to advise a customer's energy supply company whenever their meter is exchanged. In this example, when a meter exchange transpires, you'd want to create a workflow process that would, in turn, send outgoing notifications to the energy supply company. Refer to Designing Notification Downloads for more information.

Whenever a workflow process is created, the system uses a workflow process template to create the workflow process. The workflow process template defines the various events that will transpire over the course of the process. Refer to Designing Workflow Process Templates for more information.

In the above diagram, the event on 1-Dec-00 shows the creation of a workflow process with three workflow events. Notice that the events all exist in the Pending state. The events will exist in this state until their trigger date is on or before the current date.