Home > ReleaseNotes

4.2.7 fix 001

Release Date : October 16, 2007

Java Doc update

 
Any update procedure that is executed on Reference Branch can update content according to privileges on adaptations.

For more information, see:

Bug Fixes

  • 01555 With manager component, when selecting a node and then going down in complex node, the user cannot return to parent node because the navigation link is not displayed.
  • 01556 Import / Export archive buttons are not available according user permissions.
  • 01557 The manager component's header have label and layout errors.
  • 01559 Applying search on a complex node with maxoccurs > 1 causes an error "An error occurs while applying current filter. This filter has not been applied.".
  • 01560 Applying search on selection node auses an error "An error occurs while applying current filter. This filter has not been applied.".
  • 01561 Selection nodes (mdm:select) can be used in view definition, either in field selection for criteria (but their values is always null, see documentation) and in field selection for display (but they are not displayed in table view).
  • 01562 The owner of the repository and the administrator cannot change branches permissions when they are restricted to hidden or read only on the reference branch.
  • 01563 Branch and version creations' performance is affected when repository defines numerous homes.
  • 01564 Partial merge performs a full merge when calling it as a service.
  • 01567 If a profile has the right to close a branch owned by another user, the close procedure throws an exception when closing its initial version.

4.2.7

Release Date : October 10, 2007

Bug Fixes

  • [01541] If an access to webMethods Master Data Manager is done via UIHTTPManagerComponent without redirection URL, when the user log out, he is redirected to the login page which is focused.
  • [01543]If an « on error » redirection URL is defined in webMethods Master Data Manager, the redirection is not done if timeout and user session is not sub session nor external.
  • [01549] With manager component, the close button is not effective in some cases and line to calle should not appear.
  • [01550] Administrator profile may remove its privilege to manage access rights.
  • [01551] String with facet maxLength > 80 has a textarea HTML as UI. Under Microsoft Internet Explorer 6 or less, this textarea may add an undesired Carriage Return character at the end of the user input.
  • [01552] When two access rights on services are given to a profile with restrictive mode = no, the most permissive is not used.
  • [01553] The method ServiceContext.getCurrentAdaptation should not throw an exception if only one occurrence is selected in the manager.
  • [01554] Key value with double quote is not handled as expected using xpath predicate. As a consequence, change set import may throw an exception Internal Error : We shall have the occurrence we want to add.

Performance enhancements

Concurrency

When an update is performed on a branch (and more particularly a massive update), other user sessions are no more blocked for viewing the content of the branch.

However two concurrent updates on the same branch are still exclusive, that is, if a second user asks to perform an update on a branch that is already being updated (for example a procedure is being executed), this second user will have to wait for the first update to terminate.

The validation is also no more exclusive of a concurrent update. This implies that a branch's validation report has no guarantee to be up-to-date and consistent, unless it is protected against concurrent updates. There are two means to protect a branch from concurrent updates:

  1. By performing validation and subsequent operations inside a procedure execution. This solution can be used only if there are no user interactions between validation and the subsequent operations that require the same consistent and unchanged view. For example, an export procedure would perform the validation and if there are no validation errors, it performs in the same procedure the export to other systems.
  2. Otherwise, by setting an explicit persistent lock.
    For more information on persistent locks, see the method Repository.lock(...).

Branch and version creation

SQL requests to the underlying database have been optimized for branch and version creation. On Oracle, a benchmark on a large repository shows that the creation time has been divided by 13 (from 6 seconds to 0.4 seconds).

However, the optimisation has no particular effect on repositories with an average low number of occurrences per table (more precisely a low number of blocs per tables with at least one bloc). For example on a repository with 250 occurrences per defined tables, benchmarks do not notice an enhancement.

Also benchmarks on standalone HSQLDB do not improve (this is probably because standalone HSQLDB runs in the same Java virtual machine as webMethods MDM engine).

User interaction enhancements

The following enhancements have been made on webMethods Master Data Manager tool:

  1. Various user interaction scenarios now include a wait page when some calculation is needed on server-side (table selection, validation, agreement publication, adaptation activation, table's filters reset, etc.).
  2. A "Home" link has been added in the left upper corner of the page when webMethods Master Data Manager is called in focused Manager Component mode (for example, component focused on a branch). This link positions the session back to its initial page.
  3. In Manager Component mode, if an "Access denied" is responded, user session was not always cleanly reset. This has been corrected.
  4. In Manager Component mode, "log out" buttons aspect has been uniformized.