24.2 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.2.02
Root cause details updated in the incident created for a situation
If the root cause event is updated for an ML-based situation in BMC Helix AIOps, the configuration item (CI) details are updated in the Notes field of the incident created for the situation in BMC Helix ITSM. This update ensures that the latest root cause details are available for service desk agents to troubleshoot the issue and remediate it faster.
For more information, see Overview-of-Proactive-Service-Resolution and Configuring-Proactive-Service-Resolution-for-incidents.
Automatic deletion of the blackout policy based on the change request status
If a change request in BMC Helix ITSM is marked as Cancelled, Pending, or Completed during the blackout period, the corresponding blackout policy is deleted from BMC Helix Operations Management. To verify whether the policy is deleted, view the status of the Delete Blackout Policy automation policy on the History page.
When the status of the change request changes to Closed, no related automation policies are run in BMC Helix Intelligent Automation.
For more information, see Configuring-the-blackout-policy-solution.
24.2.01
Reduce incident noise by using Proactive Service Resolution for ML-based situations
When you enable the Incident Noise Reduction option while configuring Proactive Service Resolution, a single consolidated incident is automatically created for an ML-based situation in BMC Helix AIOps instead of multiple incidents for all the qualifying events that form the situation. The same incident ID is shown against the situation and all events in the situation. The incident is enriched with the causal CI, impacted service name, and details of the qualifying events. It also includes a URL to the situation to help the service desk agent investigate the situation further in the BMC Helix AIOps console. For more information, see Reduce incident noise by consolidating incidents for ML-based situations.
Earlier, even if multiple events are correlated into a situation, an incident would be created for each event. This would create a huge number of similar incidents in the IT service management system, which would lead to unnecessary noise, service desk fatigue, and probable system failures. The consolidated incident creation significantly reduces the incident noise and improves mean-time-to-resolution (MTTR).
For more information, see Configuring-Proactive-Service-Resolution-for-incidents.
24.2
Ability to recreate BMC Helix ITSM webhooks with tenant URLs for Proactive Service Resolution and Blackout Policy solutions
When you configure Proactive Service Resolution or Blackout Policy solutions for BMC Helix ITSM (only for cloud deployments), webhooks are created in BMC Helix ITSM. Before this release, the callback URL in the webhook contained ingress URLs. If your BMC Helix tenant URL changes for any reason, the URL does not get updated in the webhooks. In such cases, the callback mechanism supported by the webhooks fails, and even if incidents are created successfully, information events are not generated. When you modify the solution, a Recreate Webhook option is available, which creates the webhooks for the solution again with the updated tenant URLs. This option is not displayed if you are configuring these solutions for the first time.
For more information, see Configuring-Proactive-Service-Resolution-for-incidents and Configuring-the-blackout-policy-solution.
