Page History
...
| Note | ||
|---|---|---|
| ||
From version 3.0.0 onward, iDNA Applications upgrade packages will not be backwards compatible with the previous CentOS-based appliance. Please deploy a new v3 Alma Linux appliance to benefit from iDNA's latest and greatest features! To migrate For a how-to on migrating your existing system and data please visit our iDNA Version 2 to Version 3 Migration Guide. |
...
Code Insights: Insights were previously only re-calculated if at least one database design was re-scanned since the last nightly processing. This could result in a delay of newly created Insights appearing in the UI. It has been changed so that Insights are re-calculated as well if an Insights is Insight was added or modified.
DLAU Integration: Recent updates in DLAU have been incorporated.
Usage Cluster Calculation: the The default parameters for the processing of usage clusters has have been changed due to a significant impact on the duration of the nightly processing task in large environments. The previous setting that essentially said "calculate for the entire recorded history" has been changed to "calculate for the last 90 days". This setting can be modified by setting the ETL parameter "ai_usage_cluster_last_activity_max_days".
...
| Note |
|---|
Design will have to be re-collected for each database that contains Formula code and may be affected by this issues. Even though our observations internally and at customers point to this being a comparatively rare occurrence, we recommend re-collecting the entire application landscape to make sure no potentially relevant code blocks are being ignored. A re-scan can be started by going |
Design Re-scan: An issue has been resolved that would lead to an internal error if more than 999 DBs were submitted for design re-scan in "Settings" → "Design Analysis Status". There was no UI message indicating an issue, even though the underlying action would fail.
DLAU Collection: Collection from the DLAU database may fail due to a previous inconsistency in IFA's internal database structure. We If you are currently facing issue with collecting from the DLAU database, we recommend removing the current content package configuration, saving the settings and re-creating it afterwards in a second step.
Insights Code Highlighting: Minor inconsistencies with code highlighting have been fixed and code highlighting overall has been improved.
Insights Processing: An issue has been resolved that would lead to some custom insights processing failing in rare cases. Overall processing for insights has been improved and it now allows for creating more complex regular expression patterns.
Person Document Data: An inconsistency has been removed where advanced details in person documents would not be available due to an error in syncing nightly processed data with latest collected data.
...