24.2 enhancements and patches

Review the BMC Helix AIOps enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

Version	SaaS	On Premises	Fixed issues	Updates and enhancements
24.2.02	✅️	✅️	Known-and-corrected-issues	None
24.2.01	✅️	✅️	Known-and-corrected-issues	updates
24.2	✅️	✅️	Known-and-corrected-issues	24.2.00 enhancements

For updates and enhancements in the previous release and its patches, see Release-notes-and-notices.

24.2.01

Reduce incident noise by consolidating incidents for ML-based situations

A single incident is created for an ML-based situation instead of multiple incidents in BMC Helix ITSM for each event in the situation. All events that are a part of the situation have the same incident ID as that of the situation. If an event is not part of a situation, an incident is created based on the existing behavior. This significantly reduces the number of incidents to be handled by the service desk agent, and especially during an event storm, thus leading to noise reduction and improved MTTR.

The incident contains the name of the impacted service, causal CI, the cross-launch URL to the situation, and event details, which are displayed in the work notes. This information in BMC Helix ITSM helps the service desk agent perform root cause analysis by viewing the situation details in the BMC Helix AIOps console.

If new events or situations are generated for the same causal CI, instead of new incidents, the existing unresolved incident is updated, and the details are added to the incident. When a situation is closed, the incident is resolved automatically.

For more information, see Investigating-ML-based-situations.

The consolidated incidents for ML-based situations are created by using the Proactive Service Resolution solution in BMC Helix Intelligent Automation. For more information, see Reduce incident noise by using Proactive Service Resolution for ML-based situations.

Situation with incidents_24102.png

24.2

Learn about the new features and enhancements in this release in the following video (4:41):

Watch the YouTube video about What's new in BMC Helix AIOps 24.2

Service blueprints: Add attributes as variables on other nodes in addition to the start node

While defining the filter criterion for a CI Kind, you can add CI attributes as variables to other nodes, in addition to the start node. You can add up to three variables in one service blueprint, including one mandatory variable for the start node. When you create a service by using the service blueprint, these variables provide additional filtering capability for CIs.

For more information, see Creating-service-blueprints.

Service blueprints: Specify the content requirement of a CI kind

While adding a filter criterion to a CI kind in a service blueprint, specify whether the content should exist for the CI kind by using the Required Content option. For the start node in a service blueprint containing multiple CI kinds, this option is selected by default, and the content must exist. For other nodes, it is optional.