Page History
| Numbered Headings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Blueriq EncoreFrom this release, you will be able to unleash the power of Blueriq from our brand new modeling environment. Although the Blueriq concepts are not different compared to Blueriq Studio, Blueriq Encore offers a new and enhanced modeling experience. We were able to achieve this by listening to your feedback. Blueriq Encore is installed automatically with Blueriq Studio. Highlights of Blueriq Encore are:
Blueriq Encore is still in development (have a look at the progress here), but you are already able to use it because it is compatible with Blueriq Studio. That is: edits in Studio will appear in Encore and vice versa. Can't wait? Send an email to support@blueriq.com and gain acces to https://meet-encore.blueriq.com after watching the transition videos. We're continuously improving Blueriq Encore so don't hesitate to share your thoughts with us by using the customer portal or sending an email to support@blueriq.com. An example of a flow in Blueriq Encore:  DCM architecture betaFor a better Dynamic Case Management experience, a number of architectural changes have been made. We have been working on a new architecture, which is event-driven. The benefits are that the DCM solution is split in multiple smaller functions, that can be configured (and optimized) separately, using technologies best suited for the job, and end-users do not have to wait for processing times where it is not necessary. The new architecture also includes a first approach on reactive components, by adding a reactive Task list for the end-users. The software is in a beta stage, and can be tried on a development environment. The current way of building DCM applications and processes will remain intact, so any project can safely upgrade to the latest Blueriq version without using the new architecture. For more information trying the new beta architecture, please check DCM architecture beta release for more information. Document rendering serviceIn release 15.0 the new Document rendering service that has been introduced in Blueriq 14.9 has become mandatory. We migrated from an integrated Ibex Java renderer in the Blueriq Runtime to a stand-alone .Net Ibex rendering service. This provides the option for customers to create 1:n deployment model where one Document renderer services multiple Runtimes. To help our customers in the migration we documented the steps here. We focused on having as little differences in the pdf output as possible, in which we succeeded. Some minor differences have been noticed and have been documentend on the migration page. Installation and configuration can also be found here on my.blueriq. Keycloak as identity provider in the StudioThe Studio has supported a wide range of authentication schemes for some time already, and the selection is now extended by leveraging Keycloak as identity provider using the OpenId Connect protocol. This enables more extensive authentication configurations than were possible before, such as federated user authentication. Please refer to the Keycloak configuration page for information on how to configure the Studio to start using Keycloak. 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:
Discontinued
Upgrade InstructionsPlease review the Release 15.0 Upgrade Instructions.
ArtifactsThe Blueriq artifacts are available under name: 15.0.0.105 This release includes these versions of Blueriq components with a separate life cycle:
Aquima LibrariesThe DCM library has been updated, see below what has changed: 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 announcementFor a full list of deprecated features, go to Deprecated features. Dropped support for reading and publishing R8-R11 exportIn release 12 we introduced a new export format and to maintain backwards compatibility we added an extra set of properties to still be able to read the R8 exports. In release 15 we have removed the deprecated R8 exports altogether, when using an R8 export the Runtime will log an error stating that exports older than version 12 cannot be read anymore. For a migration path for old exports please go to Release 15.0 Upgrade Instructions Dropped support for DateValue.parseDate and DateValue.valueOf with time componentIn Blueriq 13.2 the use of DateValue.parseDate with a time component as argument and DateValue.valueOf with a time component as return value became deprecated. Starting from this release the warning has been removed and doing this results in an exception. You can read more about it in the Deprecated features. Dropped support for Trace Event V1In Blueriq 14.10 the use of Trace Event V1 became deprecated. In this release the Trace Event V1 has been removed in favour of the Trace Event V2. You can read more about it in the Release 15.0 Upgrade Instructions. Bug fixes
Known issuesFor an overview of known issue please refer to: Known issues Security notificationTo improve the default security configuration of the Runtime this release has changed various configuration defaults to enable best practices by default. Details can be found in the upgrade instructions. |
Overview
Content Tools