A Workflow that is being enacted in response to a business event can map data from the business event raised to the Workflow as enactment data.

This table stores mappings for data from a business event raised that is then used to enact the required workflow.

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. As part of this configuration, you specify that the case identifier associated with the 'payment increase' event be used as enactment data for the specified workflow. Curam creates a Process Enactment Event Data row to record the event data mapping used to enact the 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 and determines that the case identifier used in the business event raised is to be used to enact the associated workflow Process Instance for this event. The case identifier is then passed as enactment data to the workflow Process Instance as it is being enacted.

Technical Notes

• The event data mapped must be sufficient to fully populate the enactment data of the associated Process Definition.
• Any updates to the enactment data of a Process Definition must remain fully satisfied by any Process Enactment Event Data records defined for it.