4.7.1
Release Date: July 2, 2009
Inherited Attributes
An inherited attribute can now inherit from a node in the same record. The sourceRecord element in schema is no longer mandatory.
Directory and default Directory
The class ProfileListContext has been enhanced: it now offers the possibility to retrieve the list of Profiles allowed to interact with the Workflow.
This feature must be considered for the specific implementation of a Directory, in particular for the method getProfiles() .
Dependencies and validation
The class ConstraintContext has been enhanced: it now offers the possibility to specify dependencies between nodes more precisely.
For further details, see the following methods:
As a consequence, the method addValueDependencyToNode(SchemaNode) is now deprecated.
The possibility to manually reset the validation report of an adaptation has been added. This option is available from the validation report section in EBX.Manager. This functionality is only available for users granted with the Administrator role.
Data Services
The WSDL wizard generator has been enhanced so as to offer the possibility to choose the tables and the actions to expose in the WSDL.
Data Model Assistant
Constraint on null value propertry has been removed from the advanced properties section. A constraint on null is now directly usable setting a rule defining either a constraint or a constraint based on an enumeration or on a nomenclature implementing the interface ConstraintOnNull .
Bug Fixes
-
[01783] On Websphere Application Server, an exception is logged when closing connection after read-only statements (re-fix).
-
[01886] NullPointerException while comparing in Merge branches if no difference in table.
-
[01887] EBX.Manager does not show the columns of the primary key at table's record creation if these nodes are embedded in a complex node.
-
[01888] User message " Please submit these updates (max. new occurrences quantity reached) " is not accurate when a node with maxOccurs >1 has reached its maxOccurs value.
-
[01889] The request optimizer starts the index screening at a wrong point. If a request has a predicate corresponding to a part of a composite primary key, it can return a wrong result (some records are missing).
-
[01890] NullPointerException on first access to default hierarchy using
UIHttpManagerComponent(or equivalent selection and filter set). -
[01891] Specific role in default directory are not displayed as expected if no localized label defined.
-
[01892] The setup of a schema throws a NullPointerException if an Inherited Attribute refers to a table (source) which contains a selection node (
osd:select). -
[01893] Unable to download the result of a table content export (XML or CSV) using Internet Explorer under HTTPS.
-
[01894] Cannot apply last modification(s) in a table selection if the source record has been deleted.
-
[01895] Adding a dependency refering a non terminal node is ignored.
-
[01896] Adding a dependency refering a table node set the current constraint in an unknown dependency state.
-
[01897] A migration code (from version 4.1.4) throws SQL exceptions on DB server (table IHD unknown).
-
[01898] Display of actions menu in hierarchies does not take scrolling into account.
-
[01899] Workflow definition: standard actions "attach, dettach and move" might be disabled.
-
[01900] Workflow definition: a referenced process node cannot be "un-referenced".
-
[01901] View: in filter pane, button "apply" and "reset" are available even if the view has no filter criteria.
-
[01902] The request optimizer starts the index screening at a wrong point. If a request has a "starts-width()" predicate corresponding to a part of a composite primary key, it can return a wrong result (too many records are returned).
-
[01903] Dimension link by join table reference the instance from which it has been initialized. It cause severe error when working with instance duplication.
-
[01904] A character "linefeed" in the description of a node in the schema can prevent data display correctly in EBX.Manager if the server is a Unix-like system.
-
[01905] A perspective defined on an hidden table can be view by all possible readers in the perspectives menu. Moreover, when applied, it cause a NullPointerException
-
[01906] In some cases when triggers are disabled while inserting values into a table, the auto-increment value does not take into account the maximum value in the table.
-
[01907] In API, if the method
SessionPermissions.getOccurrenceActionPermissionToDeleteis invoked with an undefined record, it does not take into account removal restrictions specified in schema, onosd:table/mayDeleteproperty.