edoras one - Release Notes

Version 1.5.0.S54


Hello everyone

CLD 1.5.0.S54 of edoras one is now available:
https://confluence.edorasware.com/display/BPM/CLD+1.5.0.S54

In this sprint release, we have made many UI improvements that enhance the usability and the appearance of edoras one. For example, lists views now remember their scrolling position when you navigate back to them in the history.

We have fine-tuned the form palette some more. All form components that allow to configure a target link now also allow to set where to open the target link. On the calendar component, the number of years the user can choose from is now configurable.

Additional security checks ave been put in place to ensure that access is only granted to those parts of the UI for which the current user has been given permission.

Our support for keyboard shortcuts has been made more solid.

All default edoras one REST end-points now deliver their items in a predictable, sorted manner, e.g. the User REST end-point, the Group REST end-point, and so on.

The search functionality of edoras one has been extended to give better search support.

Support for BPMN 2.0 multi-instance sub-processes and multi-instance call-activities has been added. Also, all of the modeling of process events in edoras vis is now supported at runtime, too.

On a user task modeled in edoras vis, the modeler can specify what task actions are available at runtime in the UI, similar to what was already possible for ad-hoc tasks.

A first step towards a better modularization of the edoras one project has been taken, and affects primarily the server-side of edoras one. More steps that also involve the front-end side of edoras one will be taken in the upcoming sprint releases.

The edoras vis configuration as needed by edoras one for a given sprint release is now part of the edoras one bundle artifact and available in our repository.

All of the edoras one and edoras gear codebase has been migrated to Java 7. Java 6 is no longer supported as of this sprint release.

Regards, edoras one team

High-level Goals

  • Allow to configure the number of years to choose from on the Calendar component
  • Navigation must remember scroll position for list views
  • Make shortcut mechanism more solid
  • Prevent unauthorized view access
  • User experience improvements
  • Support multi-instance sub-processes and multi-instance call activities
  • Ensure the edoras vis process palette is configured properly for all elements supported at runtime
  • Write empty fields used as placeholders in documents and emails as empty string
  • Sort the items in Auto-Complete Selection REST endpoints
  • Enhance search capabilities
  • Initial improvements of the edoras one modularization
  • Add the edoras vis configuration to the edoras one bundle artifact available in Artifactory

Migration Notes

  • Upgraded edoras one and edoras gear to Java 7
  • edoras forms is not available as a standalone project anymore

Limitations

  • None