Home > Release Notes

4.3.0

Release Date: January 18, 2008

Warning on permissions

More restrictive permissions have been implemented on this release for procedures' execution. These new restrictions can prevent a user to execute a specific procedure that he could execute with a previous versions. So, make sure that each profile has the appropriate permissions that enable him to perform a target procedure. Moreover, you can still use the method ProcedureContext.setAllPrivileges(true) in order to disable specific access controls for a given service.

Bug Fixes

New EBX.Manager Functionalities

Search in data model

The end user can henceforth perform a search through the data model. The new search tool can be used to find attributes, tables or columns for which label, path or description contain the given search criteria and to navigate quickly in the instance view.

Mass update

The end user can now apply the same modifications on several records simultaneously.

The user must first select a single record and submit the desired modifications on it. He then selects the records on which he wants to apply these modifications and choose in the menu "Actions" the item "Apply last modification(s)".

Last update by

The last user who has modified an adaptation (instance or record) is now displayed.

Note: Information about last user is updated only for local modifications. That is, if the adaptation is a schema instance, not an occurrence, the user persisted is the one who has performed modifications on the instance not on contained table records.

The last user information is also available through class Adaptation .

Permissions on branch services

It is now possible to define permissions on branch services thanks to EBX.Manager interface. It is accessed on the "Access Right" page of the branch.

By default, all branch services are enabled for a given profile. As other branch permissions, an administrator or a "super owner" of the branch can view and modify these services permissions.

For more informations, see Permissions section.

Engine Improvements

Memory usage of comparisons

The implementation of comparisons framework has been reviewed so that use cases are less memory consuming.

Audit trail

The updates detail is now activated by default (in previous versions, it was deactivated in the context of procedures if detail was not explicitly enabled). A consequence is that larger disk space can be involved, more particularly for mass-updates.

For more informations, see Audit Trail section.

API changes

Triggers' methods

The declaration of " throws OperationException " has been extended to the following methods:

This API change preserves ascendant compatibility, unless a trigger implementation calls super.handle... . 

Class SessionPermissions

The behaviour of methods SessionPermissions .getOccurrenceActionPermissionTo... has changed: if adaptation specified as argument is an instance instead of an occurrence, they throw IllegalArgumentException instead of returning null . 

New methods have been added:

New EBX.Platform Configuration Wizard

EBX.Platform Wizard helps to quickly configure new EBX.Platform installation.

For production environment, administrators should consider to configure manually ebx.properties file.

Obsolete Properties

The following properties have been removed from ebx.properties file:

#################################################
## Deprecated. 
## EBX.Platform repository minimal internal index for inserting new records
#################################################
#ebx.repository.insertStartIndex=100
################################################# 
## Deprecated. 
## Default root path for modules. 
## It is used only when EBX.Platform is not running in a servlet container 
## Usually, it is the 'webapps' directory. 
## This property is required but it may have a void value.
#################################################
ebx.modules.directory=

################################################# 
## Deprecated. 
## Path for persisted sessions
#################################################
ebx.sessions.directory=${ebx.home}/ebxSession

#################################################
## Deprecated. 
## Path for reporting files
#################################################
ebx.reports.directory=${ebx.home}/ebxReporting

#################################################
## Deprecated. 
## Automatic reporting batch parameters
## By default automatic reporting batch is not activated 
## If automatic reporting batch is activated, it is 
## schedule by default at 03:00 AM
##################################################
#ebx.reports.activate= false 
#ebx.reports.activate=true 
#ebx.reports.timer.hour= 2
#ebx.reports.timer.minute= 30

################################################# 
## Deprecated. See ebx.directory.factory 
## Organization Database connection adapters class name
## (optional, default uses internal EBX.Platform repository)
#################################################
#ebx.core.org.OrganizationDatabaseConnection=com.onwbp.core.org.DefaultOrgDatabaseConnection



################################################################
## Deprecated. 
## EBX.Platform persistence system FileSystem is no more supported
################################################################
#ebx.persistence.factory=FileSystem

################################################# 
## Config VM logs (for reporting feature)
## MUST start at index 0.
#################################################
#vm.0.logDir=${ebx.home}/ebxLog

ebx.log4j.category.log.reporting= INFO, ebxFile:reporting
ebx.log4j.category.log.reportingMail= INFO, ebxFile:reporting

#--------------------------------------------------
ebx.log4j.appender.reportingMail.Threshold= ERROR
ebx.log4j.appender.reportingMail=com.onwbp.org.apache.log4j.net.SMTPAppender
ebx.log4j.appender.reportingMail.To=recipient@domain.com
ebx.log4j.appender.reportingMail.From=reporting@domain.com
ebx.log4j.appender.reportingMail.SMTPHost=smtp.domain.com
ebx.log4j.appender.reportingMail.Subject=EBX.Platform Reporting on Site ${ebx.site.name} (VM ${ebx.vm.id})
ebx.log4j.appender.reportingMail.layout.ConversionPattern=**Site ${ebx.site.name} (VM${ebx.vm.id}) ** \
%n${log.defaultConversionPattern}
ebx.log4j.appender.reportingMail.layout=com.onwbp.org.apache.log4j.PatternLayout

Home > Release Notes