Versions Compared

Key

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

...

New properties are added to influence the behavior of models that normally make use of the application Id. Blueriq run time responds to four settings on three levels.

Settings

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 

ComponentDescriptionComment
Process engineControls which part of the application Id is ignored by the process engine when evaluating timer nodes and handling message events. 
Process listControls 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 aquima.properties for Java, or are part of the .Net configuration. 

...