Page History
The beta version will be a first version which can be used by everyone on a development or test environment. Some items will need attention before the new architecture can be used in a production environment. A list of issues or points of improvements is kept up-to-date below. Some issues will be blocking for any production environment, some will be improvements which might be added later in time.
Known issues
| Issue | Background information | Found in version | Severity |
|---|
DCM_CaseList and WCM_WorkList Dossier Metadata does not work | In the new |
container, a new feature is implemented, the "Dossier Metadata". This is case-type specific data which can be used in lists. However, in this version, the Runtime behaviour is not yet implemented. | 16.0 | Low |
Testpaths are session bound, and will be lost when a new session is started. In the new setup, all automatic tasks and timers will be evaluated and executed in their own session (asynchronous), therefore the testpath will not be available.
Testing a DCM application will be a new business case to do further research on what is needed, and how this can be achieved.
Priority algorithms are based on the addition of custom code to evaluate priorities at certain moments in time. The Case Engine does not allow custom code. The task field Priority will remain unknown.
A new business case will be added to the product management backlog to investigate the requirements for case and task prioritization.
As an alternative, priority can be modeled and managed as a custom field for a task.
Limitations or different behaviour
| Issue | Background information | What to do? |
|---|---|---|
Multi-valued attributes and relations cannot be used in the DCM_GetCaseInfo. | In the new set-up, the service call is actually a REST call from the Runtime to the Case engine. Therefore, an interface (in JSON) is needed. Since we cannot just add complex graphs and all kinds of (multi-valued) attributes, they will be ignored for now |
| Use metadata of the case instead. This data will be loaded during task info, of can be loaded using the DCM_ReadCase service. This service supports multi-valued elements. | |
| Testpaths do not work on timed events or automatic tasks | Testpaths are session bound, and will be lost when a new session is started. In the new setup, all automatic tasks and timers will be evaluated and executed in their own session (asynchronous), therefore the testpath will not be available. Testing a DCM application will be a new business case to do further research on what is needed, and how this can be achieved. |
| The application ID (model version + branch) is stored as item in the process. When the case-model and feature-branch model of any task implementation is similar, then it will use this application-id to proceed. However, it is not possible for now to send the testpath parameter at any other services during an automatic task, since it is lost at the new session. | |
| Priority Algorithms don't work | Priority algorithms are based on the addition of custom code to evaluate priorities at certain moments in time. The Case Engine does not allow custom code. The task field A new business case will be added to the product management backlog to investigate the requirements for case and task prioritization. As an alternative, priority can be modeled and managed as a custom field for a task. |
Overview
Content Tools