You are viewing the documentation for Blueriq 18. Documentation for other versions is available in our documentation directory.
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 | |
|---|---|---|---|---|---|
| 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 | 17.2 |
|
| Runtime | blueriq.legacy.map-message-event-data-to-process-profile | In Blueriq 17.10 we introduced Message Event flows as a new way of handling message events. Because this change requires rework on the model, customers need to enable this feature with this legacy toggle for now, so they can try it when they are ready. We plan to enable this feature by default in R18 (meaning the default of the legacy toggle will be 'false'). Customers can then use this toggle to revert to the old behavior. | true | 17.10 |
|
Overview
Content Tools