Scenarios – DCR Compliance Engine

For all process models a set of scenarios can be defined. A scenario is a typical path taken to complete the proces, or an invalid path you should not be able to take. Scenarios can be created either by creating a simulation or by using the swimlane editor.

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

Scenarios for an expense report

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

Three types of scenarios 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 scenario can be classified as

  • None
  • AsIs
  • ToBe
Scenario type

Re-running scenarios – checking compliance

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

Re-run scenarios

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

A scenario is a trace!

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

You can view this scenario 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.