• Overview
  • Documentation
  • Version history

Description

ServiceNow supports application delivery by integrating service management processes, social collaboration for IT departments, software-as-a-service delivery, and web functionality. The ServiceNow plug-in for HCL DevOps Velocity automates the importing of records for ServiceNow incident management (beta), change management, and problem management from a ServiceNow server.

Quick Info

Product icon

Product

DevOps Velocity (HCL Accelerate)
Plugin type icon

Type

plugin
Compatibility icon

Compatibility

HCL DevOps Velocity 5.0.0 or later; HCL Accelerate 2.0x to 4.0.x
created by icon

Created by

HCLSoftware
Website icon

Website

Published Date

Last Updated

Summary

The ServiceNow plug-in provides for integration with a ServiceNow server. This plug-in imports incident management (Beta), change management and problem management data from a ServiceNow server and provides a single view of ServiceNow incidents, change requests, and problems in an HCL DevOps Velocity value stream map. Data between the ServiceNow server and the HCL DevOps Velocity server is synchronized every five minutes.

The plug-in can also be used to automate several ServiceNow tasks, such as create and update a ServiceNow request.

Compatibility

The plug-in supports the ServiceNow Madrid, Orlando, Paris and Washington release.

 

Usage

To use the ServiceNow plug-in, the plug-in must be loaded and an instance created before you can configure the plug-in integration and use plug-in automation tasks. You define configuration properties in the user interface or in a JSON file.

See the Automation Tasks tab for information on using automation tasks.

Integration type

The ServiceNow plug-in supports scheduled events integration which are listed in the following table.

Scheduled events
snowAllResources Queries the ServiceNow repository for Incidents, Change request, Problems,  ServiceNowWaitChangeTask,  ServiceNowWaitRequests

Integration

There are two methods to integrate the plug-in:

  • Using the user interface
  • Using a JSON file

Using the user interface

  • From the Plug-ins page, click Settings > Integrations > Plug-ins.
  • Under the Action column for the plug-in, click Add Integration.
  • On the Add Integration page enter values for the fields used to configure the integration and define communication.
  • Click Save.

Using a JSON file

The JSON file contains the information for creating a value stream and integrating with the ServiceNow server. The following table describes the information for the creating a HCL DevOps Velocity value stream map.

  • From a value stream page, download the value stream map. The value stream map is a JSON file used to define integrations.
  • Edit the JSON file to include the plug-in configuration properties.
  • Save and upload the JSON file. This replaces the current JSON file with the new content.
  • View the new integration on the Integrations page.

Configuration Properties

The following tables describe the properties used to configure the integration. Each table contains the field name when using the user interface and the property name when using a JSON file.

  • The General Configuration Properties table describes configuration properties used by all plug-in integrations.
  • The ServiceNow Configuration Properties table describes the ServiceNow configuration properties that define the connection and communications with the ServiceNow server. When using the JSON method to integrate the plug-in these properties are coded within the properties configuration property.

Some properties might not be displayed in the user interface, to see all properties enable the Show Hidden Properties field.

General Configuration properties
Name Description Required Property Name
NA The version of the plug-in that you want to use. To view available versions, click the Version History tab. If a value is not specified, the latest version is used. No image
Integration Name An assigned name to the value stream. Yes name
Logging Level The level of Log4j messages to display in the log file. Valid values are: all, debug, info, warn, error, fatal, off, and trace. No loggingLevel
NA List of configuration properties used to connect and communicate with ServiceNow server. Enclose the properties within braces. Yes properties
  The name of the tenant. Yes tenant_id
