9.3 Upgrade Guide

Before upgrading the platform and its add-on components, there are certain system changes that customers need to be aware of when moving to 9.3 from an earlier version. This list may not be comprehensive; however, along with the full release note set, it provides a starting point for upgrade evaluation.

As with every release, some components are deprecated, removed, desupported, or not backward compatible for various reasons. Customers should also read the Platform and Software Support Changes release note (here) and each individual release note for items that may not be listed below, future updates, and software end-of-life notifications.

  • Support for these platform versions is ending as of the date shown: 8.1 (November 1, 2019); 8.2 (June 1, 2020); 8.3 (November 1, 2020).
  • IE 11 is no longer a supported browser. Refer to the 9.3 Platform and Software Support topic (here) and the Platform and Software Support Changes release note for details (here).
  • All Red Hat Enterprise Linux / Oracle Enterprise Linux 6 versions are desupported with this release.
  • Oracle Database version 12.1.0.2 is desupported.
  • Adobe InDesign CC 2017 (Client and Server) will no longer be supported in the next feature release; customers should transition to a supported version.
  • The outdated DTD for the output template format is no longer available on the API documentation page. More details can be found in the API Enhancements and Updates release note here.
  • BMECat 2005 will no longer have the 'Generation date' parameter. Instead, a new GXML instruction will automatically generate the current date and time of an export. For already existing BMEcat 2005 configurations where the Generation date field has been manually maintained, the Generation date field will remain. Refer to the Data Exchange Enhancements and Changes release note here.
  • The option to import eCl@ss Basic CSV files has been removed with the 9.3 release, and an error will appear if users try to upload anything other than eCl@ss Basic XML files. Refer to the Data Exchange Enhancements and Changes release note here.
  • When a user makes the selection by clicking in the Web UI Tree, the Tree no longer shifts focus. Previously objects in the blue hierarchy took priority focus when making node selections.
  • When creating a reference to add via the Multi-Reference Editor, object types displayed in the Create Tab of the Add Reference Action dialog are now identified by the object Title rather than the object ID.
  • The default behavior of toolbar actions has been changed for Node Lists. User experience will be different in Web UI when taking the upgrade. Refer to the Web UI Enhancements release note here.
  • Simple Export has been revamped and renamed to Custom Export. Functionality was added and labels have changed; nothing was removed. Refer to the Web UI Enhancements release note for details here.
  • Customers that have entities and classifications using your system configured primary image reference will now have images for these when viewing them in Web UI Node Lists using a Thumbnail header or in the filmstrip or gallery display modes. This functionality cannot be removed; however, the image reference can be changed.
  • Existing setups with Business Action with Web UI bind will now have a 50 object max applied. The button will be disabled if more than 50 nodes are selected when using this on Node Lists. However, for customers to increase that max, they can do so in the button configuration. It is important to note that end users working on screens with the Business Action with Web UI Bind component already configured will experience no change in performance aside from a new system default restricting node selections to no more than 50. However, when admin users access the designer for those screens, the designer will display as being in error and disallow configuration changes until the error is cleared. Additionally, the field for the 'Max Number of Nodes' parameter will be blank: the default maximum of 50 is applied by the system. To clear the error, designers must manually add a value to the new 'Max Number of Nodes' parameter in all Business Action with Web UI Bind components configured for the screen.
  • Users will notice some layout changes on Web UI screens intended to fix minor issues (e.g., unnecessary scrollbars).
  • When applying dimension dependencies to attribute or List of Values (LOV) objects, users now must select the dimension point where existing values should be applied. Users are unable to bypass this selection before moving ahead.
  • The Children of Type screen has been withdrawn. Users should use the Children of Types screen prior to transitioning to 9.3 so that functionality is not lost with an upgrade.
  • The 'External Validator' and the 'Post Save Validation Script' parameters have been removed from Web UI. Also, the 'Run Server Script Action' component has been superseded. Full details can be found in the Web UI Enhancements release note, under the 'Changes to validation functionality' subheading here. Additional components have also been superseded (Move Action and Initiate Business Action) and can also be read about in the Web UI Enhancements release note.
  • The most recent survivorship rules are now comparing STEP changes with Last_Edit_Date attribute when determining newest value of an attribute during a match and merge import. STEP changes were previously not considered.
  • The Data Container Attribute View Editor and the Advanced Merge Data Container Header Web UI components have been superseded. Refer to the Customer MDM Enhancements release note for information on alternate components here.
  • The configuration for PLM storyboards has been updated to include PLMColor as a product object type instead of an asset.