Post-Upgrade Actions | ||
---|---|---|
Previous | ||
Upgrading |
This chapter describes the actions required after the upgrade process was complete. These actions depend on the current version of Convergence for MDM and the version you upgrade to.
Note: If no actions is indicated in this chapter for your versions, then no action is required after restarting the Convergence for MDM application instances.
Convergence for MDM v3.0 introduces changes that require post-upgrade actions, as listed below.
The built-in Default Application (No Application) that existed in previous releases – and could not be modified or deleted – disappears in v3.0. When the upgrade takes place, an application named Default Application is created as a replacement. This application provides the same features, but can be modified or deleted.
Recommended Action
If you do not need a Default Application and wish to enable user access only via your applications, remove this application after the upgrade.
This version introduces the capability to configure application features (Entities List, Dashboards, Lineage, etc.), and allow access to the selected features depending on roles.
Recommended Action
Review the configuration for each of your applications, un-select features to hide them and/or set roles for features access.
Attribute groups are no longer supported starting with Convergence for MDM 3.0. The default forms generated when displaying entities in applications now organize attributes as User Attributes and Built-in Attributes
Recommended Action
Create forms and table view, business objects and business object views to display entities content to replace attribute groups.
This version introduces a new computed Attribute Type field for the form attributes. This field if computed for all forms the first time you open a form view.
Action Required
After the upgrade, open any form view in the model. An Upgrade Views message prompt appears. Click OK to start the upgrade. At the end of this process, the form view editor opens. Press CTRL+S to finish the update of all the views.
Note: This process takes place once. You should not be again prompted for upgrading the views.
In form views, it is no longer required to explicitly choose a key attribute among the Golden ID, Primary key or Source ID. If you add the entity’s Primary Key attribute to a form, the form will automatically display the key that is the most appropriate for the context (master record, golden record, source record, etc.) and the type of entity (fuzzy or exact matching).
For example:
Recommended Action
Review the form views that include key attributes, and replace these key attributes by the entity Primary Key.
In form views created for the purpose of data entry, replace also the Source ID with the entity Primary Key. This second point is important as the Source ID only recognized as a simple text field. If you want to use the display component specific to IDs, replace the Source ID by the Primary Key.Only use a specific key only if you want to explicitly display this key in a context: For example, to display the Golden Record ID when viewing a master record.
Form views no longer support multi-column layout for forms and sections. When the upgrade takes place:
The result are forms with a Flow Layout. The Grid Layout enable you to configure sections and attributes at absolute positions on a grid, offering the superior features than a multi-column layout.
Recommended Action
After the upgrade, review all the form views. For those of the forms requiring a specific layout, configure them with a Grid Layout and reposition the sections and attributes to restore the form appearance.
Business object views now support defining form views for browsing data and for data entry. As a consequence, certain business object views pairs (one used for the sole purpose of data entry – marked as non-visible -, plus one used for navigating) can be merged into single business object views.
Recommended Action
Review the business object views and consider merging data-entry-only business object views with their navigation counterparts.
The upgrade process preserves user-defined filters, but resets the columns selection and user-defined sort in the data tables to the default values:
Recommended Action
Application users should review the column displayed as well as the record sort and reapply their preferences.
Previous | Top | |
Upgrading |