Home > Release Notes

3.7.0 [434]

Date  : November 6, 2006

 

Repository

  • webMethods MDM Preloading
      webMethods MDM Repository is preloaded at server startup. Set mdm.repository.preload to false to disable this new feature.

Manager:

  • Adaptation edition lock:
      A user who initiates an Adaptation edition is able to lock it for its own usage.
      All other users cannot modify this Adaptation edition and are notified of such lock.
  • Adaptation occurrence pagination:
      Large occurrence may be display/edit through several pages, allowing light-weight pages and nodes categorization.
      Occurrence nodes split refers to complex node wrapping and ""Max adaptation node quantity" value in webMethods Master Data Manager adaptation.

Documentation:

  • [01335] Add execution requirements (Web browser version, etc...).

Bug fixes:

  • [01319] When a long transaction has failed because an occurrence has been concurrently updated, if the user clicks on cancel, then he won't be able to resubmit (error message remains the same)..
  • [01320] Inconsistent behavior for nodes of type List:
      If ValueContextForUpdate.setValue(null) is called on a node with maxOccurs > 1, then the value set and returned by the next getValue() is not null but a new array list.
      This problem is also related to the persistence format, see CfxConstants class comment.
  • [01321] - [01325] Remove unused code and services form _mdm-tutorial code.
  • [01326] When there is an exception in a procedure execution, the exception causes chain is not displayed nor historized consistently.
  • [01327] Inconsistent behavior for nodes of type List:
      On a node with maxOccurs > 1, if ValueContextForUpdate.setValue(aList) is called and aList has null elements, those elements will be ignored when serializing the content. Then the list returned by the getValue() will be different if cache is refreshed or not.
  • [01328] In an external export, where ExportsSpec.isIncludesTechnicalData() is true, unneeded internal attributes are serialized for table occurrences.
  • [01329] When using RDB as persistence system, the memory used isn't reduced after all instances have been removed.
  • [01331] On Windows File System, adaptation reference must be unique in an insensitive-case policy. This restriction has an impact on instance creation and also on import process (regardless underlying persistence).
  • [01333] Automic Migration of repository:
      The automatic migration may be triggered even if the target repository is existing. This will at least block the initialization of the cache and display an exception that is difficult to understand.
  • [01334] Automic Migration of repository:
      If at least a schema used in the repository has errors, the migration cannot be performed. If this is the case, the automatic migration should :
    • 1) stop before the installation of the new target repository (so as to let the datastore in a consistent state);
    • 2) log an explicit error message.

 

Home > Release Notes