Space banner This documentation supports the 18.05 version of Multi-Cloud Service Management.To view the documentation for the previous version, select 18.02 from the Product version menu.

Configuring processes

ProcessConfigGliff.png

A process uses actions to implement the business logic for a given business case that can be triggered by rules. When setting up BMC Helix Multi-Cloud Service Management, as a tenant administrator, you need to associate the appropriate profiles with the connector actions in the BMC Helix Multi-Cloud Service Management processes.


Note: Ensure that you have selected the features you want to enable and that  BMC Helix Multi-Cloud Service Management displays a list of connectors you need for the selected features.

To configure processes

  1. Click Copy and update processes in Innovation Studio.
    BMC Helix Multi-Cloud Service Management takes you to Innovation Studio for process configuration.

    ProcessList.PNG
  2. If you are integrating with multiple instances of Jira, create a copy of the Connector Process JIRA process for each instance and name them, Connector Process JIRA for <instance name>. 
    Complete all the following steps in this procedure, for each Jira instance.
    Note: Make a note of the instance name and use the same name for your Jira instance when     Configuring vendor data.
  3. Click the process you want to configure.

    processProfiles.png

  4. Click a connector of the process to associate the account that you added when configuring the corresponding connector in BMC Integration Studio.
    The Profile field on the Element PropertiesProcessAccount.PNG tab displays the accounts.
    For example, for the Connector Process AWS, associate the profile (account) that you added when you configured the AWS connector.
  5. Complete the account association for every connector in the process.

Process configuration fields

Process

Features using the process

Configuration

Connector Process Remedy ITSM

Incident brokering

  • Remedy Incident to AWS
  • Remedy Incident to Salesforce Service Cloud
  • Salesforce Service Cloud to Remedy Incident

DevOps integration

  • Manual association of Remedy Change with Jira Issues
  • Remedy Change to Jira Issue
  • Jira Issue to Remedy Change
  • Remedy Incident to Jira Issue
  • Jira Issue to Remedy Incident
  • Remedy Incident to Agile Central Issue

Service Dashboard

  • Service Dashboard
  • Service Notifications

For the connectors in each process, in the Profile field associate the account that you added when you configured the corresponding connector in BMC Integration Studio.

Connector Process AWS

Remedy Incident to AWS

For the connectors in each process, associate the account that you added when you configured the corresponding connector in BMC Integration Studio.

Connector Process Service Cloud

  • Remedy Incident to Salesforce Service Cloud
  • Salesforce Service Cloud to Remedy Incident

For the connectors in each process, associate the account that you added when you configured the corresponding connector in BMC Integration Studio.

Connector Process JIRA

  • Manual association of Remedy Change with Jira Issues
  • Remedy Change to Jira Issue
  • Jira Issue to Remedy Change
  • Remedy Incident to Jira Issue
  • Jira Issue to Remedy Incident

For the connectors in each process, associate the account that you added when you configured the corresponding connector in BMC Integration Studio.

If you are integrating with multiple Jira instances, complete the connector-profile association for all copies of the Connector Process JIRA process that you created.

Connector Process CA Agile Central

Remedy Incident to Agile Central Issue


For the connectors in each process, associate the account that you added when you configured the corresponding connector in BMC Integration Studio.

Where to go from here

Configuring-vendor-data

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*