Synchronizing ServiceNow change requests with BMC Helix ITSM change requests by using Jitterbit Harmony

BMC Helix iPaaS, powered by Jitterbit provides a pre-built integration template that enables you to synchronize BMC Helix ITSM change requests with ServiceNow change requests. To use the integration template with the values defined out of the box, you update the project variables with details of your systems and deploy the integration template. 

The template provides the following capabilities: 

BMC Helix ITSM to ServiceNow data flow

The following image gives an overview of the data flow for creating a ServiceNow change request from a BMC Helix ITSM change request:

ServiceNow to BMC Helix ITSM data flow

The following image gives an overview of the data flow for creating a BMC Helix ITSM change request from a ServiceNow change request:

Before you begin

You require the following items to successfully set up and use this integration: 

Task 1: To download and import the integration template project file

1. Download the Sync ServiceNow Change with BMC Helix ITSM Update 2022-07-01  to your system.
   This file contains the BMC Helix iPaaS Cloud Studio project BiDirectional_Sync_ServiceNow_Change_With_BMC_Helix_ITSM_Change_Request.
   

   Important

   Your ability to access product pages on the EPD website is determined by the license your company purchased.

2. As a developer, log in to BMC Helix iPaaS and navigate to the Cloud Studio.

3. On the projects page, click Import.

4. Click Browse and then select the Sync ServiceNow Change with BMC Helix ITSM Update.json file downloaded. 

   The Project Name and Organization fields are automatically populated depending on the values you defined. 
5. From the Environment list, select the environment to which you want to import this integration template, and click Import.
   The project opens after the integration template is imported. 

6. To open the project file at a later time, select the environment where the integration templates are available, select the BiDirectional_Sync_ServiceNow_Change_With_BMC_Helix_ITSM_Change_Request project, and click View/Edit.

Task 2: To update the project variables for the integration template

