A Workflow Process Contains Relevant Data

Linked to a workflow process are the relevant data associated with the process. This information can be for audit purposes or it may be needed by one or more of the event algorithms linked to the process to do its work. For example,

  • If a workflow process is associated with the inspection of a premise, the premise is linked to the workflow process.
  • If a workflow process is associated with new service, many pieces of information are needed to be linked to the workflow including the address of the new service location, the date service should start, perhaps the desired rate and perhaps customer information, if this is for a new customer.
  • If a workflow process is triggered when we receive a notification that we have a new customer, the notification is linked to the workflow process.

This data may be linked to the workflow process in one of two ways: as context or as characteristics. The following points describe each method:

  • Context Collection
  • Uses a context type to identify the type of data. The values of the context type are stored in a lookup field and must be customized by your implementers.
  • The values are stored in the context value field. Values may be up to 50 bytes long.
  • The primary key of the record includes context type and context value so multiple values may be entered for the same type.
  • Note, the context value is a generic field. If the value of the field is a foreign key, there is no way for the system to enable drill down capability to this foreign key's entity.
  • Characteristic Collection
  • Uses the characteristic type table to identify the type of data. Characteristic types may be pre-defined, ad-hoc, foreign key or file location.
  • The values are stored in different characteristic value fields depending on the type of characteristic. The ad-hoc and file location values may be up to 254 bytes long.
  • The primary key of the record includes characteristic type and a sequence number so multiple values may be entered for the same type.
  • If the characteristic is of type foreign key reference, a search is available for selecting an appropriate value and a drill down key is available for viewing the related record.
Note:

The original design included only the context collection. The characteristic collection was added later as a result of limitations in the context functionality that was supported in other parts of the system by characteristic functionality. It is expected that characteristics will be the preferred method to use for implementations. Context will continue to be supported for earlier releases.

Information in a workflow process' context or characteristics collection is referenced by the workflow process' event algorithms when they are activated.

If a workflow process is created to process an incoming notification from a third party, the first event algorithm for your workflow process must populate the workflow process' context or characteristics with individual fields specified on the incoming notification.

Fastpath:

Refer to Uploading Notifications Into The System for more information.

Note:

If an account ID or premise ID in Oracle Utilities Customer Care and Billing is linked to an active workflow process either via context or via a characteristic, you may configure your system to display an alert when that account or premise is displayed in the current context. To display this alert, create one or more algorithms for the CCAL-WF algorithm type, setting the parameters as appropriate to display account or premise and indicate whether or not the account/premise will be found in the context or characteristic collection. Plug in your new algorithm(s) to the installation option - algorithm collection.