Page History
Table of Contents |
---|
Introduction
...
Note |
---|
This behavior is different to how it previously worked! Before R11 clicking an application determined what case could be run. The drawback of this approach was that it needs a polling mechanism. |
...
Since R11 the mechanism is as follows:
...
No additional settings are set.
Example
Cases | Applications | Comments | ||
---|---|---|---|---|
a:1 | → | d:1 | case a:1 will trigger:
| |
b:1 | b:1 | |||
c:1 | a:1 |
...
In the following example we use all different kinds of settings to illustrate what their effect is.
Cases | Applications | Ignore | Comments | |
---|---|---|---|---|
a:1 |
→ | d:2 | all | case a:1 will trigger:
note that application b:1 will not be triggered, because they don't match on name and on version. |
b:1 | b:1 | none | ||
c:1 | a:3 | version | ||
d:1 | e:1 | project |
...
Levels
It is also possible to determine on a higher level how the mechanism should work in general, so this is then for applications overall.
...
Component | Description | Comment | |
---|---|---|---|
Process engine | Controls which part of the application ID is ignored by the process engine when evaluating timer nodes and handling message events. | ||
Process list | Controls which part of the application ID is ignored when displaying cases in Case Lists and tasks in Work Lists. For backward compatibility, when process list settings are not configured, the process engine settings apply. | This component was introduced in Blueriq 9.8.5. |
...
- check the
process list
setting for application A; if not configured then... - check the global
process list
setting; if not configured then... - check the
process engine
setting for application A; if not configured then... - check the global
process engine
setting; if not configured then... - use
none
as default
Configuration
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
The configuration for the Java Runtime is done in
|
Work list and case list
The default behavior for building a work list or a case list is a query on the database which uses an application Id. If the version Id and the project name of the current model definition do not match the stored version Id and project name, no tasks and cases will be shown in the corresponding lists. With the new settings it is possible to get the required behavior.
...
Below an example is given to get a good understanding on how to address the properties:
Code Block | |||||
---|---|---|---|---|---|
| |||||
| Java
|
...
# global setting, accepted values = none, project, version, all
blueriq.processengine.default-app-id-ignore-mode = none
# per-applicaton setting; format = blueriq.processengine.app-id-ignore.<application name> = none | project | version | all
blueriq.processengine.app-id-ignore-modes.studio-ACO-First = all
blueriq.processengine.app-id-ignore-modes.studio-ACO-Second = all |