Error rendering macro 'rw-search'

null

Downloads

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Questions along this line of thinking are extremely valuable when it comes to identifying application owners and stakeholders.

New Features

DB Type Re-categorization: It is now possible to prioritize DB re-categorization rules higher, by adding a * at the beginning of their name. This works on four levels, with three leading asterisks as the highest priority and the current non-astersik format as the least prioritized.

For example: the rule named "***Highest Priority" will be prioritized over "**Higher Priority", which again is prioritized over "*High Priority". All of these are prioritized over the rule named "Normal Priority".



Improvements

DB Type Re-categorization: It is now possible to prioritize DB re-categorization rules higher, by adding a * at the beginning of their name. This works on four levels, with three leading asterisks as the highest priority and the current non-astersik format as the least prioritized.

...

Content Analysis: Attachment file extensions were previously treated case sensitive (file1.pdf vs FILE2.PDF). While a case can be made that this technically that makes sense, the overwhelming feedback of our customers and partners has been to rather treat it case in-sensitive. For example: if a document has two attachments FILE1file1.PDF pdf and File2FILE2.PdfPDF, they will both be processed a single attachment extension category "pdf", rather than two separate ones.

Domino Binaries: iDNA now uses HCL Domino 11 FP3 components to perform design exports. Due to fixes in HCL has done great work on the DXL exporter code, that should result in so the result of this update should be significantly less databases with design scan errors.

Metabase Upgrade: The integrated Metabase application has been upgraded to the latest version. Improvements include better filtering, easier and more powerful dashboard and chart creation abilities.



Bug Fixes

General UI: A potential issue with caching has been fixed. This bug could lead to outdated data being displayed in the user interface.

Catalog Grids: An issue has been resolved that lead to several dates (e.g. Last Access, Last Write) in catalog grids to be displayed incorrectly due to double time zone conversion being erroneously performed twice.

Catalog Grids: A bug has been resolved that lead to the header text of the first column header ("Title") of an Excel export being empty. The data for column "Title" itself was present, but in the header text was empty.

DB Type Categorization: Deleted databases will now be excluded from calculations while when trying to determine the correct DB Type for a replica set. In rare situations this could lead to incorrect categorization.

Agent List Processing: A potential issue has been fixed where nightly processing of agent data could crash in case of invalid date content.

Docker Containers: The panagenda_idna container now properly displays its health status and does not report "unhealthy" anymore unless there is a real issue.

Views Processing: Views are now handled and categorized properly. Several factors lead to potential issue in the categorization of Views and Folders during processing Design data.

Department/Location Processing: An potential issue has been fixed that occurred in rare situations when a certain combination of characters was part of a department or location that are used as special characters in PostgreSQL.

Department/Location Display: In database details under the tab "Usage", the correct time frame of 90 days for the data shown is now being displayed to avoid confusion.

[IFA-1111] - DBUsage Summary by Repset fails with Array Size Exceeded

[IFA-1093] - Upgrade Metabase to latest version

[IFA-1108] - Rework merging of Catalog Views with DDA Views

Nightly Data Processing: A rare issue has been fixed that would lead to an error during nightly processing



Structural Changes / Upgrade Path


Data Warehouse Rebuild Required

Note
titleDWH Rebuild Required

After installing the update, parts of the application may not be available until the data warehouse is rebuilt. This process runs automatically at night, but can be triggered manually after the update. On the first login after the installation, more information on this topic will be displayed, along with the option to trigger the rebuild.


Upgrade Procedure: Container Installer

Details on how to update to this new version can be found in the knowledge base article Upgrading iDNA Applications.





Visit our site to start your evaluation right now!