BMC Helix Multi-Cloud Service Management 20.02

BMC Helix Multi-Cloud Service Management is an add-on offering for Remedy IT Service Management Suite (Remedy ITSM Suite) and 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 17 Nov 2020

This section provides information about BMC Helix Multi-Cloud Service Management including urgent issues and documentation updates.

Tip

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

Related topics

Known-and-corrected-issues

Support-information

The following updates have been added since the release of the space:

Date	Release	Summary
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 Remedy ITSM Update the state of Azure alerts automatically from Remedy ITSM incidents
November 22, 2019	19.11	Enhancements: Consolidate incidents from Remedyforce to Remedy ITSM Share custom Remedy Action Request System form data by using the AR System connector Automatic status updates of Azure alerts through Remedy 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 Remedy ITSM incidents based on Azure Alerts Share activity notes between Remedy ITSM incident and Azure DevOps work item Share attachments associated with activity notes in Remedy ITSM incident with Jira Service Desk Map Jira, Jira Service Desk, and Azure DevOps custom fields with Remedy ITSM fields Update the status of Remedy 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 Platform 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 (ITSM) or BMC Helix IT Service Management (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 Remedy ITSM. Ticket consolidation across multiple Remedy ITSM instances. Support for attachments from Salesforce Service Cloud to Remedy ITSM. Collaborative, automated, incident brokering for multiple Remedy ITSM instances. Simplified user interface for BMC Helix Multi-Cloud Service Management configuration.
May 31, 2018	18.05	Enhancements: DevOps integration for multiple instances of Jira. Support for ticket brokering in BMC Helix Multi-Cloud Service Management without Smart IT. Ticket consolidation from Salesforce Service Cloud to Remedy ITSM.
Feb 28, 2018	18.02	Enhancements: Out of the box flows for Remedy 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.

Getting started See more		Performing preconfiguration tasks As a tenant administrator, perform the preconfiguration tasks before setting up BMC Helix Multi-Cloud Service Management. See more
Onboarding and implementing As a tenant administrator, set up an end-to-end integration between ITSM and a cloud service provider. See more		Configuring BMC Helix Multi-Cloud Service Management As a tenant administrator, set up BMC Helix Multi-Cloud Service Management features for your organization. See more

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.

Developer Community

Join discussions with peers and experts.

BMC Helix Community

Explore, 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

View the BMC Helix Multi-Cloud Service Management video playlist

Podcastshttp://digital.bmc.com/

Listen to experts in Digital Service Management.

Marketplacehttps://marketplace.bmc.com/

Find 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

FAQs

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

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

For incident brokering:

When a service desk agent adds a comment to the Remedy IT Service Management Suite (Remedy ITSM Suite) or BMC Helix ITSM incident in Smart IT and clicks Share with AWS/Salesforce, the comment is added to the vendor ticket.
When a field is updated in ITSM, BMC Helix Multi-Cloud Service Management updates the corresponding vendor ticket with a comment listing the field name with the new and existing values. BMC Helix Multi-Cloud Service Management 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 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 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 ITSM incident.
When an 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 ITSM change request or incident (in Smart IT) and clicks Share with Jira/CA Agile Central, the comment is added to the Jira/CA Agile Central issue.
When a developer adds a comment to a Jira issue or user story, the comment is added to the corresponding 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 ITSM incident fields.
Status changes to a vendor ticket are reflected as an activity note on the ITSM incident or change request.

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

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

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 Service Management 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 Service Management ships with a couple of OOTB 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 Service Management 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 Service Management 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 Service Management 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 Service Management. You can look at BMC.com and sign-up for free trials of BMC Integration Service. BMC Helix Multi-Cloud Service Management application is built using BMC Helix Multi-Cloud Service Management. If BMC Helix Multi-Cloud Service Management is the Remedy Action Request System platform and BMC Helix Multi-Cloud Service Management is ITSM.

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

Remedy with Smart IT

20.02