Release Notes

Unidata Enterprise Edition

6.6 Version

Unidata Standart Edition

6.7 Version

  • A new edition of the product: SE (Standard Edition) was created. The edition includes the basic features of working with data. Compared to EE (Enterprise Edition), SE has a number of limitations and lacks some advanced tools. Limitations are set when creating a license.

  • For Standart and Enterprise editions, the ability to create hierarchical lookup entities was added to display records as a hierarchical tree.

  • In the audit log, alphabetical sorting of filter values and the possibility of multiple selection of values were added, as well as the ability to export the entire log or just the current page.

  • A tabular view mode has been implemented for the array-attribute, where cells are filled with multi-line values.

  • In the “Roles” section, some system rights resources were updated.

  • The searching of pipelines segments by hierarchy was implemented.

  • When editing quality rule sets in advanced mode, the ability to change the sequence of rules was added.

  • In the “Data Model” section, the ” Validity Period Boundaries” parameter has been added to the entity/lookup entity properties.

Unidata Community Edition

6.6 Version

  • A personal user account with the ability to edit account settings and change the password is implemented.

  • Display of relations of the “Reference” type in the form of timelines is implemented in the record card.

  • The data model version comparison screen is implemented.

  • An option to save common search queries which will be available to all users of the system has been added.

  • It is now possible to compare records directly from the “Data” section.

Known Problems

Error when publishing a record related to large number of duplicates

The problem occurs in situations where the record being created falls under duplicate search conditions and at the same time when the record being offered for publication is added to the duplicate cluster, ElasticSearch’s search index receives more than 1024 conditions. The problem can also occur when searching through duplicate clusters, workflows, etc.

The problem will be fixed in future releases by optimizing the query to ElasticSearch.

Temporary solution:

Either optimize the matching rules by making them more specific. This will decrease search fetching.

Or to increase the parameter responsible for the number of conditions processed by the search index. In the file elasticsearch.yml edit the parameter indices.query.bool.max_clause_count (default value 1024).