Loading

Applications and Evidence

Skip Feed
  1. IT Visibility: Full Transparency into File Evidence UI

     

    Software Evidence UI has been enhanced to display all file evidence collected from your environment, giving you a complete view of your discovery data. 

    What's New? 

    File evidence is now grouped into three categories: 

    • Active (Technopedia Mapped): Recognized and mapped to a known software product. 
    • Unrecognized: Collected but not currently mapped to Technopedia. 
    • Irrelevant: Excluded from recognition of workflows.  
    • A supporting Irrelevant Reason column is now available in both the UI and CSV exports. 

    These categories are visible in Devices (Inventory > IT Visibility Devices > Devices > File Evidence tab) and Software Evidence (Applications & Evidence > IT Visibility Software > Software Evidence > File Evidence tab) 

     

    How the UI Works 

    • File evidence is pre-filtered to Active by default. Unrecognized or Irrelevant evidence can be selected as required. 
    • Summary counts at the top of the page reflect only Active (Technopedia Mapped) file evidence, so your existing recognition metrics remain unchanged. See more details below in Understanding File Evidence Recognition

     

    Understanding File Evidence Recognition 

    File evidence is a supplementary data source in IT Visibility, useful for validating executables, troubleshooting, and supporting investigative workflows. It is not the primary path for software recognition, which is driven by installer-based evidence and Technopedia normalization. As a result, a large volume of unmapped file evidence is expected and does not indicate a recognition issue. The new categorization simply provides greater visibility into your raw file evidence data. 

     

    Learn More 

    For a detailed explanation of file evidence categories, recognition rates, and FAQs, refer to our KB article: Understand file evidence in IT Visibility: Recognition, eligibility, and what to expect

     

    For questions, please contact Flexera Support. 

     

    Release Date: 29th June, 2026

     

    Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/identifying-devices-using-evidence

    https://docs.flexera.com/flexera-one/it-visibility/identifying-applications-using-evidence

    Release Documentation: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/june-2026#updates-to-file-evidence-on-the-device-detail-and-software-evidence-pages

    Expand Post

  2. Enhanced IT Visibility Software Evidence UI Experience with Installer, File, and Operating System Evidence 

     

    We’re thrilled to introduce a new tabbed experience on the IT Visibility Software Evidence page (Applications & Evidence > IT Visibility Software > Software Evidence), designed to give you richer, more organized insights into your software inventory. 

     

    With this update, you can seamlessly navigate between three evidence types: 

    • Installer Evidence (default view): Displays All, Active, Irrelevant, and Unrecognized evidence counts, now including Installation Path details.

    Installer Evidence 

    • File Evidence: Shows All and Active (Technopedia Mapped) evidence counts directly in the UI.

    File evidence 

    • OS Evidence: Includes All, Active (Technopedia Mapped), and Unrecognized evidence counts for a comprehensive OS overview.

    OS evidence 

    This enhancement empowers you to filter, track, and manage evidence data with greater clarity and control, bringing full transparency to your software inventory. Installation paths for installer evidence, OS evidence, and recognized file evidence are now available directly within the UI, reducing manual effort and reliance on external queries.

     

    Note: OS and File Evidence are now available on the Software Evidence page and will be extended to Devices, Inventory Normalization Insights, and Private Catalog in future updates. Support for irrelevant evidence will also be added in an upcoming release. Please note that the Software Evidence dataset accessible via the Queries API and Data Exports currently includes only Installer Evidence and does not contain OS or File Evidence. 

    You may notice changes in Active counts in evidence as we continue to improve and streamline the underlying behavior for greater accuracy and consistency. 

     

    This update ensures a complete, accurate, and trusted view of your software environment, enabling better lifecycle management, compliance, and risk decision-making in one place. 

     

    Documentation Links:

     Release note: Software Evidence has new Installer Evidence, File Evidence, and OS Evidence tabs 

    Software Evidence : Identifying Applications Using Evidence  

    Device Evidence : Identifying Devices Using Evidence  

    Private Catalog: Working With the Private Catalog 

    Inventory Normalization : Viewing Inventory Normalization Insights 

    https://developer.flexera.com/docs/page/technology-intelligence-platform-datasets

     

    Expand Post

  3. Unable to unassign evidence for application recognition

    Hi,

    I can unassign evidences for application recognition that are local, but for the ones that are from Flexera's library the "Delete" and "Unassign" buttons are greyd out. Whether I try to do it from the Applications properties (Evidence Tab) or from the All Evidences menu, the problem is the same.

     

    To be clear, with local evidences everything is fine, the problem is only with the Evidences which source is "Flexera".

     

    Am I missing something?

    Tx

    Expand Post

    • Flex-Jeremy (Flexera Software)

      The behavior that you are describing is expected. Evidence and applications that come from the Flexera provided ARL, where the source is "Flexera", cannot be modified.

      If you think that there is an issue with a record in the Flexera provided ARL, please reach out to our Content team by creating a support case.

  4. Does anyone have a best practice for discovering applications that may cache themselves in User AppData folders?

    Reason being - This will show a discrepancy between Installer version (preferred evidence) vs. actual version being used in a cached folder (file evidence). And many of these cached folders will not be scanned as they may be 'noisy' & bloat systems.

     

    Example for Webex - the cached user App Data file has the newest Webex installation and executable files, whereas the Program Files & Registry entry stay at the older version.

     

    This is also due to profiling - for situations where multiple users share a device, they might have different versions in their respective folders.

     

    Thanks!!

    Expand Post

End of Feed
5 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
Loading
Applications and Evidence | Flexera