23.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.
23.4.02
Input parameters not mandatory for TrueSight Orchestration actions
While adding TrueSight Orchestration actions to an automation policy, you can skip the Input Parameters field. This is helpful if you want to add query-based workflows, which do not need any input to run successfully.
For more information, see Executing-a-workflow.
Improved search functionality for the Requests, Policies, and History pages
BMC Helix Intelligent Automation starts searching for records on the Requests, Policies, and History pages after 4 characters are added to the search field. This behavior optimizes the application's performance.
For more information, see the following topics:
- Viewing-automation-requests
- Viewing-editing-and-copying-automation-policies
- Viewing-automation-policy-runs-history
Observability and AIOps use case
Take advantage of the centralized data lake to observe the data ingested from multiple sources and the power of AI/ML event correlation to streamline root cause diagnostics and isolation. Enable automated remediation to fix recurring problems faster.
For more information, see Diagnosing-and-fixing-problems-faster.
23.4.01
Dynamically search for Ansible Tower job templates online
While creating an automation policy by using Ansible Tower actions, if the action is not listed in the available actions list, you can search for it on the Ansible Tower application by using the Search Online option. By default, this option is disabled.
For more information, see Restarting-PATROL-Agent-on-a-server.
23.4
Learn about the new features and enhancements in this release in the following video (2:00):
Watch the YouTube video about What's new in BMC Helix Intelligent Automation 23.4
Reduce event noise created by information events for incidents created in BMC Helix ITSM
When you configure Proactive Service Resolution, a webhook is created in BMC Helix ITSM. Every time an incident is created or updated in BMC Helix ITSM, this webhook sends the information events to BMC Helix Operations Management. If incidents are created or updated manually or by using any other mechanism, the webhook sends notifications about those events too, thus creating event noise. To reduce this event noise, the webhook qualification is enhanced to send events for incidents created via Proactive Service Resolution only. If you are already using Proactive Service Resolution for automated incident management, you should manually update the Qualification field in the webhook.
For more information, see Configuring-Proactive-Service-Resolution-for-incidents.
Mark automation policy runs as failed
A cleanup job that runs in the background identifies automation policy runs that are in a Running state for more than two days and marks them as Failed on the History page. This helps in cleaning up the History page and keeping it up-to-date.
For more information, see Viewing-automation-policy-runs-history.
