Page History
Fundamental changes (in comparison to v4.9.x):
...
| Change topic | Background information | Remarks |
|---|---|---|
| Updated the Dashboard library so it longer has any servicetypes or containertypes related to starting applications/sessions | As we want DCM2 to be failover compliant we cannot support the services and containers any more that produce nested sessions. These | Please use Dashboard library v3.x (and up) |
Updated the DCM library and introduced new servicetypes for communication with the dashboard for specific actions: start new case, open case, start task from case |
| Please use DCM library v1.2.x (and up) |
| Project structure Main_Dashboard |
Deleted the External flow contract and related mapping | The "Home"-page with the different widgets modeled on it as containers is no longer needed. Instead, the containers now have there own implemented Exposed flows:
|
| Project structure ZaakType_A |
Deleted:
Moved:
| Task execution is now completely handled in the background and is not necessary for the Business Engineer to model any more. The ZaakA_Implementatie has been made the Root module (and thus entry point) for the project. |
Removed |
...
all external flows | This decoupling method is not necessary in the default DCM Foundation. We do see use cases for the external flows within DCM, but at the moment they are NOT supported yet | |
Created new flows with pages for the different widgets for Tasks, Notes, Documents, etc. | The new DCM Dashboard application start Exposed flows from a regular Blueriq project. Each widget on a dashboard page can be modeled in a single Exposed flow
|
| Info |
|---|
DCM_Tasklist container is not supported (as is it not able to be made failover compliant), that's why the DCM_Worklist is still implemented |
...
Overview
Content Tools