Dear customer
In this release we have improved the way that beans are enabled for use in expressions on the edoras one server.
In this release we are also announcing an upcoming change to the behaviour of the edoras one query API.
The query API implementation changes affects parent properties and variables loading.
For detailed information please see the relevant sections.
Best regards,
the edorasware team
Expression bean configuration
Previous releases used an expression.bean.whitelist
property to configure Spring beans that can be
accessed using a backend expression (e.g. from a process model). The whitelist has now been removed
and replaced with an annotation (@ExpressionBean
) which can be used to mark beans that should be
accessible from an expression. Please refer to the upgrade notes for more details.
Announcement: Query API behavior change
Release 1.5.0.S122 will include a behaviour change for the edoras one query API. This change is announced here as there may be an impact for code that implements certain expressions. For details please refer to the upgrade notes.
root
, parent
expression resolving propagates error
Release 1.5.0.S120 has changed expression resolving. The default behaviour in the case when root
, parent
base does not exist (or is not accessible because of access rights)
is to propagate an error. The previous versions did not propagate an error. They just returned null object from the expression.
Changes to default loading of entity hierarchy values
Hierarchy values, that is, hierarchy variables in case of work objects and hierarchy properties in case of work object definitions are no longer implicitly loaded when querying for the work objects and work object definitions.
For explicitly loading hierarchy entity variables and hierarchy entity definition properties the WorkObjectQuery.Hint.INCLUDE_PARENT_VARIABLES and WorkObjectDefinitionQuery.Hint .INCLUDE_PARENT_PROPERTIES have to be respectively used while querying for the work objects and work object definitions.
In cases where the legacy default loading support is required, the hierarchy-values
spring profile can be used to enable the same.
Upgrade notes
Please have a detailed look at the upgrade notes for this version so that you are able to upgrade to the newer version in a controlled manner.
If you have issues viewing the email then click here to view the online version. If you want to unsubscribe from the release notes please send an email to unsubscribe@edorasware.com.