Title

FlexNet Inventory Agent Version Group Correction

Class 3

Minor updates as a result of "Business-As-Usual (BAU)" activities, which historically cause no adverse impact on customers' environment except for coverage increase

Summary

Flexera identified an inconsistency in FlexNet Inventory Agent releases that were created in Technopedia.

FlexNet Inventory Agent uses two version formats:

-> Market-facing release versions: 2023 R1.3, 2023 R2.1, etc.

-> Internal Agent/Beacon versions: 20.4, 21.1, etc.

FYI: https://community.revenera.com/s/article/what-flexnet-inventory-agent-amp-beacon-release-number-corresponds-to-each-product-version

Both formats represent the same product releases; however, AR data contains evidence in both version formats. To maintain consistency across Technopedia records, Flexera has standardized the versioning approach as follows:

-> Version = Internal Agent/Beacon version (e.g., 20.4)

-> Version Group = Market-facing release version (e.g., 2023 R1.3)

As part of this standardization effort, we identified approximately 110 releases that were previously created with an incorrect Version Group association.

As part of this correction activity, Flexera has created the releases using the standardized versioning structure. Approximately 110 existing releases in Technopedia that were created with incorrect Version Group associations will be deleted and replaced by the correctly structured release records to maintain consistency across Technopedia.

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID & names, and will also map previously discovered data that was mapped to the incorrect versions to the corrected new versions. The change requires the customer to manage downstream processes and reporting in their organization.

Both the existing releases with incorrect Version Group associations and the newly created releases with the correct Version Group are currently present in Technopedia, which may result in releases that appear to be duplicates. To give customers time to review the changes, releases with incorrect Version Group values will remain temporarily and be deleted as per the communicated ETA.

The spreadsheet FlexNet Inventory Agent lists the releases created with an incorrect Version Group and the corresponding correct releases that will replace them.

Timeframe

Expected Time to Implementation (ETA):  July 13th to 17th, 2026.

Thank you.

Title

IBM Security Directory Server Component Filesets – Not Eligible for Mapping

Class 3

Minor updates as a result of "Business-As-Usual (BAU)" activities, which historically cause no adverse impact on customers' environment except for coverage increase

Summary

We will ignore this evidence, as it is a component of IBM Security Directory Server. These are LDAP client/base file sets that are part of a larger IBM Security Directory Server / Verify Directory package. They are not standalone installable products but supporting components delivered as part of an AIX package set. Based on the review, this evidence is not valid and will be ignored in both libraries.

Please refer to this URL: https://www.knime.com/downloads

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID & Names or previously discovered data mapped. The change requires the customer to manage downstream processes and reporting in their organization.

The Security Verify Directory server spreadsheet provides the complete list of evidence that will be marked as Irrelevant.

Timeframe

Expected Time to Implementation (ETA):  July 6th to 10th, 2026.

Thank you.

Title

Manufacturer upgrade: Trustwave acquisition by LevelBlue

Class 3

Minor updates as a result of "Business-As-Usual (BAU)" activities, which historically cause no adverse impact on customers' environment except for coverage increase

Summary

During internal quality assessments, Flexera discovered that Trustwave was acquired by LevelBlue. Consequently, Flexera will undertake the manufacturer lineage as part of this product's releases and mappings, transitioning from the previous manufacturer, Trustwave, to the new manufacturer, LevelBlue.

Please refer to the URL below for acquisition details

https://www.levelblue.com/blogs/levelblue-blog/levelblue-acquires-trustwave-ushering-in-a-new-era-as-the-worlds-largest-pure-play-mssp

Impact:

This modification will affect customers who depend on Technopedia Product ID/Release ID and Names, as well as previously identified data associated with the old product, which will now be linked to the new product. Customers will be required to oversee their downstream processes and reporting within their organization as a result of this change.

The spreadsheet “Trustwave to LevelBlue” provides the complete list of all the products/releases/mapping for which the dependency of the old manufacturer (Trustwave) will be updated to the new manufacturer (LevelBlue)

Timeframe

Expected Time to Implementation (ETA):  July 8th to 15th, 2026.