NA Unique identifier assigned to the plug-in. The value for the ServiceNow Server plug-in is ucv-ext-servicenow Yes type
ServiceNow Properties
Name Type Description Required Property Name
Access Token Secure The access token used to authenticate with the ServiceNow server. You can use either this property or the Password property for authentication.
Note: When using OAuth 2.0, the Access Token will be ignored.
No accessToken
Password Secure The password used to authenticate with the ServiceNow server. No password
HCL DevOps Velocity User Access Key Secure The user access key to authenticate with the HCL DevOps Velocity server. Yes ucvAccessKey
URL String The URL of the ServiceNow server. Yes baseUrl
User Name String The username used to authenticate with the ServiceNow server. No username
Proxy Server String The URL of the proxy server including the port number. No proxyServer
Proxy User Name String The user name used to authenticate with the proxy server. No proxyUsername
Proxy Password String The password used to authenticate with the proxy server. No proxyPassword
Resource types and sys_params Multiline This filed is used for selecting the Resource types (Change_request, incident, problem etc.,) to be synced and to pass sys_param values for each resource type. This field should be an array of objects where each object represents one event.
Example: [ { "table":"change_request", "sys_params":{ "category": "Software" } },... ]
Yes resourceTypesAndSys_params
Enable readonly replica Boolean When the feature flag is enabled, all the data collection queries will be reading it from the read replica instance. No enableReadonlyReplica
Client Id String The client ID used to authenticate with the ServiceNow server using OAuth2.0. No clientId
Client Secret Secure The client secret used for authentication with the ServiceNow server using OAuth2.0. No clientSecret
Refresh Token Secure The refresh token used for authentication with the ServiceNow server using OAuth2.0. No refreshToken

JSON code sample

The following sample code can be used as a template to define the integration within the JSON file for a value stream. Copy and paste the template into the JSON file Integration section and make the appropriate changes.


integrations": [
    {
      "type": "ucv-ext-servicenow",
      "name": "Plugin for ServiceNow",
      "tenant_id": "tenant_id",
      "logginglevel": "info",
      "properties": {
        "ucvAccessKey": "urbancodevelocity_user_accesskey",
        "baseUrl": "url_servicenow_server",
        "username": "user_name",
        "password": "pass_word",
        "client_id": "client_Id",
        "client_secret": "client_secret",
        "refresh_token": "refresh_token",
        "proxyServer": "proxy_server_url",
        "proxyUsername": "proxy_server_user_name",
        "proxyPassword": "proxy_server_password" 
      }
    }
  ]

Automation Tasks

The following automation tasks are available in the ServiceNow plug-in:

ServiceNow – Create Change Request and Change Task

Use this step to create a ServiceNow change request in HCL DevOps Velocity.

Name Description Required
Short Description A short description of the ServiceNow change request. Yes
Request type The type of request type for the ServiceNow application. Example: Standard, Normal, and Emergency. Yes
Assignment group The assignment group for the ServiceNow application. Yes
Additional properties A list of additional properties for the change request in the format for each list item is {“property”:”value”}.
Example: {“short_description”:”Created by HCL Accelerate”}.
Separate each list item with a comma (,). See the ServiceNow API documentation for additional properties.
No
Create change task To create change task , provide necessary properties.
Example: [{“short_description”:”createtask”,”change_task_type”:”planning”,”description”:”changetask”,”start_date”:”2024-01-30 08:05:04″,”end_date”:”2024-01-31 08:05:13″,”outputProperty”:”example”}]. Here outputProperty holds sys_id of change task created.
To create multiple change task, provide comma separated objects.
Example: [{},{},{}].To create under existing change request mention “parent”:”CHG0030008″,”change_request”:”CHG0030008″ along with other properties.
No
Output property The name of the property that the sys_id of the created change request is saved. No

ServiceNow – Update Change Request and Change Task

Use this step to update a ServiceNow change request in HCL DevOps Velocity.

