Page History
...
In this article we will use the notation "a:1
" in in the schema of "<name>:<version>
" . This ID is used to make sure to always address the correct case from a case list or work list. The same behavior applies using message events. So having an unique identity is a good thing, but it also limits the way of deploying models and expanding an application using more than one projects.
With this mechanism we are able to fulfill fulfil the following requirements:
...
UI Text Box | ||
---|---|---|
| ||
As business I want to be able to have a single dashboard over projects so that all cases and tasks are shown in one list. |
Behavior
...
Since R11 the mechanism is as follows:
...
Level | Description | Comment |
---|---|---|
Server | The settings apply for the complete application. | A general setting if all behavior for the application is the same |
Project | A setting per project if settings only apply for to a single project. | These settings overrule the server setting. It is possible to have a mix. So if no project setting is available, then the server setting applies. |
...
The settings are part of the
Include Page | ||||
---|---|---|---|---|
|
Rules for process engine
...
When displaying cases and tasks in the AQ_CaseList and AQ_WorkList containers, the Runtime uses the following rules to decide which part of the application Id should be ignored in an application A:
...
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
The configuration for the Java Runtime is done in applied to
|
...
Overview
Content Tools