| Subject | Property | Explanation | Default | Introduced in |
|
|---|
Composer
| blueriq.legacy.composer-nowrap-repeat-container-enabled | Elements 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. 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 rendering. | false | Blueriq 11.1 | | Include Page |
|---|
| _PropertiesFileJava |
|---|
| _PropertiesFileJava |
|---|
|
| Front-end | blueriq.legacy.page-comparison-ignores-user-input | User input will now be considered when computing the difference between the previous and the new page. This means that fields may no longer appear as updated, since the front-end already knew about the change in value. This change may affect regression tests that contain assertions for field updates. Setting this property to true will revert to the old behavior. | false | Blueriq 11.3 | | Include Page |
|---|
_PropertiesFileJava | _PropertiesFileJava |