25.4 enhancements and patches
Related topics
Review the BMC Helix Intelligent Automation 25.4 enhancements and patches for features that will benefit your organization and to understand the changes that might impact your users.
| Version | Saas | On-premises | Fixed issues | Updates and enhancements |
|---|---|---|---|---|
| 25.4.00 | ✅ | Known-and-corrected-issues | 25.4 enhancements |
For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.
BMC Helix applies upgrades as described in the BMC Helix Upgrade policy. BMC Helix applies upgrades and patches during Maintenance windows .
25.4.00
Configure multiple connectors for the same automation tool
Configure multiple connector instances for the same automation tool by using unique plugin keys. Use this feature to set up separate connectors for each use case while using the same target ID and provider ID. User can create policies by using multiple connector for the same target ID. If a connector is disconnected or the plugin key expires, you can update the policy to switch to another connector from the list and continue using the same automation tool.
For more information, see:
- Viewing, editing, and copying automation policies
- Configuring the Ansible Automation Platform on-premises connector
- Configuring the BMC Helix Operations Management on-premises connector
- Configuring the Kubernetes on-premises connector
- Configuring the Generic REST API on-premises connector
- Configuring the TrueSight Orchestration on-premises connector
- Configuring the TrueSight Server Automation on-premises connector
Select a Generic REST connector from the list to forward events
On the Configure an Action page, you can view a list of Generic REST connectors that share the same plugin key as the selected BMC Helix Operations Management connector. Select one to forward events to a third-party application. If only one matching connector is available, BMC Helix Intelligent Automation selects it automatically. This enhancement allows you to use multiple connectors to forward events to the same third-party application, offering greater flexibility and control.
For more information, see Forwarding events from BMC Helix Operations Management to third-party applications.
Reduce incident noise by using the Associate incident to incident Policy
When an incident is created for an event before it is added to a situation, and the same event is later included in a situation, BMC Helix Intelligent Automation automatically triggers the Associate incident to incident Policy. This policy uses the ML situation ID to link the original incident with the new situation-based incident.
This enhancement helps eliminate duplicate incidents, improve incident correlation, and automatically close the original incident once the correlated situation is resolved in BMC Helix ITSM.
For more information, see:
- Overview of Proactive Service Resolution
- Configuring Proactive Service Resolution for incidents in BMC Helix ITSM
