Home > Release Notes

4.2.0 fix 001

Release Date : June 8, 2007

Bug Fixes

  • [01444] The link mdm:select does not work for adaptation instances under an agreement.
  • [01445] If a table trigger handles beforeModify and sets new values on the occurrence to modify, these new values are not taken into account.
  • [01446] The definition of a specific permission on a node under a table that has already a default permission is not taken into account in all combinations of access rights.
  • [01447] On instance permissions, the list of nodes specific permission includes complex values that are not terminal. However the specification of a specific permission for such a node is not taken into account.

4.2.0

Release Date : June 5, 2007

Interactive merge process

The comparison and merge user interface has been completely reviewed so as to enhance the display and the interactivity.

From this version, the user is able to select which changes must be taken when he is doing a merge. He can make decisions on various Master Data entities and granularities: terminal node value, occurrence, table, and also instance values, instance header and instance permissions.

Limitations: When one user is performing a merge, other users can still access to the home being merged. If an update is done during the merge, this update is not systematically seen in the differences. For a safe merge, it is advised that the branch owner first forbids the writes on the branch.

Export/Import between repositories

webMethods MDM Archive files are now enabled with change sets. That is, they define not only the current state of a home but also the updates that have been done in this home since a previous version.

The import and export of archives (including change sets) are subjected to access rights. The permissions have been modified to handle this. As a consequence, the programmatic procedures previously developed may have to be adapted either by being executed as an authenticated user allowed to export or import, or by setting all privileges in the procedure (method ProcedureContext.setAllPrivileges()).

webMethods Master Data Manager now provides built-in export and import wizzards. The button is available on the branch technical pane.
Warning: the import wizzard does not import Archive that have not been exported with a change set.

The export / import functionalities are also available as programmatic API on ProcedureContext class.

Comparison of occurrences

The table user interface now provides the ability to select two occurrences so as to compare them.

For selecting easily the occurrences, the user has the possibility to use quick search and specific filters.

Instance header management

The management informations associated with an instance are called the header. They have been extended and included in the comparison and merge process. They include the internationalized label and description of the Master Data instance (adaptation), the parent reference, the activation state and delegation optional information ("agreement").

Triggers

The new schema declaration, mdm:trigger, allows to add callbacks when operations are performed on a table and also on an instance (instance creation and deletion).

Triggers benefit of the common features of programmatic schema extensions: JavaBeans declaration at schema level; a context-enabled setup phase at schema validation time; and context-enabled methods at execution time.

For more information, please refer to:

Sort API

The API now provides the possibility to sort request results. See RequestSortCriteria class.

Known limitations

  • Validation performance: for a very large number of tables (in the order of 10,000 tables) with many occurrences (in the order of 10,000,000 occurrences), validation still take several minutes.
  • Merge process: in case of instances' add-add conflict, tables in the source are ignored.
    Workaround: first create instances and merge, then tables may be populated and merged.
  • Repository locking: it is not yet detected when two Java virtual machines share the same physical repository.
    Workaround: Repositories' administrator must take care that a repository is not refered by two environments.
  • Access right management: a node can be set as ReadWrite even if it is not adaptable according to schema definition.