Name Description Required
Change Request Number Enter the change request number.
Note: Either change request number or property reference must be provided
No
Change request system id from property reference Enter the property reference to system id.
Note: Either change request number or property reference must be provided
No
Change request properties Enter properties for the change request to be updated in the format for each list item is {“property”:”value”}.
Example: {“short_description”:”change request description”,”planned_end_date”:”2024-01-31 07:52:53″,”planned_start_date”:”2024-01-30 07:52:47″}. Separate each list item with a comma (,). See the ServiceNow API documentation for additional properties.
No
Update change task To update change task , provide necessary properties.
Example to update:[{"sys_id":"abcd123","change_task_type":"planning","state":"1","planned_end_date":"2024-05-17 02:36:44","planned_start_date":"2024-05-17 02:36:30"}]
Example to create:[{"short_description":"createtask","change_task_type":"planning","description":"changetask","planned_end_date":"2024-05-17 02:36:44","planned_start_date":"2024-05-17 02:36:30","outputProperty":"example"}]. If sys_id not given, it creates change task.
To update multiple change task provide comma separated objects. Example: [{},{},{}]
No

ServiceNow – Wait Change Request

Use this task to wait ServiceNow change request in HCL DevOps Velocity.

Name Description Required
Change Request Number Enter the change request number.
Note: Either change request number or property reference must be provided
No
Change request system id from property reference. Enter the property reference to system id.
Note: Either change request number or property reference must be provided
No
Field The change request field to wait for a match. Yes
Value The value to match with the change request field. Yes

ServiceNow – Wait Change Task

Use this step to create a ServiceNow wait change task.

Name Description Required
Change task system id from property reference. Enter the property reference to system id. Yes
Change Request Number Enter the change request number.
Note: Either change request number or property reference must be provided
No
Change request system id from property reference. Enter the property reference to system id.
Note: Either change request number or property reference must be provided
No
field Enter the change task field to wait for a match Yes
Value Enter the value to match the change task field Yes

Adding automation tasks to a release

After the plug-in is integrated, automated tasks are available to add as a task within a release.

  • Verify that the ServiceNow server is connected to HCL DevOps Velocity.
  • On the Create Task page, select the automation task from the Type field drop-down list.
  • Complete the properties required for the task.
  • Click Save.

Examples


integrations": [
    {
      "type": "ucv-ext-servicenow",
      "name": "Plugin for ServiceNow",
      "tenant_id": "tenant_id",
      "logginglevel": "info",
      "properties": {
        "ucvAccessKey": "urbancodevelocity_user_accesskey",
        "baseUrl": "url_servicenow_server",
        "username": "user_name",
        "client_id": "client_Id",
        "client_secret": "client_secret"
        "refresh_token": "refresh_token",
        "accessToken": "access_token",
        "proxyServer": "proxy_server_url",
        "proxyUsername": "proxy_server_user_name",
        "proxyPassword": "proxy_server_password"  
      }
    }
  ]

Using OAuth with ServiceNow

To use OAuth in your integration, you need to provide the following details during configuration:

  • client_id
  • client_secret
  • refresh_token

Perform the following steps to obtain the client_id and client_secret from your ServiceNow instance:

1. Log in to your ServiceNow instance.

2. In the left-hand navigation pane, search for OAuth and select Application Registry.

3. Click New and choose Create an OAuth API endpoint for external clients.

4. Fill in the required details and click Submit.

5. After submission, navigate to the newly created OAuth record and click on it to view the client_id and client_secret.

To obtain the refresh token send a POST request by providing the username, password, Client ID and Client secret as shown in the below image.

Use the credentials client_id, client_secret and refresh_token in your integration to authenticate using OAuth.

Note: You must provide username and password along with client_id and client_secret if you are not providing the refresh token during the integration to authenticate using OAuth.

ucv-ext-servicenow:1.1.10

Uploaded: 27-Nov-2024 06:10

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.10
 

Release Notes

  • Added support for Refresh Token to enable secure authentication and implemented Unified Scheduled Events.

ucv-ext-servicenow:1.1.8.tar

Uploaded: 26-Sep-2024 02:10

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.8
 

