UBIK gives the possibility to login as a team now. A team is as set of logins (containing 1 to n members) and is managed via the UBIK sesssion information.
The -IGNOREUSAM parameter is remembered when restarting UBIK.Studio (e.g. after compiling the customizing). (Build 42++)
Bugfixes
A problem in managing Geo Properties with empty values was fixed.
A bug when changing the filetype (from *.jpg to *.jpeg and vice versa) during the upload of a "changed" document via the Web Service is fixed now.
Uploading a changed document (e.g. *.jpg) to the server (using the Web Service) updates the thumbnail image of the document object now.
Problems with own hosted Properties on Query Scopes are fixed: It is possible to Define the sort and group id from queries as well now.
A Problem when compiling the customizing after changing the UBIK Project is fixed now. (Build 42++)
A Problem when updating from Database Version 2.5.0 is fixed now. (Build 42++)
Updating to Database Version 2.6.0 removes unsupported Meta Structures (such as discontinued feature "ACM Userrights") now. (Build 42++)
Huge Bytestreams were not displayed in the bulk editor. This is fixed now. (Build 42++)
A bug in the evaluation of user rights for created/updated objects is fixed now. (Build 42++)
Metaclass can not be named "SYSTEM" any more
A bug in the update scripts for the MRO Module was fixed.
Enhancements
There is a new UBIK <-> MS Project interface (plugin) available since UBIK Version 2.6.0.
The memory management for View Cache has improved widely reducing the memory consumption when building up the View Cache by far.
New preloading mechanism (for the view) improve the initial View Cache setup time by up to 500%!
A refactoring in the UBIK Interface module reduced the need to add customized code and workflows by far.
UBIK supports different filetypes for Office documents now (Microsoft Excel, Microsoft Excel (97 - 2003), Microsoft Word, Microsoft Word (97 - 2003), Microsoft Powerpoint, Microsoft Powerpoint (97 - 2003))
There is a new PlugIn available that simplifies the interaction between UBIK Reports and SQL Server Reporting Services (SSRS)
2.6.2
New features
A set of new Classificationsis are provided for configuring AR Markers:
UBIK provides the possibility to configure a Query used on the client (scanning for targets) when editing a Guid Property (See Configure the ACM).
Introduced Scope Inheritance makes the reuse of scopes possible and will reduce the effort of ACM Customizing by far.
Extended customizablities on the Query Scopes increases flexibility in data design (CustomGetFilterClassMetaProperty, TakePropertyValueFromQueryInstance).
UBIK provides database maintenance operations remove deleted records from the table structure and to rebuild table indices now.
UBIK supports the PropertyType Chart now.
It is possible to load objects by its UID in UBIK.Studio now by using the Object Explorer.
UBIK extends the number of available permissions on Scope-Metaproperty Relations.
UBIK Push supports a new popup object classificatoin now:
Problems when displaying (large) icons in the bulk editor are fixed now.
A relational object can now search in the whole inheritance hierarchy to find a relational property.
A problem when updating the database version and using Windows Authentication on a DB System is fixed now.
UBIK.EnterpriseService is not able to process the very same command file twice in a row without interruption.
A bug in the update scripts for the MRO Module was fixed.
Enhancements
After reopening a connection to a database, UBIK.Studio refreshes all its controls and sub pages. It is not possible to work with an outdated environment any more.
UBIK Debugging and testenvironment saves the customized code automatically. You can find the file in the local project folder (TEMP).
UBIK provides extended mechanism to provide detailled information about the client OS when authenticating at USAM.
An improved client management mechanism ensures that unsupported data and data types are not sent to clients. This saves resources and improves the stability of UBIK Clients.
It is possible to define the max number of items being delivered by a query when evaluating it in a View. The configuration is done on the QueryViewItem.
