IT Visibility - TI Platform

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



ITV Data Explorer Drill-Downs are live - in-context entity detail without leaving the report

You can now click straight into any device or software row in a Data Explorer report and open a slide-out panel with the full, grouped detail for that entity without leaving the report or running a separate query.

Reports are great at breadth: lots of entities side by side. But the moment you need to understand one of them in depth, you used to hit a wall, navigate away, re-query, or ask someone to pull the detail by hand. Drill-downs close that gap. The depth is one click away, in the same view, so you can move from "what's across my estate?" to "tell me everything about this one device" in a single step.

Why it matters

Every context-switch costs an momentum. Jumping out to re-query, or waiting on someone else to pull the detail, is exactly where investigations stall and questions go unanswered. Drill-downs now keep that depth inline, so the person looking at the report is the person who gets the answer in the moment, without breaking flow and without a separate query. That's faster time-to-insight and a lot more self-service for you.

How it works

In a report you have built you can now click into:

• Device detail - core attributes (manufacturer, model, serial, memory, storage) plus grouped sections for business services, lifecycle, network adapters, operating system, processors, installed software, and sustainability metrics.
• Software detail - core attributes (manufacturer, product, version, edition) plus the associated device, lifecycle, taxonomy, installer evidence, and file evidence.

I am also looking for feedback so if there is any improvements you feel we can make to the data returned, please let me know!

SBOM in Flexera One IT Visibility — now GA!

We’re excited to announce the General Availability (GA) of SBOM ingestion and inventory management—now enhanced with automated obsolete data handling.

With this release, you can:

✅ Ingest and normalize SBOM data alongside traditional inventory

✅ Gain deeper visibility into software components and dependencies

✅ NEW: Automatically clean up stale SBOM data with configurable expiry / auto-delete settings

No more manual cleanup. No more outdated inventory lingering in the system.

This is a big step toward trusted, accurate, and unified visibility across modern software supply chains

Documentation:

• Release notes
• SBOM upload docs
• Auto-delete configuration

IT Visibility – Data Export Retention Policy Is Now Live

A 30-day retention policy for Normalize ZIP data exports is now live across all regions.

What's Changed

• All Normalize ZIP exports are automatically and permanently deleted 30 days after the "Requested" date.
• Exports older than 30 days at the time of rollout have already been removed.
• A new "Days Until Deletion" column on the Data Exports page shows remaining days before each export is removed.
• We recommend downloading and securely storing any exports you need before the 30-day window expires, as deleted exports cannot be recovered.
• You can always generate a fresh export anytime from the Data Exports page.

This change applies only to Normalize ZIP exports —Queries API CSVs are not affected.

For questions, please contact Flexera Support.

Reference: https://community.flexera.com/s/feed/0D5PL00000rJg0u0AC

Documentation: https://docs.flexera.com/flexera-one/it-visibility/exporting-data-from-it-visibility/it-visibility-data-export-using-technology-intelligence-platform/exporting-data-using-technology-intelligence-platform-version-of-it-visibility

https://docs.flexera.com/flexera-one/feature-list/new-features-in-2026/may-2026/#it-visibility

Upcoming Change: IT Visibility – Query API Delta Resume Token Invalidation (Action Required on July 20, 2026)

As part of an upcoming platform update, existing IT Visibility Queries API (https://developer.flexera.com/docs/api/vis/v2#/Query) delta resume tokens will be invalidated on July 20, 2026.  

What does this mean? 

On or after July 20, 2026, any delta query that uses an existing resume token will fail. This is a one-time change required to ensure data accuracy going forward. 

What action is required? 

If you consume delta data via the Queries API, please take the following action: 

• Remove the resume token from your current request 
• Run a new query/fresh snapshot on or after July 20, 2026 to generate a new resume token 
• Use the newly generated resume token in subsequent requests to continue using delta queries.   

Additional details 

• Snapshot queries are not impacted 
• No changes are required to the Queries API endpoints or request format 
• This change applies only to delta consumers 

We recommend planning this snapshot run into your workflows ahead of time to avoid any disruption. 

If you have any questions or need assistance, please contact Flexera Support.  

Upcoming Change: IT Visibility – Data Export Retention Policy Update 

We’re updating the retention period for ZIP data exports available on the IT Visibility > Data Exports page. 

Starting in June 2026, all data exports will be retained for 30 days from the “Requested” date, after which they will be automatically and permanently deleted. 

 Rollout schedule by region 

• APAC: 1 June 2026 
• EU: 4 June 2026 
• NAM: 9 June 2026 

What this means for you 

• Any export requested on or after your region’s effective date will be available for download for 30 days. 
• Any existing exports that are already older than 30 days at the time of rollout will be permanently removed on the rollout date. 

What’s new 

To help you track this more easily, a new “Days Until Deletion” column will be added to the Data Exports page. This will show how many days remain before each export is deleted. 

Please ensure you download and securely store any exports you need before the 30‑day retention period expires. Once deleted, exports cannot be recovered. 

If you have any questions, please contact Flexera Support.