22.1 enhancements and patches

Review the BMC Helix Multi-Cloud Broker 22.1 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
22.1.07			None	None
22.1.06			None	Updates in 22.1.06
22.1.05			None	Updates in 22.1.05
22.1.04			Known and corrected issues	Updates in 22.1.04
22.1.02			None	None
22.1.01			Known and corrected issues	Updates in 22.1.01
22.1			Known and corrected issues	22.1 enhancements

For a list of recent updates and enhancements across multiple versions, see Release notes and notices.

BMC applies upgrades as described in  BMC Helix Upgrade policy . BMC applies upgrades and patches during Maintenance windows . 

(On premises only) Downloading and installing the patch

SaaS application patching

BMC applies patches during  Maintenance windows .

22.1.07

BMC Helix Multi-Cloud Broker is a maintenance patch only.

22.1.06

Integrate BMC Helix ITSM work orders with Jira

Integrate BMC Helix ITSM work orders with Jira to additionally synchronize comments and status details between BMC Helix ITSM work order records and Jira issues so both records include the latest information. 

For more information about configuring the integration template via BMC Helix Integration Service, see Synchronizing work orders with Jira issues via BMC Helix Integration Service.

Ticket brokering issues fixed in the Synchronize BMC Helix ITSM incidents with PagerDuty incidents template

The Synchronize BMC Helix ITSM incidents with PagerDuty incidents template has been updated to fix ticket brokering issues.

For more information about configuring the integration template, see Synchronizing BMC Helix ITSM incidents with PagerDuty incidents via BMC Helix iPaaS, powered by Jitterbit.

22.1.05

Integrate BMC Helix ITSM work orders, known errors, and problem records with on-premises instances of Jira. Update the JIRA_INSTANCE_TYPE project variable in the integration template to define if the Jira instance is on-premises or in the cloud.

For more information about configuring the integration templates, see:

• Synchronizing work orders with Jira issues via BMC Helix iPaaS, powered by Jitterbit
• Creating known errors from Jira issues via BMC Helix iPaaS, powered by Jitterbit
• Creating Jira issues from problem records via BMC Helix iPaaS, powered by Jitterbit

22.1.04

Integrate BMC Helix ITSM incidents and change requests with on-premises instances of Jira. Update the JIRA_INSTANCE_TYPE project variable in the integration template to define if the Jira instance is on-premises or in the cloud.

For more information about configuring the integration templates, see:

• Synchronizing incidents with Jira issues via BMC Helix iPaaS, powered by Jitterbit
• Synchronizing change requests with Jira issues via BMC Helix iPaaS, powered by Jitterbit

22.1.02

BMC Helix Multi-Cloud Broker 22.1.02 is a maintenance patch only.

22.1.01

Integration templates via BMC Helix iPaaS, powered by Jitterbit

Synchronize BMC Helix ITSM change requests with ALM Octane entities

Integrate BMC Helix ITSM with ALM Octane to synchronize ALM Octane entities with BMC Helix ITSM change requests. This integration enables agents to track and manage tickets in both applications, increasing data visibility and providing more effective control of any operations. With this integration, new tickets and ticket updates are automatically synchronized between BMC Helix ITSM and ALM Octane.

Learn more about this integration in Synchronizing change requests with ALM Octane entities via BMC Helix iPaaS, powered by Jitterbit.

Synchronize BMC Helix ITSM incidents with PagerDuty incidents

Integrate BMC Helix ITSM with PagerDuty by using the integration template available via BMC Helix iPaaS, powered by Jitterbit. This integration allows automatically synchronizing new incidents and incident updates between BMC Helix ITSM and PagerDuty. Automatic incident creation and data synchronization between the applications enable teams to collaborate faster and increase ticket resolution rate.

For more information about this integration, see Synchronizing BMC Helix ITSM incidents with PagerDuty incidents via BMC Helix iPaaS, powered by Jitterbit.

Create BMC Helix ITSM incidents from SolarWinds alerts

Integrate BMC Helix ITSM with SolarWinds to create BMC Helix ITSM incidents from SolarWinds alerts. With this integration, SolarWinds alerts are automatically converted into BMC Helix ITSM incidents to provide visibility for network monitoring events. This integration supports the following incident creation scenarios:

• Creates an incident per alert that is generated in SolarWinds
• Creates an incident per server that triggers an alert in SolarWinds

For more information, see Creating incidents from SolarWinds alerts via BMC Helix iPaaS, powered by Jitterbit.

22.1

The following video (2:55) provides an overview of the key features in the BMC Helix Multi-Cloud Broker version 22.1:

https://youtu.be/dEh20Tc8esI

Integration templates via BMC Helix iPaaS, powered by Jitterbit

Synchronize BMC Helix ITSM incidents with ALM Octane entities

By integrating BMC Helix ITSM with ALM Octane, you can synchronize tickets in the two applications. With this integration, agents can easily monitor the tickets regardless of the application in they are created. When an incident is created in BMC Helix ITSM, a corresponding entity is created in ALM Octane. Similarly, when an entity is created in ALM Octane, a corresponding incident is created in BMC Helix ITSM. You can also synchronize data updates between the two tickets.

Learn more about this integration in Synchronizing incidents with ALM Octane entities via BMC Helix iPaaS, powered by Jitterbit.

Create BMC Helix ITSM incidents from Dynatrace problems

By integrating BMC Helix ITSM with Dynatrace, you can create BMC Helix ITSM incidents from Dynatrace problems. With this integration, agents can monitor the Dynatrace problems directly in BMC Helix ITSM. You can also synchronize data updates between the two tickets. 

Learn more about this integration in Creating incidents from Dynatrace problems via BMC Helix iPaaS, powered by Jitterbit.

What else changed in this release

The following enhancements are also available in this release: