Page History
Numbered Headings | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NewDeprecate elements in EncoreIt is now possible to manage the evolution of a model by deprecating elements in Blueriq Encore using the built-in label called "Deprecated". A deprecation will generate a validation warning for each usage of the deprecated element. This signal can be used by business engineers to other business engineers to communicate that an element will be removed in a future version. OpenAPI feed improvements part 2Continuing on Blueriq 17.4, more OpenAPI feed improvements have been added to the current release in order to provide standardized and clear documentation on Blueriq web services and thereby improve collaboration with consuming parties. From this release:
Process messages for a deleted case in DCM ListsSometimes a message is processed in the DCM Lists for a case that has just been deleted just. The reason for this is that messages can be processed out of order, especially when using multiple consumers. This would now lead to an exception, which would cause the message to be retried until it fails definitively in the maintenance app. There is can then only be manually removed. To fix this, cases are not directly removed from the case engine, but instead get a flag that they are marked for removal. These cases are then ignored by the DCM Lists application, unless a message is processed that relates to that specific case. Then the DCM Lists application can process that message (by discarding and logging it). As this means that cases are no longer removed from the database, the database may grow and degrade performance because of that. To prevent this, a cleanup mechanism runs at a specified interval, cleaning up cases marked for deletion before a specific time. For more information, see Case deletion in DCM Lists [editor]. Enhancements
DocumentationDocumentation on the new features and improvements of this release is linked in the respective topics. Changes Platform SupportOur Platform support is updated. Changes are:
Upgrade InstructionsThere are no specific upgrade instructions for this release.
ArtifactsThe Blueriq artifacts are available under name: 17.x.x.xxxx This release includes these versions of Blueriq components with a separate life cycle:
Blueriq LibrariesThere are no specific Library updates for this release. LibrariesIn this release, the set of third party libraries that is used by Blueriq was updated. When your installation of Blueriq includes custom components (artifacts that do not ship with Blueriq, such as proprietary plugins), those components should be tested for compatibility with these changes.
Retirement announcementThere are no specific retirement announcements. For a full list of deprecated features, go to Deprecated features. Bug fixes
Known issuesFor an overview of known issue please refer to: Known issues Security notification |