This documentation supports the 25.1 and consecutive patch versions of BMC Helix Multi-Cloud Broker.To view an earlier version, select the version from the Product version menu.

Mapping a custom third-party application field with a BMC Helix Innovation Studio field, in MuleSoft Anypoint platform


After you add a field in BMC Helix Innovation Studio that corresponds to the custom field in your vendor application, you must map the fields with each other to ensure that the field data is passed from the vendor application to BMC Helix Innovation Studio.

To map a custom field in a vendor application with a BMC Helix Innovation Studio field

  1. Log in to MuleSoft Anypoint Studio.
  2. Open the integration template for which you want to map the custom fields.
  3. Select src/main/mule > vendorBusinessLogic.xml.
  4. Open the MCB Create Operation Payload transformation.
    21.3_Select MCB Create Operation Payload.png
  5. To map the custom fields, perform any of the following actions:
    • If the custom fields from the vendor application and BMC Helix Innovation Studio are displayed in the Input and Output sections, drag the custom field from the Input section to the Output section.
    • If the custom fields are not displayed in the Input and Output sections, perform the following steps:
      1. To display the custom fields in the Output section, in the MCB Create Record Data operation, click Refresh Metadata.
      2. In the MCB Create Operation Payload, perform the following steps:
        1. In the Output section, right click on the custom field from BMC Helix Innovation Studio that you want to map.
        2. Click Edit field assignment.
        3. In the text box, enter the custom field key from the vendor application in the following format:
          payload.fields.customfieldname
          Get the key of the custom field from the vendor metadata. 

          Example

          The steps to fetch the custom field key from the vendor ticket metadata change based on the vendor application.

          For example, to fetch the customfield_10190 key from Jira, perform the following steps:

          a. Log in to Jira.

          b. In the following URL, change the project key and find the custom field key from the metadata displayed:
          https://multi-cloud.atlassian.net/rest/api/3/issue/createmeta?projectKeys=MC&expand=projects.issuetypes.fields

          Refer to this topic for more details about fetching field metadata from Jira.

        4. Click Finish.
          The custom fields that you mapped are displayed in the Output Payload section.

          21.3_Output Payload script.png

You can perform these steps to update the BMC Helix ITSM tickets. In Step 5a, select a transformation that updates a ticket; for example, MCB Update Operation Payload

 

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