IT Visibility - TI Platform

IT Visibility - TI Platform: Windows Catalog Alignment Update: Market Name Added to Software Reports

As part of ongoing catalog alignment efforts between ARL and Technopedia, Windows catalog entries have been standardized by removing version information from product names. This change supports a more consistent software catalog experience across Flexera solutions.

Customers whose reporting or integrations previously relied on product names for product-version identification may need to review these changes and utilize the updated catalog attributes and identification methods to ensure consistent reporting and data interpretation. To ensure and easily identify and analyze Windows versions, the Market Name field (also known as Version Group) is being added alongside Product Name in key Power BI software reports.

What's Changing?

The Market Name column will now be available next to Product Name, making it easier to:

• Identify Windows version
• Filter and segment software inventory
• Perform version-based reporting and analysis

Reports Updated

The following OOTB reports are enhanced:

• Comprehensive Software Inventory
• Software Portfolio Overview
• Operating System Insights
• Proactive SW EOL and Obsolescence Guidance
• Software Sprawl
• Version Update Planner
• Strategic SW Insights
• Software Procurement Guardian
• Business Service Insights
• Cloud Inventory Overview       
• Comprehensive Hardware Inventory
• Device Search
• Hardware Portfolio Overview
• Host and VM Relationship
• Proactive HW End of Sale and Obsolescence Guidance
• Software Vulnerability Insights

For Custom Reports

Customers using custom Power BI reports are encouraged to include the Market Name field in their report filters and visualizations to simplify version-level reporting.

Customer Impact

The Market Name field is already available within the data model. This enhancement simply makes it more visible within out-of-the-box reports, helping customers maintain version-level visibility following the catalog alignment changes.

Summary

The addition of Market Name to Power BI software reports ensures customers can continue to easily identify and report on Windows versions while benefiting from a more standardized catalog structure across Flexera solutions.

Release Date: 09/04/2026

Linked to: https://community.flexera.com/s/feed/0D5PL00000w4nNJ0AY

IT Visibility – TI Reporting: Enhancement - Container Software Visibility Live Now!

The Container Inventory Overview Report now extends infrastructure visibility by providing insights into the software deployed inside container workloads, helping organizations understand not only where containers run, but also what technologies they contain.

The report includes:

• Top 10 Software Releases by Containers – Identify the most widely deployed software releases across container environments.
• Software Technology Currency for Containers – Evaluate current software versions and identify opportunities to upgrade.
• Obsolete Software Releases by Year – Track software releases that have reached obsolete status to proactively reduce operational and security risk.
• Software Releases Summary Table – View a consolidated inventory of software releases, associated versions, lifecycle status

This visibility enables teams to improve software governance, strengthen compliance and reduce risks associated with outdated software running inside containers.

Release Date: 09/04/2026

Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-tip-reports/technology-intelligence-platform-report-descriptions/ , https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-tip-reports/technology-intelligence-platform-report-descriptions/container-inventory-overview , https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-custom-reports/working-with-measures#measures-available-for-hardware-report-type , https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/understanding-report-types#hardware

Release Notes: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/september-2026#software-visibility-now-available-in-container-inventory-overview-report

Previous reference Blog: https://community.flexera.com/s/feed/0D5PL00000umX8Y0AU

IT Visibility - TI Reporting: Restore Deleted Custom Reports – Live Now!

Recover deleted custom reports with confidence.

We’ve introduced the ability to restore deleted custom reports in TI Platform, helping users recover reports that were accidentally removed without having to recreate them from scratch.

Users with the Manage custom reports role can now access a Deleted Reports List from the Custom Reports page, review reports deleted within the last 30 days, and restore them when needed. Once restored, reports are returned to the regular Reports List and can be used again.

This enhancement improves report resiliency and user control, reducing the impact of accidental deletion and helping preserve the effort invested in building custom reports.

Key considerations:

• Deleted reports are recoverable for 30 days.
• Reports deleted beyond 30 days are permanently removed.
• Restoration requires the Manage custom reports role.
• If a report with the same name already exists, the restored report is automatically renamed with _restored.
• Restoration is processed asynchronously and may take some time depending on Power BI processing.

Value:

Users now have a simple recovery mechanism for accidental report deletion, reducing rework and providing greater confidence when managing custom reporting assets.

