Page History
...
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 |
Ignore Options
It is possible for every application to configure what should be ignored. You would ignore this version when ... $TODO ...
The following ignore options will influence the behavior of loading the application ID.
Ignore setting
| Ignore setting | Description | Match on | Comment |
|---|---|---|---|
none | The default behavior. The application Id is still regarded by lists and messages. | name and version | This is default behavior like prior to Blueriq 9.6. So no migration is needed. |
project | Ignores the project name part of the applicationId. This can be used when multiple projects on the same branch share the same process model. | only version | This setting was introduced in Blueriq 9.8.5. |
version | Ignores the version part of the application Id. This can be used when models are deployed from different branches. | only name | Typically for deploying from hot fix branches and different deployment strategies. |
all | Ignores version and project name from the application Id. This can be used when there are pages that wants to collect information from different projects. | nothing | Typically used in a dashboard for DCM applications. |
Example
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.
| 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 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. |
Components
On top of all properties we have the following:
| 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. |
The settings are part of the
| Include Page | ||||
|---|---|---|---|---|
|
Rules for process engine
...
| UI Expand | ||
|---|---|---|
| ||
Java application.properties  | ||
| UI Expand | ||
|
Overview
Content Tools