Configure Remote Support for the ServiceNow Integration

 

You must purchase this integration separately for both your Remote Support software and your ServiceNow solution. For more information, contact BeyondTrust's Sales team.

All of the steps in this section take place in the BeyondTrust /login administrative interface. Access your Remote Support interface by going to the hostname of your B Series Appliance followed by /login (e.g., https://support.example.com/login).

Verify the API is Enabled

Enable API

The Remote Support integration requires the Remote Support XML API to be enabled. This feature is used from within the integrating software to communicate with the Remote Support APIs.

Go to /login > Management > API Configuration and verify that Enable XML API is checked.

Create a ServiceNow OAuth API Account

The ServiceNow API account is used from within ServiceNow to make Remote Support Command API calls.

Add API Account

  1. Go to /login > Management > API Configuration.
  2. Click Add to create a new API account. Name it ServiceNow or something similar.
  3. Set Command API to Full Access.
  4. Under Reporting API, check all options.
  5. The OAuth Client ID and OAuth Client Secret are used during the OAuth configuration step in ServiceNow. Make note of these and store them in a secure location.
  6. Click Save.

Set Up Session Send

There are two ways to send sessions from Remote Support to ServiceNow: as Outbound events in Remote Support, or as scheduled jobs in ServiceNow. Outbound events sends sessions as they end. Scheduled jobs pull sessions at specified intervals. The preferred option depends on your workflow preferences and session volumes. You can use only one method, but you can change methods by reconfiguring session sending.

Add Outbound Events for Session Import

Outbound events are used to notify ServiceNow that a Remote Support session has finished and is ready to be imported into ServiceNow.

  1. Go to /login > Management > Outbound Events.
  2. Click Add and name the new HTTP recipient ServiceNow Integration or something similar, depending on your ServiceNow instance.
  3. Enter the URL https://example.service-now.com/api/x_bmgr_support_ent/outbound_event/session_end, where example.service-now.com is the ServiceNow instance name.
  4. If using an outbound event token for added security, append outbound_event_token=YOUR-TOKEN to the end of the URL, so that the entire URL resembles https://support.example.com/api/x_bmgr_support_ent/outbound_event/session_end?outbound_event_token=YOUR-TOKEN. You must also store this token with the appliance configuration record in ServiceNow.
  5. Scroll to Events to Send and check the following events:
    • Support Session End
    • Customer Exit Survey is Completed
    • Representative Survey is Completed
  6. At the top of the page, click Save.

Set up Schedule Job for Session Import

Rather than using outbound events to notify ServiceNow that a Remote Support session is ready to be imported, you can use a mechanism in ServiceNow known as a scheduled job. Using a scheduled job, you can poll the Remote Support Reporting API for the latest sessions on any schedule you prefer. Scheduled jobs are configured in ServiceNow.

For information on how to set up a scheduled job, please see Set up Scheduled Job for Session Import.

Set Up the Custom Link

Custom Link Setup

Remote Support custom links can be configured to allow representatives to quickly access the ServiceNow incident that is associated with the session.

  1. Browse to Rep Console > Custom Links.
  2. Click Add to create a new custom link.
  3. Enter a name for the link, and then set the URL, according to the task view, where support.example.com is the ServiceNow instance name. If needed, you can use any of the available macros to customize the link according to your specifications. The options are:
    • Task - Standard View:

      https://example.service-now.com/nav_to.do?uri=task.do?sys_id=%SESSION.CUSTOM.SNOW_TASK_ID%

    • Task - Agent Workspace View:

      https://example.service-now.com/now/workspace/agent/record/task/%SESSION.CUSTOM.SNOW_TASK_ID%

    • Interaction - Standard View:

      https://example.service-now.com/nav_to.do?uri=interaction.do?sys_id=%SESSION.CUSTOM.SNOW_INTERACTION_ID%

    • Interaction - Agent Workspace View:

      https://example.service-now.com/now/workspace/agent/record/interaction/%SESSION.CUSTOM.SNOW_INTERACTION_ID%

If the customer is using an external key to store the task sys_id, then use the macro %SESSION.CUSTOM.EXTERNAL_KEY% instead.

  1. Click Save to save the new link.

Create Custom Fields

Custom Fields

Remote Support custom fields are used to map ServiceNow Tasks (incidents, change requests, problem records, and service catalog requests), call records, and configuration items to Remote Support sessions.

  1. Browse to Configuration > Custom Fields.
  2. Click Add to create a new custom field.
  3. Enter the following values:
    • Display Name: ServiceNow Task ID
    • Code Name: snow_task_id
    • Show in Rep Console: checked
  4. Click Save to save the new field.
  5. Repeat these steps for the following custom field values:
    • Display Name: ServiceNow Configuration Item ID
    • Code Name: snow_cmdb_ci_id
    • Show in Rep Console: checked
  6. Also for the following custom field values:
    • Display Name: ServiceNow Call ID
    • Code Name: snow_call_id
    • Show in Rep Console: checked
  7. And again for the following custom field values:
    • Display Name: ServiceNow Interaction ID
    • Code Name: snow_interaction_id
    • Show in Rep Console: checked