Versions Compared

Old Version 3

changes.mady.by.user Unknown User (r.arts)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (m.schadd)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SettingDescriptionComment
noneThe 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.
projectIgnores 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.
versionIgnores 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.
allIgnores 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.

Levels

LevelDescriptionComment
ServerThe settings apply for the complete application.A general setting if all behavior for the application is the same
ProjectA 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

ComponentDescription
Process EngineControls which part of the application Id is ignored by the process engine when evaluating timer nodes and handling message events.
Process ListsControls 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 the .Net configuration. 

Rules 

...

When displaying cases and tasks in Case Lists and Work Liststhe 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:
  1. check the process list setting for application A; if not configured then...
  2. check the global process list setting; if not configured then...
  3. check the process engine setting for application A; if not configured then...
  4. check the global process engine setting; if not configured then...
  5. 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:

  1. check the process engine setting for application A; if not configured then...
  2. check the global process engine setting; if not configured then...
  3. use 'none' as default

Aquima.properties

...

 To configure ignore process version globally, add the "processengine.appid_ignore" and "processlist.appid_ignore" parameters to the aquima section as below:

...

To configure ignore process version per application, specify the application name and ignore mode as below in the webapplication section:

Code Block
<applicationSettings>
<application name = "studio-RepositoryName1-ProjectName1" processEngineIgnoreMode="project" processListIgnoreMode="project" />
<application name = "studio-RepositoryName2-ProjectName2" processEngineIgnoreMode="version" processListIgnoreMode="version" />
<application name = "studio-RepositoryName3-ProjectName3" processEngineIgnoreMode="all" processListIgnoreMode="all" />
</applicationSettings>

...