Upgrading from 3.2 to 3.3 - tsgrp/HPI GitHub Wiki

OCMS Config Updates

Most OCMS 3.3 should work with 3.2 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.

Exception to the above:

• Create Folder Form Config - The configuration to disallow duplicate folders has been made more configurable in the form itself rather than the old approach of a folder path lookup. If you do nothing, duplicate folders will be allowed. To prevent this, edit the applicable create folder forms to utilize the "Attribute is Unique" External Rule on the folder attribute that should be unique across all folders of that type.

Repository Updates

Content Templates

Due to the updates related to Capture Templates, the object model around content templates was updated as part of the 3.3 release. Prior to upgrading to 3.3, save any content templates from the repository locally, delete the templates in the repository and then re-create the templates after OCMS is upgraded with the 3.3 interface.

Address Book JSON Changed

Address book now has the structure:

{
   "phoneContactBook": {
      "contacts":[
         {"username":null,"phoneNumber":"+1 123-456-7890","note":null},
         {"username":null,"phoneNumber":"+1 098-765-4321","note":null}
       ]
   },
   "emailContactBook": {
      "contacts":[
        {"username":null,"emailAddress":"[email protected]","note":null},
        {"username":null,"emailAddress":"[email protected]","note":null}
      ]
   }
}

Previously the structure was:

{
   "contacts":[
      {"username":null,"emailAddress":"[email protected]","note":null},
      {"username":null,"emailAddress":"[email protected]","note":null}
   ]
}

There are three ways to handle this for an upgraded OCMS system:

1. Delete all existing Addressbook objects
2. Update OCMS to automatically upgrade an address book as it comes across objects in the old format
3. Create a script to be created to convert client's old phone book to the new version