Release Notes

  • OAuth 2.0 client credentials flow added for ServiceNow integration.
  • Refresh token mechanism introduced for automatic token renewal when the access token expires.

ucv-ext-servicenow:1.1.6.tar

Uploaded: 08-Jul-2024 05:10

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.6
 

Feature Enhancement

  • We've added a new field for Resource Types and Sys_params, which will synchronize events based on the provided sys_params.
  • When the feature flag is enabled, all data collection queries will read from the read replica instance.

ucv-ext-servicenow:1.1.5.tar

Uploaded: 29-May-2024 12:18

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.5
 

  • Bug fix: Removed drop down feature in update change request and change task and wait changes automation task which was implemented to select change request number as it was uploading more data to integration details. Now user can enter change request number manually.
  • Bug fix: Enabled to create standard and emergency change request in create change request and change task automation task by changing api request made to create.( earlier it was creating only normal change )
  • Improvement: Previously, all scheduled events would run automatically. Now, you can select specific events to execute, and only the chosen events will run.

ucv-ext-servicenow:1.1.4.tar

Uploaded: 16-Apr-2024 11:10

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.4
 

  • Add initial sync: Under the hidden properties section of add integration page for the plugin an Initial Sync Date field is added. This field is optional and can be used only for the first sync.
  • Resync functionality: After integration plugin provides an option to perform either full resync or resync from selected date so that plugin resync again.
  • Output Property field added: For automation task create change request and change task output property field is added which stores system id of change request when created and for change task output property is provided inside object under create change task field.
  • Wait change task: A new automation task is created for waiting change task.

ucv-ext-servicenow:1.1.3.tar

Uploaded: 27-Feb-2024 10:51

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.3
 

  • Minor bug fix: Earlier plugin was unable to resync when incident is resolved.
  • Feature Enhancement: Implemented drop down to select change request number in update change request and change task and wait changes automation tasks.

ucv-ext-servicenow:1.1.2.tar

 

Uploaded: 02-Feb-2024 11:10

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.2
 

  • Bug fix: The previous version was failing to upload issues of large size.
  • Minor enhancement: Previously, the number of issues per page was fixed, but now it is configurable. You can modify the number of issues per page to fetch.
  • Feature enhancement: In automation task enabled to create and update change task.
  • Bug fix: Fixed issue related to syncing of change and problem in servicenow schedule event.

ucv-ext-servicenow:1.1.1.tar

 

Uploaded: 18-Dec-2023 17:11

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.1.1
 

Release Notes

  • Import incidents
  • Add Incident creation automation task

ucv-ext-servicenow:1.0.42.tar

 

Uploaded: 13-Jul-2023 12:13

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.0.42
 

Release Notes

  • Minor bug fix: Fixed bug related to proxy server change and related to automation task execution.

ucv-ext-servicenow:1.0.41.tar

 

Uploaded: 06-Jul-2023 07:04

ucv-ext-servicenow:1.0.36.tar

 

Uploaded: 26-Aug-2022 08:46

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.0.36
 

Release Notes

  • Removed Manual User Access Key: From current version onwards this plugin will only support Auto Generated User Access Key feature of HCL Accelerate.

ucv-ext-servicenow:1.0.27.tar

 

Uploaded: 19-Aug-2021 05:28

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.0.27
 

Release Notes

  • Adding Automation Functionality

ucv-ext-servicenow:1.0.25.tar

 

Uploaded: 01-Jun-2021 07:00

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.0.25
 

Release Notes

  • Removed IBM related keywords

ucv-ext-servicenow:1.0.14.tar

 

Uploaded: 08-Feb-2021 07:41

Pull Command

docker pull hclcr.io/accelerate/ucv-ext-servicenow:1.0.14
 

Release Notes

  • Added proxy support

ucv-ext-servicenow:1.0.13.tar

 

Uploaded: 08-Feb-2021 07:41

Related Plugins