1. Next to the Environment name, click the ellipses ... and select Project Variables.
2. Update the following project variables:

   • Access points and authentication details for ServiceNow, BMC Helix ITSM, and BMC Helix iPaaS applications

     Project variable	Action
     BMC Helix ITSM
     ITSM_Company	Enter a valid BMC Helix ITSM company for which the change request must be created; for example, Apex Global.
     ITSM_Endpoint	Enter the BMC Helix ITSM host URL.
     ITSM_CR_URL	Enter the BMC Helix ITSM change request URL that you want to display in the corresponding ServiceNow change record.
     ITSM_Midtier_URL	Enter the URL of the Mid Tier instance that you are using.
     ITSM_User	Enter the user ID to access BMC Helix ITSM.
     ITSM_Password	Enter the password for the user to access BMC Helix ITSM.
     ITSM_Service_Type	Enter a valid BMC Helix ITSM Service Type. You can set the following values for this variable: User Service Restoration User Service Request Infrastructure Restoration Infrastructure Event Security Problem
     ITSM_Webhook_Name	Enter a name for the webhook that is created in the BMC Helix ITSM instance. By default, this value is set to BHIP_Webhook.
     ServiceNow
     ServiceNow_Endpoint	Enter the URL of the ServiceNow instance.
     SNOW_User	Enter the User ID to access ServiceNow.
     ServiceNow_Password	Enter the password of the user to access ServiceNow.
     ServiceNow_Client_Id	Enter the OAUTH API endpoint ID generated in ServiceNow.
     ServiceNow_Client_Secret	Enter the OAUTH API endpoint client secret generated in ServiceNow.
     ServiceNow_Reference_Field1	Enter the name of a valid ServiceNow field to store the BMC Helix ITSM change request URL. We recommend that you set this value to correlation_display.
     ServiceNow_Reference_Field2	Enter the name of a valid ServiceNow field to populate the corresponding ITSM change number. We recommend that you set this value to correlation_id.
     ServiceNow_Webhook_APIKEY	Enter the ServiceNow system property that has apikey for the BMC Helix iPaaS APIKEY authentication profile.
     ServiceNow_Webhook_Basic_User	Enter the ServiceNow system property name to store BMC Helix iPaaS BASIC authentication user name.
     ServiceNow_Webhook_Basic_Password	Enter the ServiceNow system property name to store BMC Helix iPaaS BASIC authentication password.
     ServiceNow_Webhook_Business_Rule_Name	Enter the name of the business rule to be created for the ServiceNow Webhook configuration.
     ServiceNow_Webhook_Property_Name	Enter the name of the ServiceNow system property that stores the BMC Helix iPaaS integration API.
     BMC Helix iPaaS
     BHIP_Url	Enter the URL to access BMC Helix iPaaS.
     BHIP_User	Enter the user ID to access BMC Helix iPaaS.
     BHIP_User_Password	Enter the password of the user to access BMC Helix iPaaS.

   • Webhook API variables

     Project variables	Action
     BHIP_API_User_Roles	Enter comma-separated values of the user roles assigned for the BMC Helix iPaaS API. Only a user with these roles can access the APIs. Leave this value blank to restrict access only to administrators.
     BHIP_API_Name_Suffix	Enter a suffix to be added to the name of the Webhook API that is created in BMC Helix iPaaS to handle requests from BMC Helix ITSM and ServiceNow.
     BHIP_API_Response_Type_SNOW	Enter the REST API response type used by the Webhook API to handle requests from ServiceNow. This value is added in the BMC Helix iPaaS Jitterbit API.  By default, the value is set to VARIABLE.
     BHIP_API_Response_Type_ITSM	Enter the REST API response type used by the Webhook API to handle requests from BMC Helix ITSM. This value is added in the BMC Helix iPaaS Jitterbit API.  By default, the value is set to VARIABLE.
     BHIP_API_Security_Profile_ApiKey_Key_Name_SNOW	For security profile type APIKEY, enter the name of the APIKEY to be used for the security profile. The Jitterbit API and the Webhook API use this APIKEY for authentication while accessing ServiceNow.
     BHIP_API_Security_Profile_ApiKey_Key_Name_ITSM	For security profile type APIKEY, enter the name of the APIKEY to be used for the security profile. The Jitterbit API and the Webhook API use this APIKEY for authentication while accessing BMC Helix ITSM.
     BHIP_API_Security_Profile_BASIC_Auth_Username_SNOW	For security profile type BASIC, enter the user name to be used to create the ServiceNow security profile. The Jitterbit API and the Webhook API use this user name for authentication while accessing ServiceNow.
     BHIP_API_Security_Profile_BASIC_Auth_Password_SNOW	For security profile type BASIC, enter the password for the ServiceNow security profile created.  The Jitterbit API and the Webhook API use this password for authentication while accessing ServiceNow.
     BHIP_API_Security_Profile_BASIC_Auth_Username_ITSM	For security profile type BASIC, enter the user name to be used to create the BMC Helix ITSM security profile. The Jitterbit API and the Webhook API use this user name for authentication while accessing BMC Helix ITSM.
     BHIP_API_Security_Profile_BASIC_Auth_Password_ITSM	For security profile type BASIC, enter the password for the BMC Helix ITSM security profile created. The Jitterbit API and the Webhook API use this password for authentication while accessing BMC Helix ITSM.
     BHIP_API_TimeOut	Enter a value, in seconds, for an API timeout. The minimum value must range between 30 and 180. By default, the value is set to 90.
     BHIP_Webhook_Security_Profile_Type	Enter a security profile type. Webhook uses the security profile to call the BMC Helix iPaaS API. The default value is BASIC.
     BHIP_API_Security_Profile_Type_SNOW	Enter a security profile type. You can set the following values for this variable: BASIC APIKEY ANONYMOUS The default value is BASIC. Use comma-separated values to specify multiple security profile types. Security Profile Type defines the authentication type to be used by the Webhook API while accessing ServiceNow. This value is added in the BMC Helix iPaaS Jitterbit API.
     BHIP_API_Security_Profile_Type_ITSM	Enter a security profile type.  You can set the following values for this variable: BASIC APIKEY ANONYMOUS The default value is BASIC. A security profile type defines the authentication type to be used by the Webhook API while accessing BMC Helix ITSM. This value is added in the BMC Helix iPaaS Jitterbit API.

   • Email notification configurations

     Project variable	Action
     BHIP_SMTP_Hostname	Enter the SMTP host details for email configuration.
     BHIP_To_Email_Address	Enter the email address to which you want to send the notification emails.
     BHIP_From_Email_Address	Enter the email address from which the notification emails must be sent.
     BHIP_Email_Subject	Enter the default subject line for the notification email.
     BHIP_Email_Enabled	To disable email notifications, change the default value to false. By default, the value is set to true.
     BHIP_Email_On_Success	To disable email notifications for successful operations, set the value to false. By default, this value is set to true.
     BHIP_Email_On_Error	To disable email notifications for errors in workflows, set the value to false. By default, this value is set to true.

