Workflows can be enacted:

• by business logic explicitly invoking an enactment service;
• from an existing workflow (as a sub-flow); or
• in response to a business event.

This table stores configuration only for workflows enacted in response to a business event.

Example

You define a workflow (Process Definition) to allow correspondence to be sent to customers whenever their payment details change.

The payment business processing has already been modified to raise a 'payment increase' event whenever payments increase on a case.

You use the Admin application to configure your workflow to start whenever the 'payment increase' event occurs. Curam creates a Process Enactment Event row to store the association between this event and your workflow.

Person John Smith's payment details change due to an increase in rates. This increase raises a 'payment increase' event. The Workflow Engine reads this table to identify that your workflow is configured to start whenever the 'payment increase' event occurs, and enacts an instance of your workflow.

Technical Notes

The configuration of which event starts which workflow can be specified or modified at any time after the workflow has been defined.

Changes to your workflow and the event/workflow configuration are independent provided the event data can fully populate the enactment data required by workflow at all times, i.e. you can:

• change your workflow without affecting which events start your workflow; or
• change the events which start your workflow without changing your workflow definition.