Mapping a custom third-party application field with a BMC Helix Innovation Studio field, in BMC Helix iPaaS, powered by Jitterbit

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

To map a custom field in a third-party application with a BMC Helix Innovation Studio field

1. Log in to BMC Helix iPaaS and navigate to Integration Studio.
2. Select your organization and the environment in which you have imported the integration template.
3. Open the required project.
   For example, open the Sync BMC Helix ITSM incident and Atlassian Jira issue project.
4. On the Workflows tab, open the workflow for ticket creation from a third-party application to BMC Helix Innovation Studio.
   For example, open Jira Issue to MCSM Incident.
5. Under the main workflow, open the workflow that creates a record in BMC Helix Multi-Cloud Broker.
   For example, under the Jira Issue to MCSM Incident main workflow, open Create MCSM Incident.
6. Select the transformation that creates a BMC Helix Innovation Studio record from a third-party application ticket and click View/Edit.
   For example, in the Create MCSM Incident workflow, click the Jira Issue to Incident Create transformation.
7. In the Target section, click the settings icon  and then, click Refresh Schema, as shown in the following image:
   
   
   This action fetches the custom fields from the BMC Helix Innovation Studio record definition.
8. In the target schema, open the BMC Helix Innovation Studio custom field with which you want to map the custom field in Jira.
   For example, you open MCBIncCustomField.
9. Depending on whether the source and target applications use connectors or JSON objects, perform one of the following steps:
   • If the source application uses webhooks to pass information, perform the following steps to map the custom fields:

     1. To fetch the custom field data from the webhook request object for the third-party application, click the angle brackets icon <> and add a script. The webhook request object name is jsonObj.
        For example, add the following script to fetch the custom field from Jira:

        $jsonObj["issue"]["fields"]["customfield_10190"]

        The steps to fetch the custom field key from the third-party application ticket metadata change based on the third-party 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.

        c. Use the key from the metadata in the script in step 9.

   • If the source and target applications use connectors to pass information, perform the following steps to map the custom fields:
     1. Refresh the source and target schemas to update them with new custom fields.
     2. From the source section, drag the custom field to a field in the target section.

Where to go from here

Create a corresponding field in BMC Helix ITSM. For more information see, Creating and managing fields. 

Mapping-a-BMC-Helix-Innovation-Studio-field-with-a-BMC-Helix-ITSM-field