Release Date: 09/03/2026

Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-custom-reports/restoring-a-deleted-custom-report

Release Notes: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/august-2026

New in IT Visibility: Device Domain Visibility and Technopedia Subversion for Software Evidence

Available with IT Visibility

We're excited to share two enhancements that give you greater clarity and precision when working with device and software evidence data in IT Visibility.

 1. Domain column added to the Devices page

IT Visibility now displays the domain of a device on the Devices page (Inventory > IT Visibility Devices > Devices).

The Domain column is visible by default in the device list, and the Domain field appears on the Device Properties tab when you open a device.

Why this matters: IT Visibility identifies devices using a composite key of hostname, domain, and serial number. Two devices that share the same hostname but belong to different domains are stored as distinct records. The Domain column and field help you understand why devices with identical hostnames appear as separate records.

With this update, you can:

• View the domain of each device in the device list.
• Filter and sort the device list by domain.
• Search for devices by domain using the global search.
• Export device domain data in CSV format.

For more information, see Identifying Devices Using Evidence.

2. Technopedia Subversion field added to Software Evidence

IT Visibility now shows the Technopedia Subversion field in the following locations, along with their evidence detail pages:

• The Installer Evidence, File Evidence, and OS Evidence views on the Software Evidence page.
• The Software Evidence - Installer, Software Evidence - File, and Software Evidence - OS tabs on the Device Detail page.

Why this matters: The Technopedia Subversion field shows the subversion stage of a Technopedia release, for example

RC1,GA, or Beta. This helps you distinguish between releases that share the same version string but differ in release type, such as a Release Candidate versus a General Availability build.

Note: The Technopedia Subversion column is not visible by default. To show it, use the column chooser on the relevant tab.

With this update, you can:

• View the Technopedia Subversion for each evidence item on the Software Evidence page and the Device Detail page.
• Search for evidence by Technopedia Subversion using the global search.
• Export the Technopedia Subversion value in CSV downloads for all three evidence types.

For more information, see Identifying Applications Using Evidence and Identifying Devices Using Evidence.

Release Notes

Reminder: IT Visibility Export/Parquet API Retirement (August 31, 2026)

Reminder that the legacy IT Visibility Export/Parquet API will be retired on August 31, 2026, as previously communicated in post

For customers still using the Export/Parquet API, final Parquet files will remain accessible for 90 days after retirement. Please transition to the Technology Intelligence Platform GraphQL API or Query API.

If you have any questions or need assistance with the transition, please contact support@flexera.com. 

Thank you for your continued partnership with Flexera. 

IT Visibility: TI reporting - New Report Release Update

Container Inventory Overview – Live Now!

The Container Inventory Overview report introduces a comprehensive view of containerized environments within the TI platform, enabling customers to gain structured visibility into their container ecosystem—from underlying infrastructure to container-level insights.

Note: As part of this release, the report focuses on Kubernetes container environments, providing comprehensive visibility across your Kubernetes ecosystem. Stay tuned, as we're actively enhancing this experience in future releases by expanding support to Podman and Docker environments, while also bringing in Container Software visibility extending the report beyond infrastructure and runtime into the software layer inside containers.

Problem Statement

Customers face limited visibility and fragmented insights into their container environments, making it difficult to answer key questions such as:

• What containers are running across the environment?
• How are they structured across clusters, nodes, and pods?
• Where are these workloads running?
• What is their operational and lifecycle state?

What’s New

1. Container Visibility

• Introduces containers as a first-class reporting entity within the platform
• Provides a consolidated view of clusters, nodes, pods, and containers
• Bridges the gap between raw container data and actionable insights

2. Container Ecosystem Intelligence (What / Where / Structure / State)

• What: KPIs for total clusters, nodes, pods, and containers
• Where: Distribution across clusters, nodes, and pods
• Structure: Hierarchical mapping (Cluster → Node → Pod → Container)
• State: Running vs terminated containers with restart insights

Outcome: Enables customers to move from fragmented visibility to a structured understanding of their container ecosystem.

3. Infrastructure & Lifecycle Insights

