Page History
...
This new dashboard compares five common KPIs between the database instances of a the same replica set in order to identify discrepancies between the databases. The KPIs points point out common replication issues issues by analyzing data on document count, design age and template inheritance.
...
A long requested feature by enterprise customers was is LDAP integration. You now have the ability to integrate with your directory infrastructure and use enterprise credentials to log into iDNA Applications.
...
Notes Client Information: if connected to a MarvelClient Analyze database, information on users and Notes clients can now be analyzed in DataMiner and Metabase.
Design Re-scan Configuration:
| Note | ||
|---|---|---|
| ||
The interval of design collection upon design change has been reset to the new default and recommended setting "Weekly, on Saturday (Recommended)" The previous default configuration of "Next day" may cause a continuous design re-scan of a large amount of databases if certain design refresh settings in Domino are enabled. This continuous re-scan may have negative impact on performance while creating little to no benefits. Changing this value setting in a compulsory way was a highly exceptional action and not done lightly. Of course, it can be freely (re-)configured using the page [Settings] → [Database design re-scan options]. |
Improvements
Consolidation Potential: the calculation for this category has been updated and streamlined throughout iDNA. The new calculation works as follows: no or very low usage in recorded history and no usage in the last 90 days across all DB instances.
Data Collection: several improvements were made around detecting issues with data collection (e.g. expired Notes ID password) earlier. A weekly warning email has been added and it's now easier to recover from a collection outage.
[IFA-491] - Database recategorization rule page interface enhancements
[IFA-649] - Upgrade Metabase Database Types: the interface for database re-categorization has received a number of improvements. It can be accessed via [Settings] → [Database Recategorization Rules].
Metabase: the application has been upgraded to version 0.34.1
[IFA-659] - Review decision making on database size
[IFA-668] - Clean-up in "Servers" Grid
[IFA-669] - As an admin I would like to receive weekly emails regarding collection status
[IFA-496] - When I click the 'show unused replica sets' below the Consolidation box on the Start Page it only shows me the Unused which is a lower number than the Consolidation box shows me
Bug Fixes
[IFA-497] - Typo on 'User Activity Lookup' metabase dashboard
[IFA-499] - user_agent column in idna_domino.domlog table may be too small for certain agents
[IFA-517] - Customer Metabase user cannot ask questions or drill down
[IFA-578] - Usage Overview - Focus Inventory History
[IFA-620] - Investigate user double count on anonymized license
[IFA-623] - Investigate issue with user renaming and name variations
[IFA-643] - Incorrect Last Modified Date in DB Details
[IFA-648] - Duplicated Files appearing in Catalog. Please see the release notes for more details.
Server Catalog: this grid has undergone a re-design to help with identifying collection issues. What used to be the "Details" column set has been enhanced and is now the "Default" column set and vice versa.
Bug Fixes
DB Details: a bug has been resolved that would lead to a wrong "last modified" date to be displayed in Database Details
Domlog Collection: an issue has been resolved where too much text the "user_agent" column could cause and issue when storing data to the database
Duplicate DBs: a bug has been fixed that could, in rare situations, lead to databases being displayed twice in Catalog
Metabase: a misconfiguration has been resolved that lead to the default user accounts being unable to ask custom questions
Metabase: several typos have been corrected in dashboards in the Usage category
User Activity: a bug has been fixed that lead to counting certain users twice if user anonymization/pseudonymization was enabled
User Rename: an issue has been fixed around handling user renames. Upon rename, the new name will now be properly reflected in iDNA Applications
Structural Changes / Upgrade Path
...