4.2.6
Release Date: September 12, 2007
Bug Fixes
-
[00225] In documentation, for access properties, we must add the following default cases:
- if the node is a computed value (use of osd:function) then it is "R-";
- if the node is a complex multi-occurrenced then it is "RW".
-
[01277] NMTOKENS is a list of NMTOKEN, so "token1 token2" should be equal to "token1 token2".
-
[01516] No pattern facet is implemented for datatypes NMTOKEN and NMTOKENS.
-
[01517] When parsing user input, a non empty sequence of whitespaces is preserved in cache but it is actually collapsed in persistent repository.
-
[01518] In history.xml, new values are trimmed even if they are indeed preserved in repository.
-
[01520] When a user create a version of a branch, the owner of the version is "Administrator". Thus, the user cannot see the content of its version.
-
[01521] An archive import fails if an element declared as osd:table contains an element with the same name.
-
[01522] An XML import aborts and returns a message that is not clear if the XML document contains an element that is not declared in the schema.
-
[01525] In XML Schema document, if two constraints are specified ("osd:constraint" tag) on the same element, this is considered as a schema validation error.
Whitespaces management
The behaviour toward whitespaces has been extensively reviewed. A more consistent approach has been adopted for the various processes that involve whitespaces management: XML import/export, archive import/export, user input/display, audit trail.
Three main principles have been applied:
-
conformance to XML Schema recommendation that requires to preserve whitespaces for xs:string elements;
-
prevention of ambiguous user input for primary keys by means of a default pattern;
-
support of any specific customer's Master Data (including primar keys with whitespaces).
For more details, see Whitespaces management .
Warnings :
- Since XML imports now preserves primary keys, they may have a different result from an import on a previous version.
- The new default constraint on primary keys may to new validation errors on existing repositories. Those errors can be removed by specifying a xs:pattern that accepts whitespaces.
Comparisons between branches and versions
On Manager, a new option has been added to branch and version panes for comparing them with another branch or version.
Grant of specific privileges at session level
The following new method have been added to the API
-
Profile.forUserWithSpecificPrivilege(...) : returns the user reference specified, with the specific privilege granted.
-
Profile.forUserWithSpecificPrivileges(...) : returns the user reference specified, with the specific privileges granted.
Those methods can be used in the directory authentication methods for granting a user the privilege of executing a specific service only under specific and well-controlled circumstances (for example a merge can be done only if branch is fully validated).
The particular authentication can be safely ensured by means of a ticketing process.
Property for Manager import commit threshold
A new property,
ebx.manager.import.commit.threshold
, has been added for setting the commit threshold when the user performs an import from the branch pane.
For more details, see Main Configuration .