25.4 enhancements and patches
Review the BMC Helix CMDB 25.4 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.
| Version | SaaS | On-premises | Fixed issues | Updates and enhancements |
|---|---|---|---|---|
| 25.4.00 | ✅ | Known and corrected issues | 25.4.00 updates |
25.4.00 updatesEdit
The following video (00:53) provides a quick overview of the enhancements in the BMC Helix CMDB 25.4.00.
Watch the video that describes the new features in BMC Helix CMDB 25.4
Improved RE performance with Java-based miscellaneous service
The delete, purge, copy, and compare activities in the Reconciliation Engine run in a dedicated Java-based miscellaneous service. This enhancement improves the performance and reliability of the reconciliation engine by separating these activities from the main reconciliation pod. For more information, see Enabling or disabling reconciliation engine services.
Manage product data collection from within the product
You can now manage your product data collection preferences directly from the Analytics option in BMC Helix CMDB. This enhancement provides greater control by allowing you to enable or disable data collection from within the product, without navigating to another console. The data helps improve product performance, identify usage trends, and prioritize feature enhancements.
For more information, see Modifying consent for data collection.
Date and Time fields support dates beyond the year 2038
BMC Helix CMDB Date and Time fields support dates beyond January 19, 2038, helping you store long-range timelines like End of Life (EOL) for configuration items (CIs). With this enhancement, the Date and Time field can store values up to April 11, 2262, 11:47:16.854 PM. This change ensures accurate tracking of future lifecycle data in BMC Helix CMDB.
For more information, see Normalization and the Product Catalog.
What else changed in this release
The following table lists the changes in the product behavior:
| Update | Product behavior in versions earlier than 25.4.00 | Product behavior in version 25.4.00 |
|---|---|---|
| Failover support for CMDB to Smartgraph synchronization for BMC Helix Telco Extensions | If a CMDB to Smartgraph synchronization run failed or if the AR or plug-in server experienced a temporary outage, the entire sync process had to be restarted. | During the sync, if temporary outages or failures occur, the sync automatically resumes from the point of interruption instead of restarting the entire process. This failover mechanism prevents data duplication, minimizes delays, and maintains consistency across synchronized records. For details, see Syncing CIs for BMC Helix Telco Extensions by using SmartGraph Sync. |