This documentation supports the 21.3 and consecutive patch versions of BMC Helix Multi-Cloud Broker.

To view an earlier version, select the version from the Product version menu.

21.3 enhancements and patches

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

Patch versionSaaSOn premisesDefect fixesUpdates
21.3.10(tick)(tick)NoneNone
21.3.09(tick)
NoneNone
21.3.08(tick)
NoneNone
21.3.07(tick)
NoneNone
21.3.05(tick)(tick)Known and corrected issuesNone
21.3.04(tick)(tick)NoneUpdates in 21.3.04
21.3.02(tick)(tick)NoneNone
21.3.01

(tick) 


Known and corrected issuesNone
21.3(tick)
Known and corrected issues21.3 enhancements

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

(On premises only) Downloading and installing the patch

For instructions about downloading and installing the patch, see the following topics in the BMC Helix Innovation Suite Deployment online documentation:

  • Downloading the installation files Open link
  • Installing Open link

SaaS application patching

BMC applies patches during  Maintenance windows Open link .

21.3.04

Project variable changes in BMC Helix iPaaS, powered by Jitterbit templates

The following table lists the variable changes that are available in the templates:

Template name

Change

Reference

Sync_BMC_Helix_ITSM_incident_and_Microsoft_Azure_DevOps_work_item 

Out of the box, the default value of the BHIP_Vendor_API_Profile_Type variable is now set to BASIC.

Synchronizing incidents with Azure DevOps work items via BMC Helix iPaaS, powered by Jitterbit

Create_BMC_Helix_ITSM_incident_from_Microsoft_Azure_alert

The Reported_Source variable is added to the template. You can specify the source from where the incident is created.

Creating incidents from Azure Monitor alerts via BMC Helix iPaaS, powered by Jitterbit

21.3

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

 https://youtu.be/_ia7sDvSq2I

Integrate BMC Helix ITSM with third-party applications by using BMC Helix iPaaS templates developed in MuleSoft Anypoint Platform

Use BMC Helix iPaaS, powered by MuleSoft as the underlying integration technology to integrate BMC Helix ITSM with third-party applications.

MuleSoft Anypoint Platform is a data integration technology built to connect a variety of data resources and applications. Use the out-of-the-box connectors to connect your applications in cloud, on-premises, or hybrid environment. By using this technology, you can connect applications, data, and devices with reusable APIs.

Important

BMC aims to eventually transition the integration capabilities from BMC Helix Integration Service to more robust integration platforms like BMC Helix iPaaS, powered by Jitterbit and BMC Helix iPaaS, powered by MuleSoft.

List of out-of-the-box integration templates

You can use the following out-of-the-box integration templates to:

The following image illustrates how BMC Helix Multi-Cloud Broker has improved its integration offerings over the releases and the third-party applications it supports for integrations via BMC Helix iPaaS, powered by MuleSoft:

Integrate BMC Helix ITSM with new third-party applications by using BMC Helix iPaaS, powered by Jitterbit

You can integrate BMC Helix ITSM with the following new third-party applications through BMC Helix iPaaS, powered by Jitterbit:

Other enhancements in this release

The following enhancements are available in this release:

EnhancementReference

When you integrate a BMC Helix ITSM incident or change request with an Azure DevOps work item, you can:

  • synchronize attachments between the tickets
  • view the work item details in the corresponding incident or change request
Was this page helpful? Yes No Submitting... Thank you

Comments