23.1 enhancements and patches

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

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.1.02

Multiple and complex trigger conditions in Proactive Service Resolution

Administrators can specify multiple and complex trigger conditions in the Predefined Policy for Incident policy that is created in BMC Helix Operations Management when Proactive Service Resolution is configured. The conditions are displayed in the solution configuration in BMC Helix Intelligent Automation. This gives administrators the flexibility to configure Proactive Service Resolution with as many permutations and combinations as required.

For more information, see Configuring-Proactive-Service-Resolution-for-incidents or Configuring-Proactive-Service-Resolution-for-TMF-compliant-trouble-tickets. 

Information events for automation policies

Every time a policy runs in BMC Helix Intelligent Automation, an information event (AUTOMATION_STATUS_EV class) is generated in BMC Helix Operations Management. The Generate Information Event on execution option is available while creating a policy that gives you the choice to not generate information events and thereby, reduce event noise. Learn more about the impact before clearing the check box. For more information, see Creating-automation-policies. 

Additional options for specifying trigger conditions while creating automation policies

While creating automation policies, you can use any of the following supported operators (case-sensitive): 

• Begins With
• Contains
• Does not contain

You can create a policy with complex trigger conditions, which allows you to create a single policy that can match and remediate multiple events. A minimum of three characters (maximum 99 characters) are required for using these options. 

For more information, see Creating-automation-policies. 

23.1.01

Ability to create an incident manually by using Proactive Service Resolution

When Proactive Service Resolution solution is enabled, BMC Helix Operations Management and BMC Helix AIOps operators have the option to manually create an incident in BMC Helix ITSM for open events. Typically, when Proactive Service Resolution is enabled, incidents are created automatically in BMC Helix ITSM. However, if an incident is not get created for any reason (for example, the Proactive Service Resolution is unavailable), operators can manually create an incident from the event operations menu. Currently, you can create an incident only in BMC Helix ITSM. 

For more information, see Configuring-Proactive-Service-Resolution-for-incidents. 

23.1

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

https://youtu.be/xPepP84bRq0

Create blackout policies in BMC Helix Operations management based on change requests

BMC Helix Intelligent Automation offers a solution that automatically creates a blackout policy in BMC Helix Operations Management based on a change request in BMC Helix ITSM.

Blackout policies enable you to suppress unwanted events or ignore events for a specific time period. With the automated solution, administrators can save time and effort that would be required to manually create and maintain blackout policies in BMC Helix Operations Management. When a change request status is updated (Completed, Pending, or Cancelled), BMC Helix Intelligent Automation deletes the blackout policy.

For more information, see Enabling-the-solution-for-blackout-policies.

Support for multiple functions in Proactive Service Resolution

Specify multiple functions to transform event data while configuring field mappings in Proactive Service Resolution. For example, you might require more than one function when you want to pass only a part of the message in the incoming event to appear as meaningful text in the Description field of a trouble ticket. You can specify multiple functions such as substring, substring_after, substring_before, concat, and so on that transform data. When an event occurs, the event data gets processed depending on the specified functions. 

You can use multiple functions while configuring event to incident or incident to information event field mappings. For more information, see Configuring-Proactive-Service-Resolution-for-TMF-compliant-trouble-tickets or Configuring-Proactive-Service-Resolution-for-incidents.

Audit report in BMC Helix Dashboards

As administrators, you can get a holistic view of the activities performed in the product in the BMC Helix Portal Audit dashboard. You can view an audit report for connectors, plugins, and automation policies for each user. For more information, see BMC Helix Portal Audit dashboard in the BMC Helix Dashboards documentation.

By default, audit records are stored for 7 days. For more information about retaining audit records for a longer period, see Viewing audit records in the BMC Helix Portal documentation. 

View in-app notifications

In-app notifications inform you about the actions completed in the application. In-app notifications are displayed for any updates made to the following entities:

• Connectors and plugin keys
• Automation requests
• Automation policies

For more information, see Accessing-and-navigating-the-BMC-Helix-Intelligent-Automation-console.