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 | Removed in |
|
|---|
| Process Engine | blueriq.legacy.use-legacy-case-unlocking | With the legacy behavior, checking if a case is locked and unlocking a case is done in Hibernate. This in contrast with acquiring a lock, which is done directly on the database. The new behavior is to check/unlock directly in the database as well and also throw an exception when a case is unlocked that was not locked. | false | 13.13.17 14.10.1 | 16.0 | |
BQ15:BQ15: |
| Runtime | blueriq.legacy.readonly-inherit-from-parent | With this property the old behavior can be activated for elements on the page. They will always inherit the read only property of the parent container. For lists this means that with this legacy toggle activated search buttons and navigation will be readonly. | false | 15.3 | 16.0 | |
BQ15:BQ15:BQ15:_PropertiesFileJava | BQ15: |
| Runtime | blueriq.legacy.legacy-rest-validation | With the introduction of reporting all errors during parsing of incoming JSON rest requests or responses, the error-message content changes. If this is not (yet) desirable the runtime reverts back to the previous implementation by setting the property to true | false | 15.12 | 17.0 | |
|
|---|
| _PropertiesFileJava |
|---|
| _PropertiesFileJava |
|---|
|
|
| Runtime | blueriq.legacy.legacy-rest-response-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. | false | 15.13.26 | 18.0 | |