Home > ReleaseNotes

4.3.1

Release Date: February 20, 2008

 

Backward compatibility

 
  1. Full permissions controls have been added on this release for some actions (create branch, create version and merge), when they are executed programmatically (see below).
  2. Correction of bug [01378] adds a check at schema validation time.
 

Bug Fixes

 
  • [01378] If a schema element is a foreign key (osd:tableRef), it must be of type xs:string, otherwise an exception is raised at runtime. Schema validation should check this implicit constraint and report an explicit error.
  • [01653] An erroneous or missing adaptation schema causes a NullPointerException in EBX.Manager.
  • [01658] Generated link for records which have whitespaces in their primary key is not correct.
  • [01659] When displaying a comparison in unresolved mode, a node's value status (inherited, overwritten, occulted) is not displayed correctly, due to bad value in NodeDifference object.
  • [01660] Datasource is exhausted after a short navigation in EBX.manager, as every invocation on wizard methods creates a new cache and, finally, a new connection.
  • [01661] Search, filters and CfContentValidationContext::getValue(Path path) do not work properly when a complex terminal element contains list.
  • [01662] Closed version still appears in comparison menu.
  • [01663] The action "close version" should have its own permission (currently, a user can close a version if he can create one under the same branch).
 

Data Services (Beta Version)

 

Now EBX.Platform embeds generic Web Service access to data. See documentation.

Note: Data Services is currently a Beta Version. WSDL contracts can slightly evolve in next release.

 

Permissions management

 

New permissions on branches

The following permissions have been added for branches:

  • A new item, named "close version", has been added. Hence, it is now possible to define explicitly whether a user can (or cannot) close a version on a target branch.
  • Moreover, permissions on branch services can now be defined for being set at child branch creation.

Additional controls on some programmatic access

Full permissions checks have been implemented on this release for the following procedures execution:

  • branch creation and version creation: method Repository.createHome;
  • merge: method ProcedureContext.doMergeToParent.

Backward Compatibility Note : These new restrictions can prevent a user to execute an above method that he could execute with a previous EBX.Platform release. So, make sure that each profile has the appropriate permissions that enable him to perform the target method. Moreover, for ProcedureContext.doMergeToParent, you can still use the method ProcedureContext.setAllPrivileges(true) in order to disable specific access controls.

 

New EBX.Manager Functionalities

 

Optimized component for large enumerations

A new graphical component replaces the previous drop-down component for values that depend on an enumeration (this is the case for XML Schema elements that declares xs:enumeration, osd:tableRef, osd:constraintEnumeration). This component facilitates user interaction, particularly when the enumeration has many items.

In order to use this component, it must be enabled by means of the option "Enable advanced input component" in Manager adaptation.

Description of permissions restrictions for branches

EBX.Manager interface for branch permissions definition has changed:

  • A new item, named "close version", has been added. Hence, it is now possible to define explicitly whether a user can (or cannot) close a version on a target branch.
  • Moreover, permissions on branch services can now be defined for being set at child branch creation.

Note that, user messages have been added to the following actions on homes if they are disabled: create branch, create version, initiate merge, close home. These messages explain the reasons of the restriction.

Home > ReleaseNotes