The CVApps packager is now able to take into account an external properties file and to replace the value found in it into predefined placeholders set in configuration files during the deployment process (#26005). The goal is to be able, from a single application zip file, to target multiple deployment environments.

For instance, you can add a placeholder myPath in the path value of a file connector in the Connector.xml configuration file:

Set a value for that property in a properties file and use it when deploying your application with the CVApps installer.

Partial update is now supported by the consolidation server, without impacts on performances. You can use the updateDocument command to push a partial meta set of a document.
Please carefully notice that if you directly push link directives within a document, you will also have to send those directives again within the partial update command.
If link creation is handled only with transformation processors, then partial update will be fully supported.

A new component is available in this release: the Replay server. This component allows the capture of a document flow that is sent to a PushAPI and to be able to "replay" it, fully or partially, later on.
For more details, see the "Replay Connector" section in CloudView Connectors Guide.

Please be aware that this feature is beta and should not be deployed in a production environment.

• Switch default configuration of the DIH from "auto" to "mmap" (#26173)

• Clear old configuration files is available in the "Versions" page of the Admin UI (#25972). To reduce space taken by old versions of CloudView configuration, it is possible to keep only the last versions and delete older ones.

• Field type options when adding a property in the datamodel allow to target dedicated and dynamic fields (#25751)

• Improve synthesis speed for deep category tree when a maxCategoryTreeDepth has been set (#25831)

CloudView R2016x and R2016x R1 configurations are fully compatible with CloudView R2016x R2.

To benefit from this feature inside an existing Mashup application,the following operations are needed:

In the application properties of your application, section General > JavaScript, add the following entries:

Add a new trigger in the application trigger page section:

Open a page and choose the Design tab
Drop in the application page trigger section the trigger  "Cookie to parameter" (it can be found in Triggers > Pre Request trigger section)

Set the following parameter for the trigger:
Parameter name : timezone
Cookie name: mashup-timezone

For each feed that requires to push the user timezone information, add the following configuration: 

In the Advanced Parameters section, set Timezone Parameter to ${page.params['timezone']}