Dear customer
In this release we introduce virtual time support and therefore edoras one does not rely on the system time directly, but the time information is provided by
the TimeProvider
implementation.
Another big step of the view engine integration has been accomplished in this sprint by extending the view engine to the create action
. In addition to this improvement and
thanks to the extensibility of the new view engine, we have added a mechanism to introduce custom widgets
by extending the configuration of the view engine. This feature is at
the moment a sneak-peak for developers which will be completed in future sprints with some documentation on how to create custom components and make them available in the VIS
editor.
Also, thanks to the feedback from the early adopters of the S98 release, in this release you will find some improvements in the content management API, most of them related to the content listeners. The basic methods of the content management API remain unchanged, so the migration to this version should be straightforward.
For the detailed information see the following chapters.
Best regards,
the edorasware team
Virtual time support
Virtual time support means that edoras-one does not access system time directly. The time information is provided by TimeProvider
implementation. The default
implementation of the time provider is based on the system time. In the case when you want to rely on any other time provider, which can move time forward or backward, make time
flow faster or slower, just implement your own time provider and configure the bean according to documentation. The consequence is that your custom code has to rely on the time
provider time too.
New view engine in create action
Until now, the new view engine was only used in the browse view
. As of 1.5.0.S100, the new view engine is also available in the create action
.
This is a big step towards the replacement of the previous engine and its deprecation. As of now, the view engine is still experimental and as a backup measure, the
integration in the create action
can be controlled through a property in one.properties
(please, have a look at the upgrade notes).
View engine custom widgets
Thanks to a new API available on the config phase
of edoras one, a developer can now hook its own configuration callback function to extend the functionality of the view engine.
This configuration callback will be called with the configuration of the view engine and is expected to return a new valid view engine configuration or the same one extended with
new components, decorators or validations. Please, see the example below and for some more documentation on the view engine, have a look at the {https://documentation
.edorasware.com/view-engine/documentation}[view engine documentation]. More comprehensive documentation will be provided in next sprints.
/* file: custom.js */
one.viewEngine.config(myConfigCallback);
function myConfigCallback(viewEngineConfig) {
var myComponent = {
template: '<div>My component</div>'
};
viewEngineConfig.components['my-component'] = myComponent;
return viewEngineConfig;
}
Content management API improvements
This release introduces several improvements in the content management API. Most of them are focused in making the implementation of content listener more friendly.
The most important change is the place (the layer) where the content listeners are called. In the previous versions, the content listeners were called at the content provider level. Since this release, the content listeners are called at the content manager level, that is, one level up. The configuration of the content listeners is done at the content manager as well. A new method has been added to enable the configuration of all the listeners in the Spring XML files.
The signature of the content listener methods now includes a single ContentEvent
parameter. The ContentEvent
type includes all the information that the content listener may
need, including a reference to the content manager that triggered the event.
The deleteContent()
now is declared in the ConfigurableContentManager
interface. This method is basically a call to delete all the content of all the content providers
configured in the content manager. As this method is only intended for maintenance support, it has been moved from the standard ContentManager
interface to the more specific
ConfigurableContentManager
interface.
Please, check the upgrade notes to review the detailed description of the changes and some hints to migrate your code.
edoras one CMMN Improvements
This release introduces the following fixes and improvements:
-
A number of plan item properties are now available for evaluation in CMMN back-end expressions. State information like
state
,lastTransition
,name
,id
or the number of active plan item instances can now be evaluated in CMMN expressions (e.g. in sentry conditions). This includes properties like the current state of the Required, Repetition or Manual activation rules. Check out the new sectionCMMN Expressions
in the CMMN documentation. -
As a result of the above feature, it is now possible to limit the number of repeatable plan items or stages. In addition, the new feature also helps to improve the visualization of milestones and stages (e.g. to hide a pending non-required milestone until it has been reached).
-
The property
Completion neutral
is now available for all plan item types. This improves modeling flexibility for stage completion. -
Expressions are now supported for the names of output variables (e.g. the name of the result variable of a Service task).
-
Various connector line layout improvements have been implemented in the CMMN VIS modeler.
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.