(Optional) Task 3: To review and update out-of-the-box field mappings

Out-of-the-box field mappings are defined in the transformation elements of the Process Source Payload And Preparing Payload For Create and Update Change Request Actions in Service Now and ITSM TO SNOW - Create New Change Request in ServiceNow operations in the Sync ITSM to ServiceNow Change Request workflow. For additional information about the workflow, see Workflows included in the integration template.

The following out-of-the-box fields are mapped in the Prepare ServiceNow Request transformation element for the ITSM TO SNOW - Create New Change Request in ServiceNow operation:

You can edit the ServiceNow to BMC Helix ITSM field mappings provided by the integration template. To do so, you need to update the transformation element in the workflow and map the fields. 

To update out-of-the-box field mappings

1. Open the Sync ITSM to ServiceNow Change Request project.
2. On the Workflows tab, in the Sync ITSM to ServiceNow Change Request workflow, scroll to the Process Source Payload And Preparing Payload For Create and Update Change Request Actions in Service Now operation.
3. Click the Mapping Response transformation element, and select View/Edit:
4. In the Target pane, from the View menu, select Mapped.
5. On the Variables tab, click Use Variables.
6. From the variable list, drag the variable to the field mapping you want to update in the Mappings section.

7. Click Return to Workflow .

   Important

   If the integration template is already deployed, you must deploy it again after you make changes to the mappings.

   For more information about deploying the project, see Task 4: To deploy and enable the project.

Task 4: To deploy and enable the project

After you enable the integration, when a change request is created in BMC Helix ITSM, a corresponding change request is created in ServiceNow, and the converse is true. Any updates made to the BMC Helix ITSM change request are synced with the ServiceNow change request, and the converse is true. The Change Request Number is synced to the Correlation Id field in ServiceNow, and the ServiceNow change ID is synced to the Vendor Ticket No field in BMC Helix ITSM.

(Optional) Task 5: To set the time for API debug mode

By default, the debug mode is set to 2 hours after you run the integration. Debug logs are updated for the time set for the debug mode. To increase the debug mode for a longer period of time, perform the following steps:

1. In BMC Helix iPaaS, select API Manager > My APIs.
2. Open the required API.
3. Select Enable Debug Mode Until: and set it for the required date and time.
4. Save and publish the API.

(Optional) Task 6: To update the default trigger conditions for the Sync ITSM to ServiceNow change project

You can update the trigger condition defined out of the box for the integration by updating the Webhook configuration added to BMC Helix ITSM. 

To update or define filters for the trigger condition

1. As an administrator, log in to Mid Tier.
2. In the Basic Information section, enter the value of the Source_Webhook_Name project variable in Description and click Search. 
   The following webhooks are displayed:

   • CHG:ChangeInterface_Create—Creates a webhook in BMC Helix ITSM

   • CHG:ChangeInterface—Updates a webhook in BMC Helix ITSM

   • CHG:WorkLog—Creates a worklog in BMC Helix ITSM

3. Click the configuration to update the trigger condition for that event. 
4. In the Event Information section, you can select the Events, or in Qualification, enter the qualification to trigger the Webhook configuration. For example, you can set the qualification to 'Status' != "Closed".

