Use the steps in this article to remove legacy Software Models that are no longer required following the Technopedia Windows and Windows Server product consolidation.
Proceed with this cleanup only after the Software Discovery Model cleanup has completed and all Discovery Models that were skipped during that cleanup have been reviewed.
The cleanup is performed using a controlled dry-run and deletion process, allowing you to review all identified Software Model records before any data is deleted.
-
Create a Scheduled Script Execution
In the Global application scope, create a new Scheduled Script Execution (
sysauto_script) record.Use the following name:
Cleanup Software Model Records for Windows Servers and Products Impacted by Technopedia Consolidation -
Configure the execution
Set the Run option to:
On DemandThis ensures that the cleanup script is executed only when explicitly triggered and allows the identified Software Model records to be reviewed and validated before deletion.
-
Add the cleanup script
Add the following script to the Scheduled Script Execution.
CAUTION: This script deletes data when
EXECUTE_DELETIONis set totrue. Keep the flag set tofalsefor the initial execution and review the complete dry-run output before enabling deletion.(function() { // SAFETY FLAG: // false = Dry run only. No records are deleted. // true = Delete the validated records. var EXECUTE_DELETION = false; var PRODUCTS = [ 'Windows Server 2016', 'Windows Server 2019', 'Windows Server 2022', 'Windows Server 2025', 'Windows 10', 'Windows 11' ]; var model = new GlideRecord('cmdb_software_product_model'); if (!model.isValid()) { gs.error( '[Technopedia Cleanup] Invalid table: cmdb_software_product_model' ); return; } if (!model.isValidField('x_fls_flexeraone_technopedia_id') || !model.isValidField('product')) { gs.error( '[Technopedia Cleanup] Required fields are missing. Cleanup aborted.' ); return; } model.addNotNullQuery('x_fls_flexeraone_technopedia_id'); model.addQuery( 'product.prod_name', 'IN', PRODUCTS.join(',') ); model.query(); gs.info( '[Technopedia Cleanup] Mode=' + (EXECUTE_DELETION ? 'DELETE' : 'DRY RUN') + ' | Total matching records=' + model.getRowCount() ); var deletedCount = 0; while (model.next()) { gs.info( '[Technopedia Cleanup] ' + (EXECUTE_DELETION ? 'Deleting: ' : 'Matched: ') + 'Sys ID=' + model.getUniqueValue() + ' | Display Name=' + model.getValue('display_name') + ' | Technopedia ID=' + model.getValue('x_fls_flexeraone_technopedia_id') + ' | Product=' + model.product.prod_name + ' | Version=' + model.getValue('version') + ' | Edition=' + model.getValue('edition') ); if (EXECUTE_DELETION) { model.deleteRecord(); deletedCount++; } } if (EXECUTE_DELETION) { gs.info( '[Technopedia Cleanup] Cleanup completed. ' + 'Deleted records=' + deletedCount ); } else { gs.info( '[Technopedia Cleanup] DRY RUN completed. ' + 'No records were deleted. Review and validate the output ' + 'before setting EXECUTE_DELETION=true.' ); } })();The cleanup script targets Software Model records that:
- Have a FlexeraOne Technopedia ID.
- Are associated with one of the Windows products impacted by the Technopedia consolidation:
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
- Windows 10
- Windows 11
- Pass validation of the required table and fields before processing begins.
The
EXECUTE_DELETIONflag provides a controlled two-stage cleanup process so that all identified records can be reviewed before any deletion occurs. -
Run the cleanup in dry-run mode
For the initial execution, keep the safety flag set to:
var EXECUTE_DELETION = false;Run the Scheduled Script Execution On Demand.
In dry-run mode, no records are deleted.
The script logs the total number of matching Software Model records and the following information for each identified record:
- Sys ID
- Display Name
- Technopedia ID
- Product
- Version
- Edition
The dry run must be reviewed before enabling deletion.
-
Review and validate the dry-run results
After the Scheduled Script Execution completes, navigate to:
System Logs > System Log > All
To locate only the logs generated by this cleanup script, apply the following filter:
Message contains
[Technopedia Cleanup]Review the following information before proceeding with deletion.
-
Validate the execution mode and record count
At the beginning of execution, the script generates a summary log similar to:
[Technopedia Cleanup] Mode=DRY RUN | Total matching records=25Confirm that:
- Mode = DRY RUN, confirming that deletion was disabled.
- Total matching records represents the expected number of Software Model records identified by the cleanup criteria.
An unexpected record count should be investigated before proceeding.
-
Validate each matching Software Model
The script generates a separate log entry for every Software Model identified for cleanup.
Example:
[Technopedia Cleanup] Matched: Sys ID=xxxxxxxx | Display Name=Windows Server 2019 Standard | Technopedia ID=xxxxxxxx | Product=Windows Server 2019 | Version=2019 | Edition=StandardReview the records and confirm that:
- The target record has a FlexeraOne Technopedia ID.
- The Product belongs to one of the affected legacy Windows products.
- The Display Name, Version, and Edition correspond to the expected legacy Software Model.
- The record is no longer required following the Technopedia product consolidation.
-
Validate customer-specific dependencies
Before deleting the identified Software Models, verify that they are not required by customer-specific configurations or processes.
Review, where applicable:
- Customer-specific entitlements
- Discovery mappings
- Manually maintained relationships
- Custom integrations
- Custom scripts or business logic
- Other processes that may depend on the identified Software Models
Any Software Model that is still required by a customer-specific process should be investigated before deletion.
-
Validate dry-run completion
At the end of the execution, confirm that the following log is present:
[Technopedia Cleanup] DRY RUN completed. No records were deleted.This confirms that the validation execution completed successfully without deleting any Software Model records.
-
-
Enable deletion
Proceed only after:
- The dry-run output has been completely reviewed.
- The identified records have been confirmed as legacy Software Models.
- Customer-specific dependencies have been reviewed.
- The results have been approved for deletion.
Change:
var EXECUTE_DELETION = false;to:
var EXECUTE_DELETION = true;Save the Scheduled Script Execution.
-
Run the cleanup
Run the Scheduled Script Execution again On Demand.
With
EXECUTE_DELETION = true, the script deletes the Software Model records that match the cleanup criteria.For each record being processed, a log entry similar to the following is generated:
[Technopedia Cleanup] Deleting: Sys ID=xxxxxxxx | Display Name=Windows Server 2019 Standard | Technopedia ID=xxxxxxxx | Product=Windows Server 2019 | Version=2019 | Edition=StandardAt the end of the execution, the script generates a summary similar to:
[Technopedia Cleanup] Cleanup completed. Deleted records=25Review the logs and confirm that the number of deleted records matches the records approved during the dry-run validation.
-
Validate the cleanup
- Navigate to the Software Model (
cmdb_software_product_model) table. - Verify that the validated legacy Software Models have been removed.
- Confirm that Software Models outside the affected Windows product list remain unchanged.
- Navigate to System Logs > System Log > All.
- Filter using Message contains
[Technopedia Cleanup]. - Confirm that the cleanup completed successfully and that the expected number of records was deleted.
- Navigate to the Software Model (
After successful completion of the cleanup:
- Validated legacy Software Models associated with the affected Windows and Windows Server products are removed.
- Software Models outside the defined cleanup criteria remain unchanged.
- The cleanup is performed only after the records have been reviewed through the dry-run process.
- The environment no longer retains the targeted legacy Software Models created from the pre-consolidation Technopedia product structure.
Related Articles
Clean Up Legacy Software Discovery Models following upgrade to FlexeraOne Scoped App 1.8.4 3Number of Views Enable CI class mapping rules for Flexera One IT Visibility 1.6 ServiceNow scoped app 14Number of Views Connect App Portal to Flexera One IT Asset Management without Flexera Service Gateway 11Number of Views ServiceNow application properties showing incorrect scoped app version after upgrade 16Number of Views Migration Instructions: Flexera Integration App to Flexera One App 23Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago