You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
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.
| Issue | Background information | Severity |
|---|---|---|
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 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. | low |
Overview
Content Tools