Version 2.4 (Server) - UBIK Wiki / Augmensys

Minor releases

During startup the system always showed a misleading warning "item does already exit in pool". This problem is fixed now.
The system does not show one particular warning / message more often than once. This reduces the items in the event tracker and makes it more useable.

UBIK^® Studio comes with a new feature called Event Trace. This tool records all UBIK events of the current session and provides the possibility to trace the UBIK execution history. This will help to find problems more easily without grubbing in any log files.
The UBIK^® Studio Bulk Editor now supports pasting from the clipboard into multiple selected cells
New workflow activities for adding data to the UBIK Push Service:

UBIK Injection Management provides a possibilty to extend the standard functionality by adding plugins, controls, activities, etc. to the basic environment.
UBIK Injection Management supports adding of Workflow Activities to UBIK.
Injected libraries can be used in customizing (as well as Whobert, etc.) now.

A concurrency problem in the UBIK WebServices - which could lead to the the wrong update information on an edited object - was fixed.
Using a Reference with an empty Target field, caused UBIK^®Studio to crash when compiling the database. This issue is fixed now.
UBIK WebService does not crash as invalid data was added to the list of infrastructure objects

UBIK^® Proxy management supports import and export of index MetaProxyProperties now. As transfering mutlilanguage properties is supported as well now, the management of multilingual values is much more effective.
UBIK^®supports user groups and rights management in the Application Context Management (ACM) now.
UBIK^® Validation stamps not only the timestamp of the validation but also the login who performed the validation now.
UBIK^® comes with the first prototype of a Push Mechanism.
UBIK^® Workflows supports a new activity which provides the possibility to load Customized System Objects by their Key.
UBIK^® Studio provides a feature to automatically create a new Reference instance and a new Reference - MetaProperty for every new MetaClass (both, Reference and MetaProperty refer to the new MetaClass).
UBIK^® Studio provides a feature to configure user action triggered Workflows. Supported actions are: Drag&Drop and Mouse Click Actions.
UBIK^® Studio delivers an update script for configuration of Custom System Objects via the Database tools folder ([UBIK Installation Path]\Maintenance\Tools\01_ConfigureCustomizedSystemObjects.sql)
UBIK^®Studio provides a feature for automatic name creation (based on rules) now.
New workflow activities for interfacing with OLE-compliant data sources:

ProxyImportScanner compare the correct HashCodes now when evaluating the set of proxies that where modified since the last import.
An accuracy problem when importing / exporting double values by using double properties on proxies was fixed.
UBIK^®Studio ClassBrowser: fixed problems with namespace nodes in the ClassBrowser after the namespace of a UBIK object has been changed.
A Reference and Relation update issue was fixed for Proxy Imports.
A bug in saving and loading of the UBIK® Studio Layout was fixed.
An improved mechanism for creating new objects via ACM avoids the usage of wrong relations.
A bug that allowed stepping through (debugging) a workflow only once was fixed.
When the child object of a relation is deleted, the corresponding relation data object is deleted as well.
A problem when using a Index Property as a Query Item was fixed.
TryImportValue and TryExportValue on the Proxy only updates the timestamp once the value was edited
An inconsistent database could cause the version update mechanism to fail, which leads to an inaccessable UBIK System. This issue is solved now.
Using a Reference with an empty Target field, caused UBIK^®Studio to crash when compiling the database. This issue is fixed now.

It is not possible to implement an interface via the ClassDetailsBrowser Classification View.
Interface manager crashes when reading a not wellformed Interfaces.xml.
Adding a new object in the View Test Environment fails, as the parent node was not expanded before.