panagenda is proud to announce this new release of iDNA Applications. Whether you’re modernizing or migrating Notes/Domino, iDNA gives you the knowledge to deliver the most difficult projects efficiently, on time and on budget. This new major version brings a ton of value with many new features, improvements and bug fixes.
Highlights
Content Analysis
The solution is now capable of scanning individual documents in a database. Document metadata (e.g. date created, last modifier, form name) is analyzed and displayed for a variety of use cases. This scan does not extend to evaluating user entered content like e.g. names, addresses or social security numbers. Topics analyzed include:
- Document structure and used Forms
- Attachments
- Encryption and signature
- Reader and author fields
- Content editors
- Special objects in Richtext
more benefit oriented?
new license system?
Instant Usage History
We have added a new source of usage history by reading a DBs own activity records (DB Properties > Info > Activity > User Detail). The data collected that way will seamlessly integrate with session data, which will remain the main data source for usage related information. The main benefit with this feature is that basic usage information spanning weeks or months of history will be available a few days after the setup of iDNA Applications.
This data source has several caveats though. Collection might not be enabled for all databases. Only a few hours of history might be available on very busy databases, while months of history is available for others which are rarely used. Data quality in general is not on par with session information from log.nsf, which is the main data source for usage information.
To gather this data, a design re-scan has to be performed on each database. This can be triggered manually from the "Settings" menu on the "Design Analysis Status" page.
Custom Application Properties
We have added a new source of usage history by reading a DBs own activity records (DB Properties > Info > Activity > User Detail). The data collected that way will seamlessly integrate with session data, which will remain the main data source for usage related information. The main b
New Features
Metabase: it is now possible to create nested folders in the navigation menu by creating sub-collections in Metabase
* As a user of IFA, I'd like to identify databases that are encrypted on the Domino server
* New Language: French
* As a user I would like to have information on database ACLs
* As a user, I would like to see a list of all my agents and their (most important) properties
* As an admin, I would expect DBs to vanish from the catalog if I decomission a server
* As an admin, I would like to be able to disable DBs being categorized as UserMail or Orphans
* Integration of a beautified teamWorkr view
Improvements
UI Refresh: Navigation Bar Style has been improved
Data Processing: more details needed on nightly automatic refresh
* Make it harder to stumble over the INIT/REFRESH buttons in sys/etl
* Update Metabase to latest v0.35.x
* As an admin, I would like to be able to remove user history for users I have marked to be excluded wihtout going to pgAdmin or doing an INIT
* As an admin, I would like to be able to reset org data without having to go to pgAdmin
* As a user, I would like to export all DB instances that belong to a design similariy cluster
* As a user, I would like to see similarity cluster info in the DB Instance grid
* As a user, I would like to see info about creation and last modified for DB Instances and Replica Sets
Bug Fixes
* Server status displays OK if no session data can be collected
* Investigate missing Nomad columns
* Health Job does not validate ETLLoaderJob status
* Investigate name "iDNA for Applications"
* Server Grid: ETL last modified timestamp seems to be missing
* Namevar conflict: Two users with the same name in different node types
* Updating views ETL statement sometimes leads to postgres being killed
* UI Issues around XPages
* Inconsistent handling of DB Types in Catalog grids
* Show all DBS in catalog does not show user mail files and orphans
* Handling of "no DB title" different in catalog and repset grid
* License Expiration Notification Mail cannot substitute Vendor and ProductName placeholders
* Hover over details on usage pattern similarities bubbles shows "undefined"
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.
Reminder: license structure pohne home
Visit our site to start your evaluation right now!