Page History
...
| Subject | Property | Explanation | Default | Introduced in | Removed in | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| XML in Web Services | blueriq.legacy.create-empty-elements-for-unknowns | Controls whether the legacy behaviour of generating empty elements for unknown relations should be enabled. | false | Blueriq 11.6 | Changed to feature toggle in Blueriq 14.0: blueriq.webservices.create-empty-elements-for-unknowns |
| ||||||
| Datamapping when cancel task | blueriq.legacy.execute-datamapping-on-cancel-task | Controls whether the legacy behavior of executing the datamapping when cancelling a task is enabled. | false | Blueriq 12.12.1 | Blueriq 14.0 |
| ||||||
| Flow transaction rollback | blueriq.legacy.rollback-unknown-relation-to-empty-list | Controls whether previously unknown multi value relations should be rolled back to an empty list instead of unknown on transaction failure | false | Blueriq 12.13.19 and Blueriq 13.9 | Blueriq 14.0 |
| ||||||
| Container type: AQ_InstanceList | blueriq.legacy.single-field-instance-list-pagination | Controls whether the legacy behavior of using a single Field for pagination in the AQ_InstanceList should be enabled. NB: the new behavior adds a Container which contains two text Assets and a Field for pagination. | false | Blueriq 13.13 | Blueriq 15.0 |
| ||||||
| 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 | Blueriq 13.13.17 Blueriq 14.10.1 | Blueriq 16.0 |
|
...
Overview
Content Tools