24.4 enhancements and patches
For updates and enhancements in the previous release and its patches, see Release-notes-and-notices.
BMC applies upgrades as described in BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows.
24.4.02
Use a proxy server for communication between BMC Helix Intelligent Automation and third-party automation tools
When configuring an on-premises connector, you can use a credentials file in a JSON format to create credentials in a single step. In this file, you can specify a parameter to indicate whether a proxy server should be used to communicate between BMC Helix Intelligent Automation and the endpoint automation tool. If you have a proxy server configured, by default, connectors use it to communicate with BMC Helix Intelligent Automation.
This setup helps you connect with automation tools outside the same network domain as the BMC Helix Intelligent Automation application. For more information about the sample credentials file, see Configuring-the-Generic-REST-API-on-premises-connector.
24.4
Proactive Service Resolution enhancements
The following enhancements are available for Proactive Service Resolution for incident and trouble ticket management systems:
View the host name and situation severity in the incident notes in BMC Helix ITSM
When incidents are created in BMC Helix ITSM for ML-based situations occurring in BMC Helix AIOps, the host name and situation severity are added to the incident notes.
To view these details, you must disable the Proactive Service Resolution solution, turn off and turn on the Incident Noise Reduction option, and enable the solution again in BMC Helix Intelligent Automation.
For more information, see Configuring-Proactive-Service-Resolution-for-incidents-in-BMC-Helix-ITSM.
View user name in BMC Helix Intelligent Automation solutions
When you view or modify the Proactive Service Resolution or Blackout Policy solutions, you can view the user name specified for connecting with the IT Service Management (ITSM) or trouble ticket management system. Use this information to identify the user account used for configuring the connection.
This capability is available only if you have connected with a cloud deployment of ITSM or trouble ticket management system.
For more information, see the following topics:
Enhancement to the Proactive Service Resolution for TMF621-compliant trouble ticket management systems
BMC Helix Intelligent Automation supports TMF621-compliant callback payload for receiving trouble ticket updates. This method is a standard way of connecting with the TMF621 trouble ticket management systems. The callback URL can also accept JWT tokens.
For more information, see Configuring-Proactive-Service-Resolution-for-TMF-compliant-trouble-tickets.
Improved user experience on the History page
You can perform the following actions on the History page:
- Copy the event ID by double-clicking it.
- View the Event ID column next to the Automation Policy column.
- Use the column selector to select the columns to be displayed on the History page.
For more information, see Viewing-automation-policy-runs-history.
View and edit published policies
Use the Edit option in the Actions menu to view and edit automation policies with the Published status. You no longer need to move a policy to the Draft status before editing it.
For more information, see Viewing-editing-and-copying-automation-policies.
Install and run on-premises connectors as non-root users
On Linux-based operating systems, non-root users can install, run, and perform any actions on the on-premises connectors. Root users can also install and run connector as a service for non-root users by providing the non-root user credentials.
For more information, see Connecting-with-automation-tools.
Connect with BMC Helix Automation Console to remediate vulnerabilities
BMC Helix Intelligent Automation connects with BMC Helix Automation Console (SaaS deployment only) to remediate vulnerability events. To remediate these events, you can use the Ansible connector to connect with the Ansible automation platform and run playbooks.
For more information, see Remediating-vulnerabilities-in-BMC-Helix-Automation-Console.
