Upgrading from 3.3 to 3.4 - tsgrp/HPI GitHub Wiki

OCMS Config Updates

OCMS 3.4 actions should work with 3.3 configurations. However, as with all releases, it's recommended that you backup your configs prior to the upgrade and visit all areas in the OCMS admin to verify and tweak configurations. For production environments, it's recommended to perform the upgrade in a Dev/QA environment and then utilize the config archiver to move upgraded configs to higher environments.

Send Notification Updates

Notifications are now sent using an Ad-Hoc Form to provide better flexibility as to what fields are included in the notification. Additionally, viewing notifications can now be configured as a dashlet in addition to the header modal. See below for more information. To use Notifications with OCMS 3.4, you must follow these steps to configure the send notification action.

As part of these updates, the workflow template changed slightly. The easiest way to get the updates is to restart OC once with the following property set in your external properties after deploying the 3.4 OpenContent:

activiti.template.force.redeploy=true

After restarting OC with the above setting, remove it from your external properties to prevent subsequent unnecessary template redeployments.

Repository Updates

Templates Location

Prior to this release, the ocmsTemplates folder lived under /hpi. As part of the 3.4 release, this folder should be moved to /hpi/default.

Controlled Documents (Alfresco only)

The Controlled documents model now contains the af:autofiled aspect as mandatory. Prior to installing the latest OpenContent AMP, all documents should have that aspect applied. This can be done via the JavaScript console in share.

Controlled Documents Effectivity Job (Documentum only)

The Effectivity Job was moved to an OC job in this release. The old tsg_makeDocsEffective dm_job can be disabled as of this release.