Dear customer
In this release we introduce several improvements such as the front-end project setup and CMMN
authorization. In addition, the profile security-low
with CSRF tokens disabled was implemented.
For detailed information please see the relevant sections.
Best regards,
the edorasware team
CMMN authorization improvements
CMMN case access authorization is implemented based on a 'run-as-user' concept. There are two types of such users, the case owner and the acting user.
By default, the acting user is set to the current edoras one user invoking an action on the case (e.g. by clicking an action button or by completing some task which causes a reaction in the case model).
Internal CMMN state operations are performed under the case owner. Resulting operations on edoras one Work Items (other than the Case itself) are performed under the acting user.
Note: up to this release, all activity on a CMMN case was performed under the acting user. This caused problems in situation where the acting user (e.g. a person completing a task) didn’t have access to the Case Work Item.
Frontend project setup improvements
In this sprint we improved the frontend project setup by introducing a way to avoid the need of updating the names of the Webpack generated resources when upgrading to a newer version of edoras one (no more hashed or versioned names are required in the HTML pages). This only applies to customers who need to override the standard HTML pages of edoras one. If this applies to you, please have a look at the upgrade notes for the instructions on how to update your project accordingly. Cache busting is of course still supported.
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.