4.7.2
Release Date: July 20, 2009
Backward compatibility
The deployment descriptor (web.xml) for EBX.Platform web applications has been modified to comply with the Servlet 2.3 specification . This allows to use the datasource v5 facility in Websphere Application Server out of the box. Customers using the legacy datasource v4 facility in Websphere Application Server are required to repackage the "ebx" web application .
Workflow
The workflow designer is now able to insert a node between two other nodes.
Inheritance
The behaviour of inheritance has been clarified for the various combinations of definition modes:
-
The specification of the various definition modes has been moved from the table page to the inheritance reference page , it has been completed and the inherited mode is now explained.
-
The definition of the root mode and the overwriting mode has evolved: this information is no longer intrinsic to the record, but is evaluated dynamically, depending on the existence of a parent with the same primary key. Consequently, the distinction between both notions becomes pointless in the context of a record creation and for its validation.
-
The deriving mode has been removed from the documentation... Indeed, it was already no longer proposed in the Manager and its usage has been considered a bit difficult to understand for the end user. In the improbable case where a repository defined deriving records, these records would be considered as either root or overwriting (see previous item). Their parent key will also be ignored.
API
Computation of Differences
The method
compareOccurrences
has slightly evolved. The parameter
showDetails
will be forced to false if not in resolved mode.
Inheritance and definition modes
As mentioned above, the inheritance specification has evolved so as to clarify the behaviour and to make it tolerant to any combinations of definition modes between a table and its parent table. This has the following impacts on the API:
-
Since 'overwriting' and 'root' modes become dynamic, the record creation does not involve these notions: on interface
ProcedureContext, the methodsdoCreateRootanddoCreateOverwritingconsequently have the same behaviour: they both invoke the new methoddoCreateOccurrence, that is to be preferred. -
The method
ProcedureContext.doCreateDerivingbecomes deprecated, it henceforth throws an exception. -
The methods
SessionPermissions.getOccurrenceActionPermissionToDerive,DefinitionMode.isDerivingand the constantDefinitionMode.DEFINE_DERIVEalso become deprecated. -
The evaluation of programmatic permission rules in the context of a record creation has also been clarified, so that a virtual record is always passed as argument and this record belongs to the current table (see AccessRule.getPermission ).
Clarification of "before creation" trigger
Limitations on the "before creation" trigger context are henceforth explained. See TableTrigger.html.handleBeforeCreate .
Bug Fixes
-
01908 Table grid header may not be sized as expected.
-
01909 In workflow email configuration, a NullPointerException is thrown if no
fromvalue defined. -
01910 Overwriting a record which has been occulted in the parent adaptation causes a NullPointerException.
-
01911 Blank screen in EBX.Manager if permissions have be defined with a wrong syntax on the id of the user / role.
-
01912 Blank screen in EBX.Manager if permissions have be defined with a wrong syntax on the id of the branch.
-
01913 In case of an
osd:selectwhich specifies a predicate that targets a single record (i.e. fully defines the primary key value in the target table); if the target record does not exist, EBX.Manager reports an 'access denied' (instead of an empty filtered view of the target table). -
01914 DataServices 'getChanges' operation should specifiy maxOccurs=unbounded on element 'updates/changes/change'.
-
01915 DataServices 'getChanges' operation should specifiy maxOccurs=unbounded on element 'updates/changes/change/path'.
-
01916 DataServices 'getChanges' operation should specifiy maxOccurs=unbounded on element 'deleted/predicate'.
-
01917 Data Model Assistant generates an invalid schema if a
tableRefdefines custom labels. -
01918 Workflow process tokens are not restarted as expected after failure.
-
01921 Editor of multi-occurrences nodes does not show ongoing updates (occurrence deletion) if the form is redisplayed due to a form validation error.
-
01922 Label pattern specified by a customized hierarchy definition is not taken into account anymore by the method
getLabelFromDefaultPatternofUILabelRendererContextclasses (regression since 4.7.0). -
01923 The archive's import fails when an occurrence is to be altered or created, and when a record with the same primary key already exists, but is occulted, in the target table.
-
01924 Permission rules (
AccessRule.getPermission) are not always call in table record creation mode.