edoras one - Release Notes

Version 1.5.0.S70.1


Hello everyone

CLD 1.5.0.S70.1 of edoras one is now available:
https://confluence.edorasware.com/display/EDWDEV/CLD+1.5.0.S70.1

One of the goals of hot fix 1.5.0.S70.1 release is to upgrade activiti BPM platform from 5.16 to 5.16.3. Activiti BPM platform 5.16.1,2,3 releases fixed bugs mostly. On the other hand default job executor implementation changed. It can affect repeating timers invocation. There is no guarantee for timer to be executed exactly on the time when it was scheduled. Upgrade to the activiti version 5.16.3 needs to execute DB upgrade script (edoras-gear-core-3.0.2.S67-B9.jar:/com/edorasware/gear/core/db/update/activiti.${DB_TYPE}.update.engine.S65.to.S67.sql).

This hot fix release improves support for making APP parent of cases introduced in 1.5.0.S70. Java API call to workObject.getRootId() returns the first work object in the path. The path hierarchy has changed for UserDashboard work objects (Case, Process, Task, Document) and root work object is since S70 application. Backward compatibility in java API calls is supported through com.edorasware.commons.core.entity.WorkObjectUtils.getTopMostParentIdOrSelf(CaseId.class, workObject) method call. There is no need to migrate long running process instances because expressions still returns case as root user dashboard work object.

Regards, edoras one team

High-level Goals

  • Upgrade activiti BPM platform from 5.16 to 5.16.3
  • Improve support for making APP parent of cases

Migration Notes

  • Java API call to workObject.getRootId() returns the first work object in the path. The path hierarchy has changed for UserDashboard work objects (Case, Process, Task, Document) and root work object is application since 1.5.0.S70. Backward compatibility is supported through com.edorasware.commons.core.entity.WorkObjectUtils.getTopMostParentIdOrSelf(CaseId.class, workObject) method call. There is no need to migrate long running process instances because expressions still return case as root user dashboard work object.
  • Activiti BPM platform 5.16.1,2,3 releases were mostly bug fix releases. The default job executor implementation changed. It can affect repeating timers invocation. There is no guarantee for timer to be executed exactly on the time when it was scheduled. Upgrade to the activiti version 5.16.3 needs to execute DB upgrade script (edoras-gear-core-3.0.2.S67-B9.jar:/com/edorasware/gear/core/db/update/activiti.${DB_TYPE}.update.engine.S65.to.S67.sql).

Limitations

  • None