4.2.4
Release Date: July 12, 2007
Bug Fixes
-
[01490] "Illegal state exception" during table import.
-
[01491] Even if the user has writing rights, a 'submit' is not allowed in a table where elements are:
- an id (autoIncrement),
- all other elements are stored in Non terminal intermediary nodes.
-
[01488] On a filtered table. If a record is modified in tabular mode and doesn't match the filter anymore, the record stays in edition mode and is not filtered (even if we go back to the "form" edition mode). Furthermore, the button "cancel" does nothing in this case.
-
[01496] IllegalArgumentException when browsing the branches, because a home owner is undefined.
-
[01497] When an occurrence is in overwrite mode, the button 'overwrite' is still enabled. If the user clicks on it he gets an 'Invalid request' message.
-
[01498] When schema is validated, a NullPointerException is thrown in AbstractFacetTableRef.setup.
UI Services on branches and versions
UI Services can now be run in the context of a branch or a version. Those services are declared in the document
module.xml
.
As those specific services can include built-in services such validation and merge and also specific procedures, it is possible to provide advanced processes to users. For example, "Master Data Propagation" can be a well-defined process that include versioning and validation.
For more details, see UI Services on branches and versions .
Validation API
A fully-featured validation API is now available for getting the validation report of adaptation instances. The main entry points are:
Lock/unlock API
It is now possible to lock a branch, for preventing any updates during sensitive operations (for example between Master Data Validation and their propagation). The main entry points are:
Version pane
When the user selects a version he will now be directed to a version pane that is similar to the branch pane (with less options). This new pane also includes the "Services" option for executing service in the context of the branch.
Permissions for instance deletion and activation
It is now possible for the owner of an instance to define permissions:
-
for deleting an adaptation instance;
-
for activating and deactivating an instance.
Those permissions are defined in the standard instance permissions ("Permissions" tab on an adaptation instance).