Dear customer

In this release we introduce a lot of new enhancements related to the persistence of edoras one. We also implemented a lot of new features which are described in the next paragraphs. Besides that we also fixed major bugs and we are constantly improving the client experience. As you maybe already noticed that we also polished the release notes emails and the upgrade notes to deliver you the best experience to see what is new and how to easily upgrade to the latest version of edoras one.

Best regards,

the edorasware team

New release notes

In this release we upgraded the way we create and style our release and upgrade notes. The new release notes are now created with the help of AsciiDoctor and therefore we are easily able to provide you nice looking and informative release and upgrade notes.

We split up the release and upgrade notes into two separate pages such that you will receive the release notes as email and you are able to read the upgrade notes online. There you will find all information needed to upgrade to this version of edoras one.

If you have issues with the styling of the release notes in your email client then you can always have a look at the online version of it here.

Oracle 12c support

As of now we are fully supporting Oracle 12c. We added the support for this version as Oracle 11g reached its end of life this year. We tested the release with the Oracle version 12.1.0.2.0. We are still supporting the old Oracle 11g version till all customers migrated to version 12.

Automatic database upgrades

200

We are finally able to announce that we now support automatic database upgrades such that you do not need to execute the database upgrade scripts by hand anymore. We used Flyway to provide the automatic database migrations and adapted it to our needs. After migrating to this release mostly all future upgrades are executed automatically without the need of manual steps. Please have a detailed look at the upgrade notes on how to setup the automatic database upgrades.

Unicode support for all databases

We also added support for unicode characters for all our supported databases. If you need unicode support you will need to check out the where all the database scripts are provided to convert the current fields to unicode compatible ones.

edoras vis persistence

We no longer store edoras vis model data in specific database tables. Instead, we store the model data as variables of the related model items such that we use the same persistence as we use in edoras one, which is edoras gear. This eliminates duplication of data and data synchronization between vis and gear tables. We have also optimized the loading of model information while comparing model revisions so that only relevant revisions' data are loaded as required.

Please have a look at the upgrade notes on how to migrate to the new data persistence of edoras vis.

Miscellaneous

edoras vis

Ability to skip BPMN 2.0 schema validation when importing process XMLs

It has been observed that the BPMN 2.0 process XMLs exported out of other modeling tools are not always 100% BPMN 2.0 schema compliant which resulted in not being able to import such process XMLs in edoras one. We have now added an option to the import process action form to optionally disable BPMN 2.0 schema validation while importing the process XMLs. This enables importing of processes from XMLs which are near BPMN 2.0 schema compliant by ignoring minor syntax errors which might cause schema validation failures.

CMMN

CMMN now supports a new type of case file item that watches Case variables

By using the new case file item definition type "edoras case variable", case file items can now be modeled which refer to a variable of the case work item. As the variable changes, corresponding create/update/delete events are triggered on the case file item.

Id-lookup in the CMMN case provider was modified to support external case ids

A bug was fixed in the CmmnCaseProvider to honor external ids. The fix is only relevant for CMMN customers managing their own external case ids.

Actions from closed CMMN stages are now properly hidden

The visualization of case actions for stages was improved/fixed. Enabled plan items within completed or terminated stages are now properly hidden.

CMMN XML class-lookup has been changed to be more robust in complex war/ear deployment scenarios

This low-level improvement relates to the way CMMN XML classes are loaded. The new lookup is more robust with respect to deployment configurations and application server environments.

Upgrade notes

Please have a detailed look at the upgrade notes for this version such that you are able to easily upgrade to the newer version.

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.