Introduction

This page describes the mechanism of loading the right case with the right application in Blueriq so that it is possible to:

...

Below an overview is given of the interaction between the different components.

DCM 2.0

The ignore modes are also used in DCM 2.0, but they work slightly different from DCM 1.0 as described above. The reason for this is that in DCM 2.0, the runtime and the case engine (which contains the process engine) are separate components. The process engine settings therefore apply to the case engine (process engine) and the process list settings apply to the runtime, which contains the DCM_CaseList and the DCM_WorkList. Where the process list settings have a fallback to the process engine settings in DCM 1.0, this is no longer possible in DCM 2.0 since the process engine is no longer available in the runtime. So, for DCM 2.0 the rules for process lists are:

1. check the process list setting for application A; if not configured then...
2. check the global process list setting; if not configured then...
3. use none as default

Apart from this everything else described above also applies to DCM 2.0.