UBIK® content objects now has information about the session it has been created in. Once a content object is updated even multiple times, it will still be possible to identify the session it was created in.
UBIK® Studio Debug Form (Who-Bert) now allows to execute code without any customizing binaries loaded into memory.
UBIK® Kernel now has enhanced logging features to provide a separate logging within customizing code and workflows.
UBIK® Kernel now has new Classifications to mark objects/queries being able to be compared via scan codes: SYSCLS OBJECTWITHIDMARKER, SYSCLS IDMARKERSCANQUERY
UBIK®USAM provides an extended authentication mechanism now. This new features delivers more detailed information about the failure in the case of a not successfull authentication. This feature will be used to give feedback after a failed login on the mobile client (future version) and can be used to test a system setup during the project initialization.
UBIK® Queries provide possibilties to add logical search criteria now. With this method it is possible to search for objects by comparing two their property values.
UBIK® Proxy Manager provides extended information in case of a not successfull update (export / import). This will help the admin to find inconsistencies in the data.
UBIK® Proxy management supports scanning for proxies now. Different scanners can be used to find the proxy instances which have to be exported a/o imported.
UBIK® Proxy management supports deletion of objects from and to a 3rd party system.
UBIK® Proxy management "reuses" existing target objects instead of always creating new instances. During an import, it checks as the target (identified by its external primary key) already exists, and refers to it.
MetaProxy objects deliver import a/o export information for ProxyMetaProperties even if the TargetProperty is not defined.
UBIK® Studio Database update performs necessary maintenance tasks (e.g. recompilation of the table structure) automatically now. The user will be guided through the update procedure.
Bugfixes
Metaproperties can have a name ending with '_V' or containing '_L' now. Naming properties like this, does not lead to a lost of data any more.
Category-information (configured on the Metaproperty) does not get overwritten any more. Finally, this fix brings the usage of Categories alive.
As the connection to the session management gets lost in UBIK® Studio, the studio is not closed without further user interaction anymore. Now the user can choose between leaving immediately or the user now can attempt to save the current data before the Studio session is closed.
System.NullReferenceException does not show up in the log files when starting a UBIK WebService Session any more (problem was solved and error does not occure any more).
UBIK® ProxyManager is able to import RelationProxy data now (it is possible to create relations via Proxies).
Database/Systemupdate:. Customized UBIK Code Library data does not get lost during the update any more.
MetaProperties released in the ACM now have the FormatString as defined for the MetaProperty itself or defined in the system default settings if no FormatString is explicitly defined within the ACM context scope.
A problem when creating instances for not yet compiled Metaclasses is fixed now. This solved the problem with creating instances in a derivate of MetaProxyPropertie as well.
Updating MetaProxyMetaproperties forces an update of the database structure of MetaProxies using them. This solves an inconsistency bug when editing MetaProxyProperty.
UBIK® ClassBrowser could have problems after the namespace of an object has been changed by the user (e.g. in the ObjectExplorer). Now only one object node is created and it is ensured that no namespace node is created in the hierarchy view.
Known Issues
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.
Passwords, configured via the interface manager are not saved corretly in the command files.
2.3.1
New features
UBIK® Studio provides a feature to configure the System objects the system will use whenever the user triggers an action. The admin gains the possibility to define which object UBIK must use, whenever the user triggers an action (e.g. creation of a new Metaclass, automatic creation of a Reference, etc.). This feature gives the possibility to separate between objects that where created due to a useraction and objects that where created during a system update.
Bugfixes
For System Settings and System Objects the UID property shows its value and not the UID of the Settinngs object any more. Settings and SystemObjects can be configured via the BulkEditor now.
UBIK® Proxy management "reuses" existing target objects instead of always creating new instances. During an import, it checks as the target (identified by its external primary key) already exists, and refers to it.
Improved Session Management for UBIK Webservices stabilzes them and provides the possibility to "kill" a Service Session now.
UBIK® Database connectivity is able to work with encrypted passwords now. This solves the problem with not working connections as the password was configured via the Interface Management.
Known Issues
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.
2.3.3
New features
UBIK® Studio provides a new feature to configure Workflows that are triggered by certain User Actions. Supported action will be: Drag&Drop and Mouse Click Actions.
If configured, UBIK® Studio automatic creates a new Reference instance and a new Reference - MetaProperty when a new MetaClass is created (both, Reference and MetaProperty refer to the new MetaClass).
UBIK® Studio provides a new feature for automatic name creation out of rules.
Bugfixes
An improved mechanism for creating new objects via ACM avoids the usage of wrong relations
A Reference and Relation update issue was fixed for Proxy Imports.
TryImportValue and TryExportValue on the Proxy only updates the timestamp once the value was edited
Known Issues
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.
A bug in saving and loading of the UBIK® Studio Layout was fixed.
A Reference and Relation update issue was fixed for Proxy Imports.
