Dear customer
In this release we enable the configuration of the content versioning capabilities of edoras one. By default, the versioning is disabled, but now you will have the option to enable it to take advantage of the content manager’s API version aware methods.
Another big step of the view engine integration has been accomplished in this sprint by extending the view engine to support the actions
.
For the detailed information see the following chapters.
Best regards,
the edorasware team
Customization of the content manager’s versioning behaviour
The edoras gear’s new content manager API has versioning capabilities. Until this release, these capabilities were not used by edoras one. The 1.5.0.S101 release includes a new
customizable property: content.enableVersioning
. By default, this property is set to false. If the enableVersioning
property is set to true, the content manager will keep all
the versions of the content on every update. The normal behaviour and usage of edoras one will be the same, with or without versioning, but with versioning the previous versions
of the content will be available through the content manager API.
Please, check the upgrade notes to understand how to use this new configuration.
New view engine in actions
As of 1.5.0.S101, the new view engine is also supports the actions
.
This is a big step towards the replacement of the previous engine and its deprecation. Currently, the view engine is still experimental and as a backup measure, the
integration in the actions
can be controlled through an additional property in one.properties
(please, have a look at the upgrade notes).
CMMN
User event listeners are now smart in the sense that their GUI representation (i.e. action button) is only visible if clicking it actually has an effect in the run-time model (i.e. a sentry connected with the user event listener actually triggers the plan item it is connected with).
The CMMN engine now supports plan item connectors (on-parts) that cross stage hierarchies. Before this release, such connections had to be modeled via a Milestone element living in a common parent stage of the two stage hierarchies involved. With this release, plan items may be connected freely between stages. The run-time behavior is identical to the modeling pattern using the mentioned common up-hierarchy Milestone element.
Various improvements have taken place in the VIS modeler. This includes improvements to the handling of 'dockers' (the red points in plan item connector lines) and connector line routing.
A new section on CMMN modeling options (CMMN palette properties) has been made available in the CMMN documentation. The tooltip texts available in the CMMN VIS modeler have been updated accordingly.
Case File Item handling for Case File Items of type edoras case variable
has been improved. This includes added support for "native" Work Item fields
like name
and priority
and includes a bug-fix related to update detection of variables triggered by a BPMN process.
Miscellaneous
Byte-range requests enabled for all the content types
In the 1.5.0.S101 release, byte-range request support was implemented for the PreviewRestService (the document preview) and the Document Viewer. This feature was enabled only for linearised PDF documents. In this release, we enable the byte-range request for all the PDF documents, linearised or not.
The downside of delivering non-linearised PDFs with Byte-range requests support is that the final rendering of the PDF is not guaranteed until the last chunk of the file is loaded. Hence, the user can browse the PDF documents while the document is still loading, but the content may change if an object that must be displayed in one of the already loaded pages is physically stored in the last parts of the PDF file. This case is very rare and checking the linearisation of the PDFs reduces the performance notably, therefore the benefit of enabling this feature for all the PDFs greatly outweighs the risks of experiencing a late content change.
Runtime values included in exporting and importing of translations
The exporting and importing of text translations used within the Process, Form and Case models belonging to a given App model has now been extended to include the run-time values of all the attributes which support multi-language entries in the vis designer view and have a i18n-key specified.
A -RT
suffix is added to the keys of the run-time entries in the exported translation files to differentiate them from the non-run-time entries.
Upgrade notes
Please have a detailed look at the upgrade notes for this version such that you are able to easily upgrade to the newer version.
If you have issues viewing the email then click here to view the online version. If you want to unsubscribe from the release notes please send an email to unsubscribe@edorasware.com.