Home > Release Notes

4.1.0

Release Date: April 19, 2007

Views

This new functionality allows users of EBX.Manager to define their own views on a table by building complex filtering criteria and by specifying columns to display.

This functionality is accessible through the "View" tab at the adaptation instance level.

Manager Component API

This new API makes possible to call EBX.Manager from any Web application. Any user can be transparently authenticated and focused on particular Master Data entities and services. His specific interaction is entirely logged with an optional specific identifier (trackingInfo) and it can be allocated specific permissions. Typical scenarios include workflow integration and intranet integration.

For more information, please refer to:

• Manager Component Introduction

• UIHttpManagerComponent class comment

Auto increments

This new XML Schema extension consists of specifiying that a field of type int or integer in a table must be automatically incremented when a new occurrence is inserted.

For more information, please refer to Auto incremented values .

Manager

New Manager HTML page encoding: UTF-8 (instead of ISO-8859-1).

Specific UI Services (User Interface Services) must be also UTF-8 encoded.

Bug fixes:

• [01386] If a node is constrained by an enumeration facet (e.g. a osd:tableRef ), but its value has become invalid (it has been removed from the enumeration), then the node is presented in EBX.Manager, the first value in enumeration becomes selected. Either a void value or the invalid value should be preselected.

• [01388] UI services are not available on the Reference branch.

• [01394] If a table key has an enumeration, the field appears as a simple string in EBX.Manager and has no corresponding drop down list.

• [01396] Configuration JNDI data source jdbc/EBX_REPOSITORY is not documented.

• [01397] Foreign keys are not correctly displayed using label path(s).

• [01398] When repository is not initialized or ebx.jar is deployed erroneously twice, the error message is not clear.

• [01399] The attribute named "description" can be seized when a version is created but then it is not displayed when a version is selected.

• [01400] The "last modification date" of an occurrence is displayed only when there is a validation error. It should be always displayed.

• [01405] The API does not throw an Exception if we create a branch from a closed one.

• [01407] It is possible to close Reference branch through programmatic API.

• [01413] When the user specifies a table inside another table, the error message raised is not self explanatory ( nullPointerException in table node setup). A suitable message is required.

• [01417] Collapse / expand / collapse sequence on adaptation tree does not display the tree as expected.

• [01410] Key or part of composite key can be modified.

• [01404] Null or empty field on composite keys accepted by import service. If any key field is null, the record can neither be modified nor deleted. If some key fields are empty, the record can be edited.

Known limitations:

• Performance: for large number of tables (in the order of 10,000 tables) and for large number of occurrences (in the order of 10,000,000 occurrences), optimizations are not yet available.

• 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.

• Comparison and Merge: Header informations are not yet included in the comparison user interface nor in the merge process.

  Workaround: for merging header informations, a least one value must be updated on instance.

• 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.

Home > Release Notes