With Blueriq 11.0 we introduce legacy properties that will be available for one major version and are immediately deprecated from the moment of introduction. The properties should therefore preferably not be used but may Legacy properties are properties to configure legacy behavior in specific cases. This legacy behavior is deprecated and should therefore not be used, as it will be removed in a future release. The properties exist to help during a transitioning period towards the new behavior.
| Subject | Property | Explanation | Default | Introduced in |
|---|
Composercomposernowraprepeatcontainer-enabledElements with a repeat expression are transparently wrapped in a container to achieve more stable element keys for determining page updates. Setting this property to true causes repeated elements not to be assigned a nested key as was the case before R11.0 | false | Blueriq 11.0 | | Include Page |
|---|
_PropertiesFileJava | _PropertiesFileJava | Flow | blueriq.legacy.keep-errors-on-exception-exit-enabled | When true the legacy behaviour keeps errors after the exception exit of a service or function call was taken. | false | Blueriq 11.0 | | Include Page |
|---|
_PropertiesFileJava | _PropertiesFileJava | Process Engine | blueriq.legacy.transactional-case-evaluator-enabled | When true, the legacy behaviour of single transaction per background case evaluation is enabled. This may lead to deadlocks when automatic tasks call BAAS services that also modify the process data store. | false | Blueriq 11.0 | | Include Page |
|---|
_PropertiesFileJava | _PropertiesFileJava | Aggregates | blueriq.legacy.service-exception-on-aggregate-of-wrong-type | When true, the legacy behaviour for taking the exception exit on the AQ_Aggregate_Read service is enabled. This means that when an Aggregate is read that has a different type than requested, the exception exit will be taken. | false | Blueriq 11.0 | | Include Page |
|---|
_PropertiesFileJava | _PropertiesFileJava | Composer | blueriq.legacy.validate-invisible-fields | Fields that will become invisible because their visibility condition changed will no longer be validated since R11.1. | validation | Blueriq 15 started to also include field validations when parsing a REST response, which may result in the REST service client call failing for messages that used to be accepted in earlier versions. |
Setting this property to true reverts to the old behavior |
, in which validation messages will be computed for fields that may no longer be on the page during the next page renderingBlueriq 111| 2 | | Include Page |
|---|
| _PropertiesFileJava |
|---|
| _PropertiesFileJava |
|---|
|
|