(Optional) Task 7: To map custom BMC Helix ITSM fields to existing ServiceNow fields

You can map custom fields created in BMC Helix ITSM to existing ServiceNow fields by updating the mappings in the integration template. If you delete a custom field that is not mapped to a mandatory field in ServiceNow, the integration continues to work. However, we recommend that you delete the field mappings from the integration template project.

To add the field mapping for a custom field created in ServiceNow

1. Log in to BMC Helix iPaaS as a developer and navigate to the Cloud Studio.

2. Select the environment where the integration templates are available.

3. Select the Sync ITSM to ServiceNow Change project and click View/Edit.
4. Expand the ITSM Change to SNOW Change workflow.
5. Refresh the schema to include the custom fields added to ServiceNow.
   1. Select the Query ITSM change element in the Process Source Payload And Preparing Payload For Create and Update Change Actions in Service Now operation and click View/Edit.
   2. Click Step 1 in the query, and then click Refresh.
   3. From the Select an Object list, select the change request table, and click Next.
   4. On Step 2, to ensure that your custom field is added to the list of change request fields, click Refresh.
   5. When the change request field table is loaded, to select any new fields added to the BMC Helix ITSM change request table, clear and then select SELECT ALL. 
   6. Click Next, and then on Step 3, click Finished. 
6. To create and update mappings for the custom field in other transformations, create a global variable for the custom field.
   1. Click the Mapping Response transformation element in the Process Source Payload And Preparing Payload For Create and Update Change Actions in Service Now operation, and click View/Edit.
   2. In the Target pane, click Settings and select Edit schema.
   3. To add the field mapping for the custom field, click +Add Field.
   4. Scroll to the bottom of the field list, enter the field name and select the Type, and then click Save Changes.
   5. To create and update the mapping for the custom field in other transformations, in the Target pane, click the script icon  next to the new field and add a global variable entry for the field. For example, add the following global variable to the script:
      $custom_field = OUTPUT$chaneg$Entity.u_custom_field$;
7. Follow these steps to map the custom field to an existing ServiceNow field:
   1. Click the Prepare ServiceNow Request Payload transformation element in the ITSM TO SNOW - Create New Change in ServiceNow operation and select View/Edit.
   2. On the  Variables  tab, click Use Variable .
   3. From the variable list, drag the global variable you created for your custom field, and map it to the ServiceNow field in the Target pane.
   4. Click Return to Workflow.
8. Deploy the project.
   For more information about deploying the project, see Task 4: To deploy and enable the project.

9. If you delete the custom field from BMC Helix ITSM, you must delete the custom field mapping in the integration template.
   To delete the custom field mappings, perform the following steps:

   1. Refresh the schema in the Query ITSM change element in the Process Source Payload And Preparing Payload For Create and Update Change Actions in Service Now operation.
   2. Remove the global variable created in the Mapping Response transformation element in the Process Source Payload And Preparing Payload For Create and Update Change Actions in Service Now operation.
   3. Remove the field mappings defined for the custom field in the Prepare ServiceNow Request Payload transformation element in the ITSM TO SNOW - Create New Change in ServiceNow operation and the Mapping ServiceNow Change Response transformation element of the Update ServiceNow Change operation.
   4. Deploy the integration.
      For more information about deploying the project, see Task 4: To deploy and enable the project.

Workflows included in the integration template

The following workflows are defined as a part of the integration template. Refer to the following details for an overview of the tasks defined in the workflow operations and configurations defined within each workflow.

Enable Integration

This workflow defines the operations to control the sync between BMC Helix ITSM and ServiceNow. The following operations are included in this workflow:

BHIP Operations

This workflow defines the operations required to enable the integration after all the required project configurations are completed. The following operations are included in this workflow:

ITSM Operations

This workflow creates the Webhook required for BMC Helix ITSM. The following operations are included in this workflow:

SNOW Change to ITSM Change

ITSM Change to SNOW Change

This workflow creates the ServiceNow change request when a BMC Helix ITSM change request is created or updated. The following operations are included in this workflow: