Database Schema Changes
Upgrading to uPortal 3.2 requires re-initializing the uPortal database structure. uPortal adopters may migrate their data to uPortal 3.2 through the use of the import/export tools. The remainder of this section describes places where changes to the portal's schema or default data sets may warrant hand-tuning of migrated data.
Default Categories
The uPortal 3.2 release included a reorganization of the default uPortal categories. New categories may need to be added to an existing installation to ensure all new content is properly imported. Several previously-existing categories were removed, so upgraders may also need to choose betweeen restoring those categories or assigning existing content to new categories.
...
The uPortal permissions implementation was also modified to allow inheritence of permissions by targets. For example, setting a permission on the target "Everyone" group will now cause that permission to cascade down to all members of the "Everyone" group. Prior to uPortal 3.2, permissions inheritence was calculated for principals, but not for targets.
Profiles, Themes, and Structures
uPortal 3.2 introduces the concept of an functional name ("fname") on user profiles. This new field allows the portal to properly associate multiple profiles with a single user without relying on hard-coded profile IDs. Profile IDs should now be globally unique rather than unique per user. uPortal's import/export scripts are designed to assign a default fname to profiles exported from uPortal versions prior to 3.2.
uPortal 3.2 also introduces new themes, structures, and default profiles to enable mobile functionality. Upgrading institutions should ensure that these new resources are created while data is migrated from prior versions.