Phased rolloutThis documentation supports the 21.02 version of BMC Helix Multi-Cloud Broker.To view an earlier version, select the version from the Product version menu.


BMC Helix Multi-Cloud Broker 21.02


BMC Helix Multi-Cloud Broker 21.02

BMC Helix Multi-Cloud Broker is an add-on offering for BMC Helix ITSM that enables organizations to effectively manage IT services in a hybrid, multi-provider environment. It provides out-of-the-box integrations to address advanced service management challenges related to cloud services and to enable DevOps teams to work seamlessly with multiple applications.

Release notes and notices Updated 11 Oct 2022

Learn what’s new or changed for BMC Helix Multi-Cloud Broker 21.02, including new features, urgent issues, documentation updates, and fixes or patches.

Tip

To stay informed of changes to this list, click the icon watch.pngon the top of this page.

Related topics

Known-and-corrected-issues

Support-informationBMC Helix Integration Service Release notes and notices


Date

Title

Summary

May 04, 2021

Enhancements available in this release:

To learn about product changes, see Product-announcements.

September 23, 2020

20.08 enhancements

Enhancements available in this release:

  • Create an incident in BMC Helix Remedyforce from a Remedy ITSM incident
  • Create an issue in Jira Service Desk from a Remedy ITSM incident
  • Create a known error in Remedy ITSM from a Jira issue
  • Support for data sync between a worklog item and feed item
  • Open Smart IT from vendor tickets
  • Revamped screens for work orders and incident in Remedy with Smart IT
  • Support for self-signed certificates by using the AR system connector
  • View additional information about failed transactions

February 21, 2020

20.02

Enhancements:

  • Automatic incident creation from IBM QRadar SIEM offenses
  • Automatic incident creation from TrueSight Operations Management events
  • Automatic change request creation and activity note sync from Azure DevOps
  • Automatic update of field values of mapped fields between Jira and ITSM 
  • Update the state of Azure alerts automatically from ITSM incidents

November 22, 2019

19.11

Enhancements:

  • Consolidate incidents from Remedyforce to ITSM
  • Share custom Remedy Action Request System form data by using the AR System connector
  • Automatic status updates of Azure alerts through ITSM
  • Enhancement to the custom field support for Jira and Jira Service Desk
  • Share activity notes and attachments by using Salesforce Chatter
  • Register a self-signed certificate for Jira connector

August 22, 2019

19.08

Enhancements:

  • Create ITSM incidents based on Azure Alerts
  • Share activity notes between ITSM incident and Azure DevOps work item
  • Share attachments associated with activity notes in ITSM incident with Jira Service Desk
  • Map Jira, Jira Service Desk, and Azure DevOps custom fields with ITSM fields
  • Update the status of ITSM incident from Jira or Jira Service Desk
  • Define CI priority to calculate risk of a change request
  • Updated BMC Helix Multi-Cloud Service Management application according to the latest BMC Helix Innovation Suite archetype

May 31, 2019

19.05

Enhancements:

  • DevOps integration for Azure DevOps Services
  • Enhanced Error Console for consolidated view of errors from BMC Helix Platform and BMC Helix Integration Service
  • Automatic risk calculation for change requests brokered from Atlassian JIRA Software issues
  • Ability to share attachments between Remedy IT Service Management Suite (Remedy ITSM Suite) or BMC Helix ITSM and JIRA
  • Introduction to self-help with guided assistance

February 28, 2019

19.02

Enhancements:

  • DevOps integration for Work Order records.
  • Manually restart failed brokering transactions.
  • Support for custom Salesforce Service Cloud objects in Incident records.

November 30, 2018

18.11

Enhancements:

  • DevOps integration with Jira includes support to create issues for Problem records.
  • Additional activity feed flows to include author name.
  • Support for custom fields in Incident and Change records.

September 14, 2018

18.08

Enhancements:

  • Ticket consolidation for Jira Service Desk to ITSM.
  • Ticket consolidation across multiple ITSM instances.
  • Support for attachments from Salesforce Service Cloud to ITSM.
  • Collaborative, automated, incident brokering for multiple ITSM instances.
  • Simplified user interface for BMC Helix Multi-Cloud Broker configuration.

May 31, 2018

18.05

Enhancements:

  • DevOps integration for multiple instances of Jira.
  • Support for ticket brokering in BMC Helix Multi-Cloud Broker without Smart IT.
  • Ticket consolidation from Salesforce Service Cloud to ITSM.


Feb 28, 2018

18.02

Enhancements:

  • Out of the box flows for ITSM.
  • Tailor out-of-the-box flows.
  • Track service targets and status of cloud service providers.
  • Custom connectors and flows for other third-party service providers.


Tip

Ready-made PDFs are available on the PDFs-and-videos. You can also create a custom PDF.

Click here to see the steps.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Performing preconfiguration tasks

As a tenant administrator, perform the preconfiguration tasks before setting up BMC Helix Multi-Cloud Broker.

Onboarding and implementing

As a tenant administrator, set up an end-to-end integration between BMC Helix ITSM and a cloud service provider.

Configuring BMC Helix Multi-Cloud Broker

As a tenant administrator, refer this section to learn about integrating with vendor applications by using BMC Helix iPaaS, powered by Jitterbit and BMC Helix Integration Service.

Administering

As a tenant administrator, assign user roles and permissions, and update configurations post upgrade.

Integrating

As a tenant administrator, integrate custom connectors, and perform custom integrations.

Troubleshooting

As a tenant administrator, resolve common issues or errors, review logs, or contact Support.

Subscribe

subscribe.png Sign up for a trial or log in.

Developer Community

communities.pngJoin discussions with peers and experts.

BMC Helix Community

