panagenda is proud to announce this new release of iDNA Applications. Whether you’re in a Notes/Domino modernization or migration project, iDNA gives you the knowledge to deliver the most difficult projects efficiently, on time and on budget. This new version is mainly a maintenance release, but brings a lot of value with new features, improvements and bug fixes.
Highlights
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-asterisk 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".
Department/Location Import: An advanced feature has been added that allows you to programmatically manipulate collected department and location data during automatic processing. To use this new hook function, please contact support@panagenda.com.
Department/Location Processing: This new version now makes a clearer distinction as to which users get the department/location "Company [ID: 1]" and "Unknown [ID: -1]". The designation "ID: 1" applies to all users that cannot be linked to a specific department, but have person records in the Domino Directory and can thus be linked directly to the top-level organization. The designation "ID: -1" is the unknown department/location for users where activity is present, but they cannot be linked to the current organization structure via the Domino Directory. A typical example of who would fall under the designation "ID: -1" would be those users that are no longer with the company. Thus it is easier to distinguish between the "current users" and the "users who were active in the past".
Content Analysis: Attachment file extensions were previously treated case sensitive (file1.pdf vs FILE2.PDF). While the case could be made that this technically makes sense, the overwhelming feedback from our customers and partners has been to instead treat it case insensitive. For example: if a document has two attachments file1.pdf and FILE2.PDF, they will both be processed as 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. HCL has done great work on the DXL exporter code, so the result of this update should result in significantly fewer 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 dashboards 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 led to several dates (e.g. Last Access, Last Write) in catalog grids being displayed incorrectly due to time zone conversion being erroneously performed twice.
Structural Changes / Upgrade Path
Data Warehouse Rebuild Required
DWH 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!