Thank you.

Title-

Manufacture update :CyberArk to Palo Alto Networks

Class 3

Minor updates as a result of "Business-As-Usual (BAU)" activities, which historically cause no adverse impact on customers' environment except for coverage increase

Summary

Based on our analysis, the manufacturer needs to be updated from CyberArk to Palo Alto Networks. All CyberArk products and releases should be moved under Palo Alto Networks.

Flexera will also migrate all associated products, releases, and mappings from the old manufacturer CyberArk to the new manufacturer Palo Alto Networks.

Link : https://www.paloaltonetworks.com/company/press/2026/palo-alto-networks-completes-acquisition-of-cyberark-to-secure-the-ai-era

These changes are being implemented to ensure alignment across both ARL and Technopedia (TNP) environments and to avoid any mapping issues.

Impact

This change will impact customers who rely on Technopedia Product ID/Release ID & Names, or previously discovered data mapped to the old manufacturer, will be mapped to the new manufacturer. The change requires the customer to manage downstream processes and reporting in their organization.

The spreadsheet “CyberArk to Palo Alto Networks “provides the complete list of software products for which the product name will be renamed from “CyberArk to Palo Alto Networks”

Timeframe

Expected Time to Implementation (ETA):  July 13th to 17th, 2026.

Thank you.

Title: Manufacture Name Update - Corelogic to Cotality

Class 2- Moderate Update for Tier 3 Manufacturer

This update introduces significant coverage changes that could adversely affect some customers. If these changes aren't reviewed in advance, they could affect customer environments. Please be aware and make any necessary adjustments.

Summary

The manufacturer will be updated from CoreLogic to Cotality, with all associated products, releases, and mappings migrated accordingly. Flexera is performing a complete transition to ensure continuity under the new manufacturer. These updates are being executed in coordination with the ARL team to maintain alignment across ARL and Technopedia (TNP) environments and prevent any mapping inconsistencies.

Ref: CoreLogic Rebrands to Cotality: A Bold Vision for Property

Impact

This change will impact customers who rely on Technopedia Product IDs, Release IDs, and product names, as well as any previously discovered data mapped to the old manufacturer (CoreLogic), which will now be updated to the new manufacturer (Cotality). Customers may need to review and adjust their downstream processes and reporting to align with these updates.

The spreadsheet “Corelogic to Cotality” provides the complete list of affected software products for which the product names are being updated as part of this transition.

Timeframe: 

Expected Time to Implementation (ETA): July 13th,2026 to July 17th,2026.

Thank you

Title: OneNote Evidence Re-Recognition Changes

Class 1

Major updates which introduce new content to support new product features/capabilities, modify existing content to change the behavior of existing product features/capabilities, or deprecation of any existing content (along with the associated product features/capabilities), which require all customers to make necessary adjustments beforehand

Summary

Context:

Currently, the Technopedia and ARL libraries have Alignment issues with respect to Product OneNote, especially with Microsoft 365 subscription versions. These are mentioned in the link: Update history for Microsoft 365 Apps (listed by date) - Office release notes | Microsoft Learn

Current Process: 

If the Discovery Name/evidence for OneNote has a discovery version with a Microsoft 365 subscription, it is currently recognized as the Microsoft 365 Product (PID 1054728482)

Proposed changes: 

Flexera is planning to curate a new product as OneNote for 365, along with curating the Microsoft 365 subscription versions and Re -Recognition of the evidence. This has already been mapped to the Microsoft 365 Product (PID 1054728482), where the Discovery Name includes OneNote.

These changes are only for Technopedia since the ARL library has the correct format.

Impact

This change will impact our previously discovered data mapped to the old product, which will be mapped to the new product. The change requires the customer to manage downstream processes and reporting in their organization.

Note:

->  As part of the new CCN process, releases with the updated name have already been created in Technopedia.

-> The migration of discovered data mappings will occur after 1, 2, or 4 weeks, depending on the CCN type. For this case, it will be one week.

->  Accordingly, the new release IDs are included in the spreadsheet to help manage downstream processes and organizational reporting