• Hardware visibility: Manufacturer, model, and product distribution
• Lifecycle tracking: Node Hardware Lifecycle stages such as GA, End of Sale, and Obsolete
• Risk visibility: Identification of nodes approaching obsolescence
• Infrastructure context: OS, CPU, memory, storage, location, business unit, and cost center
• Workload distribution: Containers, pods, and nodes across clusters

Outcome: Connects container workloads with underlying infrastructure risk, lifecycle, and scalability insights.

4. Container Ecosystem Analytics

• Hierarchical visualization of container environments
• Node-level mapping of container deployments
• Container growth and churn tracking over time
• Restart indicators to highlight instability
• Pod-level health and status visibility

Outcome: Enables customers to monitor container health, understand adoption patterns, and track operational stability.

5. Drill-Through & Detailed Inventory

• Seamless drill-through across:
  • Clusters → Nodes → Pods → Containers
• Detailed metadata views for deeper analysis

Outcome: Empowers platform, infrastructure, and operations teams to move from visibility to actionable decision-making.

Key Value Delivered

• Transforms fragmented container data into a structured ecosystem view
• Converts raw metadata into meaningful operational insights
• Connects infrastructure and containers into a unified, end-to-end story
• Enables better governance, planning, and optimization of container environments

Release Date: 06/30/2026

Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-tip-reports/technology-intelligence-platform-report-descriptions/container-inventory-overview, https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/understanding-report-types, https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-custom-reports/working-with-measures, https://docs.flexera.com/itam-discovery/gathering-flexnet-inventory/k8s-agents

Release Notes: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/june-2026

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

IT Visibility: TI reporting Updates

Report Replication Across Organizations - Live Now!

Feature Overview

The TI Platform now supports Report Replication Across Organizations, enabling authorized users to efficiently replicate custom and out-of-the-box reports from one organization to multiple destination organizations. This capability reduces manual effort, improves reporting consistency, and accelerates report deployment at scale.

What's New

Replicate Reports Across Multiple Organizations

Users can now clone an existing report and distribute it to one or more destination organizations through a guided replication workflow.

Comprehensive Report Structure Replication

The replication process preserves the complete report design and configuration, including:

• Report visuals (charts, KPIs, tables, and other report elements)
• Report layout and visual positioning
• Filters and slicers
• Report-level configurations and settings
• Report metadata, including source organization and creator information

This ensures a consistent reporting experience across organizations without requiring manual recreation.

Permissions & Access

The Report Replication capability is available to users with Manage Custom Reports permissions, helping to ensure that report replication activities are performed only by authorized users.

Replication Workflow

• Navigate to Reports and select a Custom Report or Out-of-the-Box Report.
• Choose the Replicate option.
• Select one or more destination organizations.
• Define replication handling preferences:
  • Overwrite Existing Report
  • Create New Copy
  • Skip Existing Report
• Submit the replication request.
• Monitor replication progress and status for each destination organization.

Dependency Handling

Report Replication transfers the report structure and configuration only. The following are not replicated:

• Underlying datasets
• Data sources
• Organizational data

If the destination organization contains the required datasets and dependencies, the replicated report will function as expected.

If dependencies are unavailable, the report structure will still be imported successfully. Users will receive warnings or error messages identifying unresolved datasets, mappings, or configuration dependencies, allowing remediation after replication.

Enhanced Status Visibility

To improve troubleshooting and operational efficiency:

• Replication status is available for each destination organization.
• Hovering over a Failed or Error status displays detailed failure information.
• Error details help users quickly identify issues such as:
  • Missing permissions
  • Configuration conflicts
  • Missing datasets or dependencies
  • Replication processing errors

Benefits

• Reduces manual report creation and maintenance effort
• Improves consistency across organizations
• Accelerates report onboarding and deployment
• Supports scalable report governance and administration
• Provides greater transparency into replication outcomes and failures

Important Notes

• Report Replication copies report structure, configurations, and metadata only.
• Organizational data and datasets are not transferred during replication.
• Destination organizations must have the necessary data sources and dependencies available for full report functionality.
• Reports can be replicated to multiple organizations in a single operation, simplifying large-scale report rollouts.

Release Date: 06/29/2026

Product Documentation: https://docs.flexera.com/flexera-one/it-visibility/it-visibility-with-tip-reports/working-with-custom-reports/replicating-reports-across-organizations/  

Release Notes: https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/june-2026#replicate-custom-reports-across-organizations