Flows – DCR Compliance Engine

For all process models a set of flows can be defined. A flow is a typical path taken to complete the proces, or an invalid path you should not be able to take. Flows can be created either by creating a simulation or by using the DCR Flow Editor.

The expense report model have a set of favorite flows, sometimes also referred to as representative simulations or scenarios.

Scenarios for an expense report

When flows are displayed the swimlane for the first flow will be displayed. When the user selects a new scenario the flow will be shown.

Three types of flows exists:

  • Required – this path must be possible to complete
  • Optional – this path might be possible to do
  • Forbidden – this path can not be completed

A flow can be classified as

  • None
  • AsIs
  • ToBe
Scenario type

Re-running flows – checking compliance

Flows can be verified at any time by clicking the DCR Compliance Egnine button. Valid flows will be shown with a green marker whereas invalid will be shown with a red marker.

Re-run flows

Each flow can be shown as a swimlane by selecting Edit under each scenario. Read more about DCR Flow Editor.

A flow is a trace!

When using DCR Simulator you can test the model and create flows like the expense report happy path as outlined below:

You can view this flow as a DCR XML Log as outlined below:

For each box in the swimlane you will find a corresponding event node in the xml file. In each event node you can locate the id of the activity and the role executing the activity. The details of the format is defined in the dcr xml log format.

Related Release notes

No related documentation found.

Related Videos

No related videos found.

Related Articles

No related articles found.