The new changes will impact both the catalog and evidence mapping levels, as updates and deletions at the existing catalog level will directly affect the existing normalized Mappings.

The details of these Sample evidence, products, and releases are provided in the attachment

Timeframe

Expected Time to Implementation (ETA):  July 3rd, 2026.

Thank you.

Title: Product Deletion Notification

Class 2- Minor Update

This update introduces significant coverage changes that could adversely affect some customers. If these changes aren't reviewed in advance, they could affect customer environments. Please be aware and make any necessary adjustments.

Summary

These products have been identified as free utilities that do not meet Technopedia criteria for core, widely used, or enterprise-grade software components, and are therefore proposed for deletion from Technopedia.

Products Identified for Deletion:

Impact

This change may affect customers relying on Technopedia Product ID/Release ID, associated naming, and previously discovered mapped data. As these products no longer meet eligibility criteria, the related evidences will be marked as irrelevant, requiring customers to assess and manage the impact on their downstream processes and internal reporting.

The spreadsheet “Products Identified for Deletion” provides the complete list of all the software products to be deleted.

Timeframe: 

Expected Time to Implementation (ETA): June 29th 2026 to 2nd July 2026.

Thank you

Introducing ‘Unspecified’ Version and Edition in Technopedia

Overview

Technopedia is introducing a new set of catalog-only releases with Unspecified Version and Unspecified Edition.

These releases are designed to enhance catalog completeness and alignment while addressing scenarios where precise version or edition information is not available via standard discovery methods. These releases are:

• Catalog-only entries
• Not linked to any discovery data or evidence in the global catalog.
• Not normalized to existing application mappings.
• Not curated with lifecycle dates but will have regular exceptions.

What Are ‘Unspecified’ Releases?

• “Unspecified Version” and “Unspecified Edition” represent generic placeholders within the Technopedia catalog when:
  • A manufacturer and product can be validated, but exact version and/or edition details are not available.
  • Different versions and editions of the software are documented in the vendor literature but are not available for standard normalization.
• These catalog entries will not be linked to any installation, inventory or usage signals.
• Since the manufacturer and product is validated, this software will have standard Technopedia categories.
• Lifecycle dates will not be available. An exception of “Date not published by the vendor” will be curated.
• Unspecified version will be placed at the end of the version order.

Why Are We Introducing ‘Unspecified’ Releases?

 The introduction of unspecified releases addresses a critical need in catalog management:

1. Enabling a Single Logical Catalog with Consistent Data Alignment

Technopedia aims to provide unified, and logically consistent catalog across all applications while ensuring alignment across multiple data sources and systems.

In practice, not all upstream or downstream sources provide complete metadata, such as:

• Version-level details
• Edition-level classification

Without a structured approach to handle these gaps:

• Products with incomplete data may be excluded from the catalog
• Inconsistencies may arise across integrated systems
• Downstream alignment and reporting can be impacted

By introducing “Unspecified” Version and Edition:

• All known software products can be consistently represented in the catalog
• Alignment is maintained across disparate datasets and systems
• A standardized mechanism is established to handle incomplete data
• Logical structure and hierarchy are preserved without forcing incorrect mappings

This ensures Technopedia can maintain both catalog completeness and cross-system consistency, even when source data is partial or ambiguous.

2. Handling Incomplete or Ambiguous Data

In real-world scenarios, data may be:

• Partial
• Ambiguous
• Unverified

Instead of forcing incorrect mappings or discarding data:

• Unspecified entries act as safe, neutral placeholders
• Prevent incorrect normalization
• Preserve data integrity

Impact on Customers

What This Means

• You may see additional entries with Unspecified version and edition.
• These entries are expected and intentional
• They ensure no loss of product representation

What This Does NOT Mean

• They do not represent deployable or discoverable versions
• They will not affect existing normalized releases.
• They will not affect license calculations or usage data directly

Best Practices

• Treat unspecified entries as placeholders for incomplete metadata
• Avoid using them for:
  • Compliance validation.
  • Lifecycle planning.
  • Version-specific decision-making.
• Prefer versioned/edition-specific entries when available.