Skip to Content

25.4.00 enhancements and patches

Review the BMC Helix Telco Extensions 25.4 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

✅️

 

For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.

Related topics

Managing-incident-requests

Managing change requests

Managing-service-targets

Administering

 

25.4.00

Update TMF621 trouble tickets without replacing the entire record

Use the patch endpoints in the TMF621 trouble ticket API to update specific fields in trouble tickets, such as alarms, assets, source requests, notes, or related parties, without replacing the complete record. This enhancement helps maintain data consistency and reduces processing efforts during ticket management.​​​​

For more information, see Endpoints in REST APIs.

Improved alarm creation and CI mapping via TMF621 APIs

Integrate external monitoring systems with BMC Helix Telco Extensions through the enhanced TMF API. With this improvement, create alarms with only essential fields and search configuration item (CI)  by using either ReconciliationIdentity or CI Name. You can also retrieve the status change history from HPD:WorkLog in trouble ticket GET responses. These enhancements reduce alarm rejection, improve incident accuracy, and streamline fault management workflows for telecom providers.

For more information, see Endpoints in REST APIs.

Dedicated telco roles for operational clarity

BMC Helix Telco Extensionsincludes new functional roles, Telco Agent and Telco Config, to distinguish Telco users from general BMC Helix ITSM users. These roles provide clear separation of responsibilities and focused access to telco-specific capabilities such as alarm management, ticket prioritization, and configuration settings.

Telco functional roles

For more information, see Roles and permissions.

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

 

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.

<Will be updated with the target space link>

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Telco Extensions 25.4