Home > Release Notes

4.7.9

Release Date: February 11, 2010

User Interface

Instance permissions

Access to permissions table is now direct from "permissions" tab.

API

Instance properties

The class ProcedureContext has a new methods for setting instance properties:

• The method setInstanceLabel has been added for setting the label of an instance.

  For more information, see ProcedureContext.setInstanceLabel(Adaptation, UserMessage)

• The method setInstanceDescription has been added for setting the description of an instance.

  For more information, see ProcedureContext.setInstanceDescription(Adaptation, UserMessage)

• The method setInstanceOwner has been added for defining the owner of an instance.

  For more information, see ProcedureContext.setInstanceOwner(Adaptation, Profile)

• The method setInstanceActivation has been added for defining the activation state of an instance.

  For more information, see ProcedureContext.setInstanceActivation(Adaptation, boolean)

DataModel API

The method SchemaNode.getAccessMode() has been added. It returns the access mode that is defined in schema to see and modify a node.

For more information, see SchemaNode.getAccessMode()

Workflow API

InteractionHelper has a new method:

The method InteractionHelper.isComplete has been added. It returns true if the current interaction has been set as complete.

Bug Fixes

Data Model & DMA

• [2392] Option to disable auto-increment value check upon max value of table content does not work as expected.

  It updates last increment value when importing new records with preset incremented values.

• [2406] Table properties on reusable types are overwritten when new tables referencing them are created.

  When an existing reusable type is referenced during the creation of a new table, its table properties are overwritten by the new table.

Import Export

• [2385] Occulted records are erroneously exported to CSV file.

  An occulted record in the child instance part of an inheritance tree is erroneously exported to CSV file.

• [2405] When an archive is exported with a "change set", if the "permissions" check box is not ticked, the export is erroneous.

  The export is erroneous: the differences in the access rights table are exported even if the "permissions" check box is not ticked, whereas the permission table is not exported. Consequently, the archive cannot be imported.

User Interface

• [2350] Workflow execution screen: in IE 8, the warning icon does not appear for instances of deactivated publications

  In the Workflow execution main screen: in IE 8, the warning icon does not appear for instances of deactivated publications.

• [2375] Setting node access permission takes too long in IE.

  Using Internet Explorer to define a specific permission on a node:

  when we click on a specific permission for a node (Read-Write, Hidden ,...), Javascript execution takes too long, especially for complex data models.

Users & Permissions

• [2397] Distributor (only) profile is restricted even out of the context of agreements.

  This fix is an addition to previous bug fix #02373 (cf. release note 4.7.8).

  As many implementation of EBX.Platform declare users without at least built-in "Provider" role, bug fix #02373 has many inconvenients and side-effects in adaptations without agreement management (provider delegation to distributor through agreement in adaptation tree).

  This new fix handle this case.

• [2398] A distributor cannot create child adaptation of its agreement.

  After bug fix #02373 (cf. release note 4.7.8), "Distributor" profile cannot create agreement child, even agreement is a delegation for its profile.

• [2404] A user, with a default permission "hidden" on nodes, cannot update instance values.

  It should be allowed if the user has specific permissions on the required nodes.

  However, update fails with error message: the record may not be updated (no write permission on the following record: "/").

Validation

• [2394] When a "constraintPredicate" is defined in an "osd:select" node, validation is erroneous.

  In case of a validation error due to a constraint predicate on "osd:select", an update that fixes the validation error does not trigger the incremental validation. Furthermore, the validation process cannot be re-run explicitly.

Workflow

• [2314] Only output variables must be displayed for output parameters.

  In task and condition definition, it is possible to select a dataContext variable as output parameter by using a drop-down list.

  Variables that are not marked as 'output variable' must not be displayed in the drop-down list. The dataContext variables must be filtered.

Home > Release Notes