Versions Compared

Old Version 6

changes.mady.by.user Deny Raatgever

Saved on

compared with

New Version 7

changes.mady.by.user Felix Janssen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

IssueBackground informationSeverity

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

low
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.

low
Priority Algorithm does not workAlgorithms don't work

Priority algorithms are The priority algorithm was 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.

low