Dear customer
Release 1.5.0-S127 brings the first small change in the release version format. We’re changing the version format to be semantic versioning compliant.
On Elasticsearch, we’ve added full index name configuration and also a bootstrap project sample.
Cloud users can choose one of the predefined account css classes, in line with the account.css changes from 1.5.0.S124.
We’re also announcing deprecation of implicit expression variable and property resolution and enabled both ids and GlobalIds in the REST endpoints on the way to improving the use of GlobalIds.
For detailed information please see the relevant sections.
Best regards,
the edorasware team
Configurable full index name
The index name used by the full index configuration can now be changed using a system property, allowing a single ES cluster to support multiple edoras one full indexes at the same time. Please refer to the upgrade notes for more details.
Release version changes
The version format has changed from MAJOR.MINOR.PATCH.S$sprintId
to MAJOR.MINOR.PATCH-S$sprintId
.
This change was made to make the version format compliant with semantic versioning. For more information see
the semantic versioning specification.
Predefined account CSS classes
Cloud solution users can now choose the color scheme for their accounts from one of the colors of the following table:
CSS Class | Main Color | Main Dark Color | |
---|---|---|---|
account-brown |
|||
account-green |
|||
account-teal |
|||
account-blue |
|||
account-purple |
|||
account-pink |
|||
(empty/default) |
Cloud users can set the field "CSS class" in the account form to one of the values of the "CSS Class" column in the table. On-premise users can create their own accounts.css files.
Please refer to {account-doc} for more information.
Implicit variable/property resolution
Since 1.5.0-S127 we have made resolving implicit variables/properties deprecated. It means that all *.getVariable\*
methods on the domain object and all *.getProperty/ies\*
methods on the domain definition object are now deprecated.
If the methods are used inside an expression (e.g. in the process execution) a warning message is logged.
The change is done to as a conceptual simplification and to improve performance of expression evaluations. Because the deprecated methods are wildly used, we’re announcing this change well in advance.
Use the Local
counterparts *.getLocalVariable\*
and *.getLocalProperty/ies\*
instead of *.getVariable\*
and *.getProperty/ies\*
methods.
Identity manager bean interface improvements
The identityManager
bean interface has changed:
-
the bean methods supports collections instead of lists
-
support for both
String
andGroupId
items in the collections
Bootstrap Elasticsearch integration sample
The bootstrap project now contains a sample Elasticsearch custom index configuration and the edoras one Developer Guide has been updated to include more information about defining and testing custom indices.
GlobalId in REST interface
The rest interface supports ambiguous ids. This means that REST requests can contain either workobjectId or globalId.
The response to e.g. rest/frontendObjects/TSK/${workObjectId}
is equivalent to rest/frontendObjects/TSK/${globalId}
.
The frontend implementation has reflected the change and uses mostly globalId`s. The goal is to transform the product
and solutions from `workObjectIds
usage to globalIds
. Because you might be using workObjectIds in URL expressions,
we’re supporting both until the workObjetIds are phased out.
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.