CommunitiesExplore, talk, and learn about BMC Helix offerings.https://bmcsites.force.com/casemgmt/sc_CoveoSearch#t=All&sort=relevancy

Videoshttps://www.youtube.com/user/BMCSoftwareBMCtv/featured

videos.pngView the BMC Helix Multi-Cloud Broker video playlist

Podcastshttp://digital.bmc.com/

PodcastsListen to experts in Digital Service Management.

Marketplacehttps://marketplace.bmc.com/

MarketplaceFind apps, connectors, learning modules, and more.
PDFs

This topic describes and links to PDFs, videos and other documents that support this product release. If the ready-made PDFs of this space do not satisfy your requirements, you can export a custom PDF.

You must log in or register to view this page

Videos

The following list displays the topics that contain videos that supplement or replace the text-based documentation:

FAQs

This section contains a list of frequently asked questions and common use cases for BMC Helix Multi-Cloud Broker features.


How are activity notes and status updated in BMC Helix Multi-Cloud Broker?

For incident brokering:

  • When a service desk agent adds a comment to an incident in BMC Helix ITSM: Smart IT and clicks Share with AWS/Salesforce, the comment is added to the vendor ticket.
  • When a field is updated in BMC Helix ITSM, BMC Helix Multi-Cloud Broker updates the corresponding vendor ticket with a comment listing the field name with the new and existing values. BMC Helix Multi-Cloud Broker adds a comment only for those fields that are mapped when you specify technology provider and field mapping during Vendor data configuration.
  • Any updates to fields in the vendor ticket are reflected in the corresponding BMC Helix ITSM incident fields. This behavior applies to the fields that are mapped when you specify technology provider and field mapping during Vendor data configuration.
  • An BMC Helix ITSM incident is marked as resolved when the vendor ticket is closed based on the option you select when you specify technology provider and field mapping during Vendor data configuration. 
  • When a Case Comment is added to a Salesforce Service Cloud ticket, Smart IT displays the comment as an activity note for the corresponding incident.
  • Status changes to a vendor ticket are reflected as an activity note on the BMC Helix ITSMincident.
  • When an BMC Helix ITSM incident is Cancelled, Closed, or Resolved, the corresponding vendor ticket is Closed.

For DevOps integration:

  • When a service desk agent adds a comment to the BMC Helix ITSM change request or incident (in Smart IT) and clicks Share with Jira/CA Agile Central, the comment is added to the Jira Software or Rally Software (formerly, CA Agile Central) issue.
  • When a developer adds a comment to a Jira issue or user story, the comment is added to the corresponding BMC Helix ITSM change request or incident if the Viewable to all users option is selected in Jira.
  • Any updates to fields in the vendor ticket are reflected in the corresponding BMC Helix ITSM incident fields.
  • Status changes to a vendor ticket are reflected as an activity note on the BMC Helix ITSM incident or change request.

For more information, see the appropriate feature configuration at Configuring-BMC-Helix-Multi-Cloud-Broker.


What is the main difference between My Service Broker and BMC Helix Multi-Cloud Broker?

The scope of My IT Service Broker, which is now a part of BMC Digital Workplace (Advanced) is limited to brokering service requests whereas BMC Helix Multi-Cloud Broker is focused at brokering other ITSM objects like Incident, Change, among others. It is possible that both solutions may share some connectors provided with BMC Helix Integration Service, their purpose and solution goals remains completely different.


How much development effort does it take to create a new connector that is not OOTB?

The time required to create a new connector would depend on the third-party application you are trying to connect to and the capabilities you want to configure.

BMC Helix Multi-Cloud Broker ships with a couple of out-of-the-box flows for select vendors but there are many other connectors that are available with BMC Helix Integration Service. These connectors could be leveraged to build flows with non-OOTB vendors.

BMC provides a Connector builder that makes connector development easier. Two programming languages are supported to build the connector (broker): javascript and java. The Connector builder will help you to generate the skeleton of the connector codes. After it is generated, you need to implement the business logic to connect to the external application and pull and/or push data to it

Effort would also include getting insight about the external solution's APIs. If the vendor support REST API, it will be much easier.


We just bought a ticket broker tool from a BMC Partner (VIPCON). The Ticket Broker (BGI) will be used to sync incidents and changes between T-Systems cloud and us. How does BMC Helix Multi-Cloud Broker add-on differ from the ticket broker (BGI) of VIPCON? Up to now I think the only different is that the BMC Helix Multi-Cloud Broker add on is a cloud application and BGI is a on premise application. T-Systems use HP Service Manager 9.

Yes, some of our Remedy customers have implemented integration scenarios with different approach, incl. (but not limited to) partner solutions. As our customers move more and more to a multi-provider / multi-cloud approach to IT sourcing and have an increased need to bring DevOps and ITSM solutions closer together, BMC plans to support these uses cases with this OOTB service offering. With a BMC provided solution, we can integrate these use cases better into the user experience. 


Is the BMC Helix Multi-Cloud Broker add-on the same as the project name "Panama" launched two years ago?

Panama is now generally available from BMC and is called BMC Helix Multi-Cloud Broker. You can look at BMC.com and sign-up for free trials of BMC Integration Service. BMC Helix Multi-Cloud Broker application is built using BMC Helix Multi-Cloud Broker. If BMC Helix Multi-Cloud Broker is the Remedy Action Request System platform and BMC Helix Multi-Cloud Broker is ITSM. 

Related topics

Protection against CSRF attack vulnerabilityBMC Helix Platform Product SupportBMC Helix Platform Knowledge Base

Related spaces

BMC Helix

Helix Chatbot

Helix Business Workflows

Digital Workplace Advanced

Remedy Single Sign-On

18.08 18.11 19.02 19.05 19.08 19.11 20.02 20.08

Remedy IT Service Management Suite

20.02

Remedy with Smart IT

20.02