Page History
| Table of Contents |
|---|
| Warning |
|---|
When publishing 9.8.5 documentation, this page should replace the page above. The diagrams still need to be updated. |
Introduction
This page describes how to manage behavior of the application Id in Blueriq so that it is possible to:
...
New properties are added to influence the behavior of models that normally make use of the application Id. Blueriq run time responds to three four settings on two three levels.
Settings
| Setting | Description | Comment |
|---|---|---|
| none | The default behavior. The application Id is still regarded by lists and messages. | This is default behavior like prior to Blueriq 9.6. So no migration is needed. |
| project | Ignores the project project name part of the applicationId. This can be used when multiple projects on the same branch share the same process model. | 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. | 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. | Typically used in a dashboard for DCM applications. |
...
| 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
| Component | Description |
|---|---|
| Process Engine | Controls which part of the application Id is ignored by the process engine when evaluating timer nodes and handling message events. |
| Process Lists | 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. |
The settings are part of the aquima.properties for Java, or are part of .Net configuration.
Rules
When displaying cases and tasks in Case Lists and Work Lists, the Runtime uses the following rules to decide which part of the application Id should be ignored in an application A:
- 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
When handling timers and message events, the Process Engine of an application A uses the following rules to determine which part of the application Id should be ignored:
- 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
Aquima.properties
Java Runtime configuration is done in aquima properties:
| Code Block |
|---|
#global setting for the process engine, accepted values = none, project, version, all processengine.appid_ignore=none #per-application setting for the process engine; format = processengine.appid_ignore.<application name> = none | project | version | all processengine.appid_ignore.studio.RepositoryName-RepositoryName1-ProjectName1=versionproject processengine.appid_ignore.studio.-RepositoryName2-ProjectName2=all |
...
version
processengine.appid_ignore.studio-RepositoryName3-ProjectName3=all
#global setting for process lists, accepted values = none, project, version, all
processlist.appid_ignore=none
#per-application setting for process lists; format = processlist.appid_ignore.<application name> = none | project | version | all
processlist.appid_ignore.studio-RepositoryName1-ProjectName1=project
processlist.appid_ignore.studio-RepositoryName2-ProjectName2=version
processlist.appid_ignore.studio-RepositoryName3-ProjectName3=all |
.NET configuration
To configure ignore process version globally, add the "processengine.appid_ignore" parameter " and "processlist.appid_ignore" parameters to the aquima section as below:
| Code Block |
|---|
<aquima> <properties> <!-- Optional property to override the default value for ignoring the process version --> <property name="processengine.appid_ignore" value="none" /> <property name="processlist.appid_ignore" value="none" /> </properties> </aquima> |
...
| Code Block |
|---|
<applicationSettings> <application name = "studio-RepositoryName1-ProjectName1" processEngineIgnoreMode="version"project" processListIgnoreMode="project" /> <application name = "studio-RepositoryName2-ProjectName2" processEngineIgnoreMode="version" processListIgnoreMode="version" /> <application name = "studio-RepositoryName3-ProjectName3" processEngineIgnoreMode="all" processListIgnoreMode="all" /> </applicationSettings> |
...
Overview
Content Tools