News

07.12.2017 ver. 3.2.0.0-SNAPSHOT

1) Templates now are loaded from the repository alfresco at the first request. Furthermore, the main data source for a template is its content (cm: content). This has lead to the following changes:

  • Fixed a bug where a template stops working after system reboot if there is no exported xml file xml in classpath’e;
  • When updating template on a cluster system there is no longer need to renew templates in two nodes;
  • Fixed a bug whereby changing type/kind in a template journal did not operate until templates are exported/imported. At present type modification leads to a content modification;
  • A bug is fixed in which the new version uploading on the template card had utterly no effect. Now types/kinds and data are being updated and applied to the new cases;
  • Fixed a bug where downloading a template through logs came out as an almost empty xml file. In the updated version you download the actual content.

You should pay more attention to templates duplicates. In the current version a first eligible template is assumed.

2) The template implementation and launch of the case process are divided into different transactions. This will slightly accelerate launching process and will not roll back the successfully implemented template if there are some problems at start-up.

29.09.2017 ver. 3.2.0.0-SNAPSHOT

1) An “Automatic events management” flag was added. If it is active, startup and completion events are automatically generated. If an activity is the first one, a parent is being checked. If it is a case, an event will be a “Case created”. If it is a stage, a “Step launched“ event will constitute a starting event. If the activity is not the first one, a “Prior activity completion” event will serve as a starting event.

2) Logic has been changed related to the new steps of the “Latest active subtask was completed” event. At the moment, this event additionally emerges when the step is launched but no activity started.

A new step is an updated step. If a step is created based on the template and there no “activ:typeVersion” field, such a step is considered as an old one.

3) The reboot event was considered outdated and has been removed from steps/tasks/actions forms. Instead of it the starting event + the “Replicable” checkbox should be used. In those activities where such actions have been created, the field remains visible and vanishes after deleting of actions.

Fixed a bug with an erroneous activity list in the events when a task/stage/action has not been formed.

25.09.2017 ver. 3.2.0.0-SNAPSHOT

A Case Management functional has been moved from ecos-enterprise to idocs-repo.

19.09.2017 ver. 3.1.4.0-SNAPSHOT

1) Every template is associated with a certain template node in the memory. Consequently, modification of condition'а solely in this node will turn on/off a template. Binding takes place during system boot. If a node is deleted, “Template nodeRef doesn't exists" errors will occur in logs and template will not be implemented (even if there are template duplicates, see paragraph 3).


2) While comparing templates the “condition” field is being ignored. That is to say two templates with the same type, kind, and alfresco type are considered as the same template.


3) If several identical templates are found when the system is being booted (they are compared on the 3 lines, Paragraph 2), then the first one that is included (with an empty condition or with the “true” condition) will be active.  All other patterns are recognized as duplicates and the comment "/ * IGNORED DUPLICATE * /" will be added to their condition. Templates with such a comment can be deleted without harm on the working system.
4) When selecting a template upon the alfresco type, the hierarchy of types is now taken into account. That is, the template for sys: base will be applied to all cases in the system for which a more suitable template could not be found (upon type / kind or closer by type hierarchy).


5) The Case Type field now can contain not only an alfresco type, but an aspect as well.