Managing Java reporting excess data from ARL update

Prior to November 2025, reporting for commercial installations of Java, using the Application Transparency Report (as recommended by Flexera), had been working well.

This is described in this best practices video: https://youtu.be/jMD_AijaBXw?si=pwQ3sMOJ3xt0Esoh&t=1872.

The ARL/SKU/PURL update of November 16, 2025 added a precedence rule that effectively inserts installer evidence into the Java platform application that previously were only using file evidence. Announcement here: https://community.flexera.com/s/feed/0D5PL00000glvjd0AA

Since this change, the number of rows returned when reporting on Java using the Application Transparency Report has basically doubled. Typically, for every installation of Java detected using file evidence, there is now a second line that is derived from the installer evidence via the suite recognition.

To eliminate this extra data from the Java reports you can run the report as you previously did, however once the report is displayed, add a filter to the Suite member application column and set the filter to Is blank. The report will now perform as it did, prior to the November 2025 change.

Note that Java recognition is based on file evidence, as this is the only reliable way to retrieve the accurate application build information needed to correctly identify the version of installed Java; and therefore to determine if the installation is commercial (requiring a license).