Upgrade notes 1.5.0.S101

Customization of the content manager’s versioning behaviour

The activation of the content manager’s versioning behaviour can be controlled through a new configuration property called content.enableVersioning. The default value of this property is false so edoras one will not change the way the content manager is used. As this new property is part of the configuration of edoras one, the property is required to be present in the one.properties file.

The versioning behaviour can be activated and deactivated at any time. While it is active, no versions will be overwritten. When it is deactivated, if a content has several versions and it is updated, only the latest version will be overwritten. Simply put, enabling content versioning means that versions will be created upon every content update.

New view engine in `actions`

The activation of the new view engine in the actions can be controlled through a new configuration property called experimental.view.engine.actions.enabled. The default value of this property is false what forces the front end to use the previous implementation. As this new property is part of the configuration of edoras one, it is required to be present in the one.properties file. As per this release, the experimental configuration section looks as follows:

##############################
# Experimental configuration #
##############################

experimental.view.engine.enabled = false
experimental.view.engine.create.enabled = false
experimental.view.engine.actions.enabled = false

CMMN

A redundant locale parameter has been removed in select method signatures. This change only affects methods which also contain a transitionData parameter. If interested in the current locale, please access it now via the locale property of the transitionData object.

Due to the new smart behavior of User event listeners, stand-alone user event listeners in a model (any User event listeners with no connector, i.e. on-parts) must now be configured with custom property visibility=force in order to make their action button appear in the case GUI.

Miscellaneous

Filesystem content provider folder structure changes

In this release we have changed the internal folder structure of the filesystem content provider. The change was motivated to prevent a performance problem accessing the filesystem due to the integration between edoras one and the new content manager (from edoras gear).

The versions affected by this change are the S98, S99 and S100. If you have an edoras-one instance (or a bootstrap project) that uses the FilesystemContentProvider and one of these versions, you will have to recreate your database and wipe the contents of the filesystem content provider root folder.

Bootstrap project

Here you will find a list of files which have changed since the last release. This helps you check the difference between your bootstrap project version and the current one:

/src/main/resources/com/edorasware/bootstrap/config/one.properties: experimental.view.engine.actions.enabled = false, content.enableVersioning = false, properties were added src/main/resources/com/edorasware/bootstrap/config/one-dispatcher-servlet-context.xml: one.properties loading change