
Flexera One Blog — HArumugasamy_E (Flexera Software)
IT Visibility - TI Platform: Key Enhancements to the PBI reports – (Live now - 27th September)
Segmented Button for Lifecycle Dates in Software Reports
We are introducing a segmented button control across the Software reports (8 in total) to give users more flexibility in how they view and analyse lifecycle information. With this update, users can easily switch between Researched lifecycle dates and a Researched + Calculated lifecycle dates (Combined view) - enabling both compliance-focused accuracy and planning-focused comprehensiveness within the same report.
What’s New
- Dynamic Segmented Button
- Allows users to toggle between two lifecycle date views:
- Researched Lifecycle Dates – factual, validated data points, manufacturer provided
- Researched + Calculated dates – includes researched dates with calculated extensions/predicted for missing/incomplete values.
- Report-Wide Updates
- All visuals, tables, and KPIs dynamically update based on the selected option.
- Default state clearly defined (Researched + Calculated dates view).
- Fields Enhancements
- Software Lifecycle Tables now reflect with End Of Life Date Calculated, End Of Life Date Researched Calculated fields, similarly for General availability and Obsolescence.
- Details page has new column added, to highlight the value is from Researched or Researched + Calculated dates
- Customer Action – Update to New Fields
- The previously used field “Calculated Support Lifecycle Stage Name” (which combined researched and calculated values) has been retired and hidden from further use.
- Customers are advised to update any cloned/custom reports to leverage the new fields, which now clearly separate researched and combined lifecycle dates.
- Important: Hiding this field will not break existing cloned reports, but updating them is strongly recommended to align with the new reporting structure and ensure clarity of use.
Why This Matters
- User Flexibility – Supports different user needs, from audit/compliance teams who require strict researched data, to operations teams who need calculated extensions for forecasting and planning.
- Efficiency – Reduces the need for duplicative custom reports, consolidating multiple use cases into a single, more powerful interface.
- Clarity & Trust – Explicitly differentiates between actual researched data and calculated fallback values, ensuring transparency and confidence in reporting.
Business Impact
This release significantly enhances the value of the Software Power BI reports by making them adaptive to diverse decision-making needs. By streamlining how lifecycle data is consumed, it improves efficiency, reduces custom report overhead, and strengthens insights provided—ultimately enabling stakeholders to balance compliance, risk, and planning objectives in one place.
Expanded Fields and Measures on Software & Hardware Statistics Pages
We have enhanced the Statistics Pages within the Software and Hardware Portfolio reports to provide customers with greater flexibility and depth of analysis. Originally, these pages allowed users to select custom fields and measures via checkboxes to quickly view high-level numbers and volumes across their IT estate. With this release, we’ve introduced additional fields and measures—expanding the range of insights available briefly.
What’s New
Hardware Statistics Page Enhancements
- Users can now select from a richer set of fields, including:
- Device-level fields (D): Device Name, Operating System, Last Logged-In User, Calculated User, Logical Count, Number of Processors, Serial Number, Inventory Agent, Obsolete Date, EOL Date.
- Hardware-level fields (H): Last Inventory Date, Chassis Type.
- Virtualization fields (V): VM Name, VM Type.
Software Statistics Page Enhancements
- Expanded field options across software, file, and product dimensions:
- Software fields (S): Application, Edition, IsLicensable, EOL Date, OBS Date, EOL Criticality, Product Family.
- File fields (F): File Name, File Path, File Version.
- Product fields (P): Installation Path, Title, Version, Revision.
- New Measure: Install # Licensable – a key metric highlighting the number of licensable installs.
Why This Matters
- Broader Visibility – Provides users with more granular insights into both hardware and software portfolios.
- Customization Power – Empowers customers to choose exactly which fields and measures matter most to their analysis.
- Customer-Driven Enhancement – Directly responds to customer requests for expanded reporting options on Statistics Pages.
Business Impact
This release strengthens the self-service analytics capability of the portfolio reports by giving customers a more comprehensive, customizable view of their IT estate. With more fields and measures available, organizations can better track compliance, lifecycle milestones, and resource allocation—enabling smarter and faster decision-making.
Release Date: 2025-09-25, 2025-09-27
Product Documentation: https://docs.flexera.com/flexera/EN/ITVisibility/OOTBReportDescriptions.htm,
I am using GraphQL to retrieve the Lifecycle dates. This is what I read:
• Researched Lifecycle Dates - Factual, validated data points, and manufacturer provided.
• Researched + Calculated Dates - Includes researched dates with calculated extensions, predicted for missing, or incomplete values.
However, I see the End of Life Date is a ficticious date, wheras the calculated date looks correct. Am I comparing the correct dates?
Hello @peeder , Thankyou for reaching out. The columns that you have pulled in is right. The 2999 and 1900 are placeholders, which were removed in the BI layer to provide realistic dates and avoid confusions when we are working with graphical representation. So since the Researched date is a placeholder here(Meaning doesn't have any manufacturer provided date), the Calculated/Predicted would help us with an approx. value.
That said, GraphQL changes are in-progress and we would see the same changes reflecting there soon. Let me know if you have anymore questions, happy to jump on a call!😊
Hi @HArumugasamy_E (Flexera Software) ,
Thanks for the update.
What will the GraphQL changes be? A new attribute, or nullifying the contents?
For now, I should ignore any 2999 or 1900 dates. Correct?
Thanks,
Peter
Yes @peeder The graphQL value will be nullified. For now you can ignore the 2999 and 1900 dates there.