Versions Compared

Key

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

...

Warning
titleCritical Update

Our previous operating system CentOS Linux 7 will reach end of life (EOL) on June 30, 2024. Please see the official announcement by Red Hat for more details.

panagenda provides new virtual images based on Alma Linux 9, a RHEL based open source Linux distribution. We encourage all customers to migrate their installations to the new virtual image.

Note
titleCompatibility Warning

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 continue benefiting 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.

...

Table of Contents


New Features

User Licensing Optimization Dashboard

This new feature

    [IFA-1207] - Provide new Insights for 64bit compatibility

profile documents


   [IFA-1193] - Display search result summary after code searchNotes 64-bit Readiness and Nomad Web/Android/iOS Compatibility

The new 64-bit Notes client brings a lot of new opportunities as well as challenges with it. However, as discussed our Webinar on Preparing for the 64-bit Notes Client there is some work to be done in order to be ready for it. One of the key areas to look at will be application code.

We see a similar story developing for the new platforms for Nomad on Web, Android and iOS. They offer tremendous value for next level user experience and portability, but with they also come with a number of LotusScript Restrictions and Compatibility Limitations to consider.

iDNA Applications supports you with a wide array of new Code Insights to help you prepare for these new platforms. After all, ignoring these topics may mean that your applications' functionality and associated business processes might be at risk!

Image Added


Code Search Results Exploration

After performing a code search, a new button will now appear that allows exploring the results in a Metabase dashboard. 

Image Added


This new Metabase dashboard was added to give a more summarized result of a search that is easier to export and requires less interaction when used, for example, to create a task list.

Image Added


Insights Findings Exploration

Similar to the previous new feature, this new Dashboard accessible from iDNAs left-side navigation menu via "Design" → "Insights Findings by Code Element in Database" gives a way to explore the results (or Findings) of Insights. 

It displays the findings in a summarized, tabular structure that makes it easy to filter and export a list of Findings by code element for further processing.

Image Added


Improvements


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 create a delay for results of newly created Insights appearing in the UI. It has Changes have been changed added so that Insights are re-calculated as well if an Insights is Insight was added or modified, or a database has been re-scanned.


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" (navigate to https://<your-idna-host>/idna/sys/etl → ETL Properties).


Bug Fixes


Code/Design Collection: A issue has been fixed that would lead to compiled Formula code not being properly decoded during design collection.

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 to "Settings" → "Design Analysis Status". There, the default filtered results will include all relevant DBs and clicking selecting "Start" will trigger a re-scan. 


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 the creation of 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.

...

Virtually all Docker images/containers have undergone significant updates in outward facing components and underlying libraries. This provides a significant improvement in performance, stability and security.


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

...