This document contains information that is important to note when upgrading to iSymphony 3.1.1. Please be sure to completely read the information before upgrading.

Loss of Settings

Although we try to make every change backwards-compatible, in some cases the effort involved in that is simply impractical. When upgrading from iSymphony 3.0 to iSymphony 3.1 or later, take note of the following:

• The permission overhaul has changed the architecture of the permissions system significantly. Unfortunately, because of the complexity of the system and the number of potential edge cases that may be missed, we are not able to copy existing permission definitions over from the architecture used in version 3.0. As a result, all permissions defined in version 3.0 will be cleared upon upgrade, and when the upgrade is complete, no permissions will be defined. This means that you will need to redefine your permissions after upgrading. With the improvements to the batch editing, this should be significantly quicker and easier to do with version 3.1 than version 3.0. Note that this also includes access rules for extension directories, so on upgrade, all extension directories will be public by default.
• The existing queue widgets have been removed, and since significantly fewer total widgets are typically necessary with the new widget, we have elected to allow users to reconfigure their dashboards as they see fit. Therefore, all existing queue widgets will be removed from dashboards, and the new widget must be added back and configured as necessary. 

Other Notes

• Please note that as previously announced, iSymphony 3.1 drops support for Java 6. If you are running Java 6, you will need to upgrade to Oracle Java 7 or above. See the Supported Platforms page for more details. 

Upgrade Steps

Follow the standard upgrade instructions found in the Upgrading iSymphony document for all upgrades.