Versions Compared

Key

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


 

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 
ApplicationsComments
a:1


d:1

case a:1 will trigger:

  • application a:1, because they match exactly both on name and on version.
b:1b:1
c:1a:1

...

In the following example we use all different kinds of settings to illustrate what their effect is.

Cases 
ApplicationsIgnoreComments
a:1



 

 

d:2all

case a:1 will trigger:

  • application d:2, because nothing has to be matched: all versions of d will be taken.
  • application a:3, because with ignoring the version the name has to match.
  • application e:1, because with ignoring the project name only the version has to match.

note that application b:1 will not be triggered, because they don't match on name and on version.

b:1b:1none
c:1a:3version
d:1e:1project

...


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.

...

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.

...

  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

 


Configuration

UI Expand
titleJava configuration

The configuration for the Java Runtime is done in 

Include Page
_PropertiesFileJava
_PropertiesFileJava
:

 


Code Block
#global setting for the process engine, accepted values = none, project, version, all
blueriq.processengine.app-id-ignore=none

#per-application setting for the process engine;  format = blueriq.processengine.app-id_ignore.<application name> = none | project | version | all
blueriq.processengine.app-id-ignore.studio-RepositoryName1-ProjectName1=project
blueriq.processengine.app-id-ignore.studio-RepositoryName2-ProjectName2=version
blueriq.processengine.app-id-ignore.studio-RepositoryName3-ProjectName3=all

 
#global setting for process lists, accepted values = none, project, version, all
blueriq.processlist.app-id-ignore=none
 
#per-application setting for process lists; format = processlist.appid_ignore.<application name> = none | project | version | all
blueriq.processlist.app-id-ignore.studio-RepositoryName1-ProjectName1=project
blueriq.processlist.app-id-ignore.studio-RepositoryName2-ProjectName2=version
blueriq.processlist.app-id-ignore.studio-RepositoryName3-ProjectName3=all

 

 



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:

ui-expandJava Image Removed
Code Block
languagetext
Java properties
title
application.properties

 

 

 

 

...

# 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