ServiceNow is a software-as-a-service (SaaS) provider of IT service management (ITSM) software. It creates a single system of record for all IT processes within a company. This system brings together IT strategy, design, transition and operation on a powerfully simple cloud platform that just works.
ServiceNow is built to be a productivity tool for all types of business users including the CIO, service desk staff, application developers, IT finance, IT operations and business people. ServiceNow applications are built on a single platform as a service. The platform offers a consistent and intuitive user experience through the entire IT Infrastructure Library (ITIL) service life-cycle.
For more information about ServiceNow, go to the ServiceNow home page.
CloudBees CD/RO integration to ServiceNow
ServiceNow supports calling both inbound services leveraging the ServiceNow REST API to perform actions such as queries and updates as well as calling outbound web services, such as CloudBees CD/RO Rest API, upon a user action in ServiceNow such as an Approval or Rejection of a change request.
This plugin supports the inbound interaction with ServiceNow, only, by calling provider web services such as creating a change request, creating an incident, getting the status of an approval, and so on.
The Native Extension plugin which is installed in a ServiceNow instance supports the outbound (consumer) web service interaction and is available in the Service Now Marketplace. This plugin is documented here for no purpose other than cross referencing CloudBees CD/RO capabilities for both inbound and outbound interactions.
-
The Native Extension plugin which mentioned in a separate section of this document is not required to be installed in ServiceNow if there is no need for the outbound interaction.
-
If you have not installed a CloudBees CD/RO ServiceNow application, you cannot use the bi-directional integration features in CreateChangeRequest and CreateChangeTask procedures.
Plugin Version 3.1.0.2022041327
Revised on April 14, 2022
Updated Perl version required
This plugin is using an updated version of Perl, cb-perl shell (instead of old ec-perl). This means that it needs CloudBees CD agent version 10.3+ in order to work.
Integrated version
This plugin was developed and tested against following ServiceNow versions:
-
Eureka (Deprecated)
-
Fuji (Deprecated)
-
Geneva (Deprecated)
-
Helsinki (Deprecated)
-
Istanbul (Deprecated)
-
Jakarta (Deprecated)
-
Kingston (Deprecated)
-
London (Deprecated)
-
Madrid (Deprecated)
-
New-York
-
Paris
-
Orlando
| For all parameter descriptions in this document, required parameters are shown in bold italics. |
| In the CloudBees CD UI, go to the Home page, open the Main Menu, and select Admin > Plugins to open the Plugin Manager. |
Setting up the plugin configuration
Plugin configurations are sets of parameters that apply across some or all of the plugin procedures. They reduce repetition of common values, create predefined sets of parameters for end users, and store credentials securely. Each configuration has a unique name that is automatically entered in designated parameters in the procedures.
Input
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
Find the EC-ServiceNow row.
Select Configure to open the ServiceNow Configurations page.
Select Create Configuration.
To create a ServiceNow configuration, enter the following information, and select OK.
Remember that you may need to create additional configurations later.
| Parameter | Description |
|---|---|
Configuration Name | Name of the plugin configuration. (Required) |
Host | Host machine, such as "https://demo10.service-now.com". (Required) |
Test connection? | If checked, a connection endpoint and credentials will be tested. |
Use CloudBees CD Application? | If checked, EC-ServiceNow will assume that CloudBees CD Native Application is installed on target instance. Otherwise no native application specific APIs would be used. Procedures affected by this checkbox:
|
Login as |
|
Log Level | This option sets debug level for logs. If info is selected, only summary information will be shown; for debug, there will be some debug information. |
HTTP Proxy | A HTTP proxy that should be used for connections. |
Proxy Authorization | Username and password used to connect to HTTP proxy. |
Using non-admin users on ServiceNow instance with CloudBees CD application
IMPORTANT: if you decided to use non-admin user in ServiceNow instance with enabled CloudBees CD application, you should ensure that user has necessary roles: import_transformer and EFImportTableAdmin.
Plugin procedures
AddRecord
This procedure adds a record to ServiceNow.
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the AddRecord procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Name of the configuration. (Required) |
Record ID | Record ID of the incident, such as a table or number. |
Content | JSON representation of the request content that will be used as content. To add a short description, you can use next JSON:\{"short_description":"New Short Description"}. |
PropertySheet for procedure result | The property sheet where the procedure results should be saved. The default is /myJobStep. |
Output
After the job runs, you can view the results on the Job Details page in CloudBees CD.
In the AddRecord step, select Log to see the diagnostic information:
AttachChangeTasksToChangeRequest
This procedure attaches one or more change tasks to the change request. All CRs and Tasks should exist already, else procedure will fail.
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the AttachChangeTasksToChangeRequest procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Provide the name of the configuration to use. |
Change Request Record Id | A Change Request Record Id to which previously existing Change Tasks should be linked. |
Change Tasks Record Ids | A comma-separated Change Task Record Ids of existing Change Tasks that should be linked to existing Change Request. |
CheckApprovalStatus
This procedure checks the status of one or more approvals. When you select the "Check All" parameter, all the approvals are retrieved. When you select or specify the other parameters, specific approvals are retrieved. When both the "Approval For" and "Approver" parameters are specified, CloudBees CD searches for and retrieves approvals that match both parameters. When the same approvals are retrieved using either the "System ID(s)" parameters or the "Approval For" and "Approver" parameters, CloudBees CD retrieves and displays them once.
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the CheckApprovalStatus procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Name of the configuration. (Required) |
Check All | If selected, all approvals are retrieved. |
Approval For | The identifier for what the approval is for. An example of a change request is CHG0000009. |
Approver | The user or group who approves the approval requests. |
System ID(s) | The unique identifier for an approval. You can specify more than one ID, separating them with commas. |
CollectReportingData
This procedure creates incident report and sends it to CloudBees CD.
Input
-
Create schedule, or procedure within any project.
-
Go to the that project or schedule and add a plugin procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration name | Provide the name of the configuration to use. |
Source table | Servicenow table to get reporting data from. It is should be ServiceNow table name, but no label. For example, for Incident table it should be incident, for Change Request it should change_request. |
Filter | Filter in JSON format. For example: |
Preview mode | Special CollectReportingData procedure mode. This mode is designed to help customer with report configuration. If this mode is enabled, no reports will be sent and no metadata will be set. High verbosity will be enabled instead. In that mode user can configure mappings, transformation before set before enabling automatic reporting. In this mode each object, retrieved from servicenow will be displayed, transformation, mapping and final payload will be displayed also. |
Use Table API | If checked, ServiceNow Table API will be used instead of JSONv2 API for data retrieval. Table API returns data with a different structure, thus default mappings in "Field mapping" won’t work. Default mappings for Table API are available in the Table API Field Mapping help section. |
Field mapping | Allows user to place custom fields to payload, or modify payload values. Examples: "MyApplication":releaseName - map value "MyApplication" to payload releaseName field. lastBuiltRevision.SHA1:myLastRevision - map SHA1 field from lastBuiltRevision object to myLastRevision. lastBuiltRevision.branch[0].SHA1:myLastRevision - map SHA1 field from first element of branch array of lastBuiltRevision object to myLastRevision. |
Transform script | Allows user to provide perl script for payload customization. This method will be invoked by plugin with 2 parameters. 1st parameter is context object, 2nd is payload object. Method should be named "transform", and should return payload object. In this example myTimestamp field will be added to payload object: sub transform {
my ($context, $payload) = @_;
$payload->{myTimestamp} = $context->one();
return $payload;
}
sub one {
my ($context) = @_;
return time();
} |
Metadata propertysheet path | Path to propertysheet which will be used to store metadata. If omited, path will be used depending on context: schedule or procedure. |
Base URL for drill-down | Drill-down URL for the records in ServiceNow. |
Release Filter URI | URI that will be used with the base Url to build a drill-down URL for records in ServiceNow. |
Debug | If checked, the debug level will be set to "Debug". |
Table API field mapping
If "Use Table API" checkbox is checked, ServiceNow Table API will be used instead of JSONv2 API for data retrieval. Table API returns data with a different structure, thus default mappings in "Field mapping" won’t work. Default mappings for Table API:
number.display_value:incidentId, category.display_value:category, subcategory.value:subCategory, cmb_ci.display_value:configurationItem, priority.display_value:priority, state.display_value:status, opened_by.display_value:reportedBy, resolved_at.value:resolvedOn, sys_created_on.value:createdOn, sys_updated_on.value:modifiedOn, cmdb_ci.display_value:releaseName, "Enter-release-project-name-here":releaseProjectName
Dot-walking feature
With enabled Table API you can use ServiceNow "dot-walking" feature. You can specify chains of field names separated by escaped dots (periods) in Field Mapping parameter:
assigned_to.company.display_value:company, opened_by.manager.value:manager, opened_by.department.dept_head.display_value:department_head
CreateChangeRequest
This procedure creates new Change Request in the ServiceNow instance. If Correlation ID and Correlation Display is specified and CloudBees CD Integration Scoped Application is installed and enabled on ServiceNow side it’s possible to approve gate task in the CloudBees CD automatically after approval in the ServiceNow.
Note:
In order to use this procedure for bi-directional integration a CloudBees CD application should be installed on your ServiceNow instance from ServiceNow Store and enabled parameter "Use CloudBees CD Application?" in used EC-ServiceNow configuration. If you have not installed the Native Extension plugin, you can disable parameter "Use CloudBees CD Application?" in configuration or use the AddRecord procedure instead to create a change request.
Note about non-admin users on ServiceNow instance with enabled CloudBees CD application:
Please, ensure that user in ServiceNow instance has necessary roles. Details: Using non-admin users on ServiceNow instance with CloudBees CD application
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the CheckApprovalStatus procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Name of the configuration. (Required) |
Description | Short description for new change request. (Required) |
Correlation ID | Used only for bi-directional integration with native ServiceNow plugin "CloudBees CD". Parameter for CloudBees CD ServiceNow scoped application. Should contain path for the completeManualTask REST call. This parameter will be used for pipeline gate approval or reject by approving or rejecting change request at the servicenow side. Example: /flowRuntime/$[/myPipelineRuntime/id]/stage/Stage 1/gate/POST/taskName/out1 . Where $[/myPipelineRuntime/id] is a property with current runtime id, stage is a Pipeline Stage name and out1 is gate name with type POST. For integration Correlation Display parameter should be also provided. |
Correlation Display | Used only for bi-directional integration with native ServiceNow plugin "CloudBees CD". Parameter for CloudBees CD servicenow scoped application. Should be set to "ElectricFlow Pipeline Task" (without quotes) to trigger CloudBees CD ServiceNow scoped application. Also, for integration proper Correlation ID should be also set. |
Content | Additional change_request table parameters. |
PropertySheet for procedure result | Property Sheet where procedure results should be stored. |
CreateChangeTask
This procedure creates new Change Task in the ServiceNow instance. If Correlation ID and Correlation Display is specified and CloudBees CD Integration Scoped Application is installed and enabled on ServiceNow side it’s possible to approve gate task in the CloudBees CD automatically after closing task in the ServiceNow.
Note:
In order to use this procedure for bi-directional integration a CloudBees CD application should be installed on your ServiceNow instance from ServiceNow Store and enabled parameter "Use CloudBees CD Application?" in used EC-ServiceNow configuration. If you have not installed an CloudBees CD application, you can disable parameter "Use CloudBees CD Application?" in configuration or use the AddRecord procedure instead to create a change task.
Note about non-admin users on ServiceNow instance with enabled CloudBees CD application:
Please, ensure that user in ServiceNow instance has necessary roles. Details: Using non-admin users on ServiceNow instance with CloudBees CD application
Input
-
In the Main Menu, Admin > Plugins to open the Plugin Manager.
-
Go to the CreateChangeTask procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Name of the configuration. (Required) |
Description | Short description for new change task. (Required) |
Correlation ID | Used only for bi-directional integration with native ServiceNow plugin "CloudBees CD". Parameter for CloudBees CD ServiceNow scoped application. Should contain path for the completeManualTask REST call. This parameter will be used for pipeline gate approval by closing change task at the ServiceNow side. Example: /flowRuntime/$[/myPipelineRuntime/id]/stage/Stage 1/gate/POST/taskName/out1 . Where $[/myPipelineRuntime/id] is a property with current runtime id, stage is a Pipeline Stage name and out1 is gate name with type POST. For integration Correlation Display parameter should be also provided. |
Correlation Display | Used only for bi-directional integration with native ServiceNow plugin "CloudBees CD". Parameter for CloudBees CD servicenow scoped application. Should be set to "ElectricFlow Pipeline Task" (without quotes) to trigger CloudBees CD ServiceNow scoped application. Also, for integration proper Correlation ID should be also set. |
Change Task Details | Specify values for various ServiceNow Change Task fields using JSON format. For e.g. |
Change Request Record Id | Specify the record Id of change request to which change task should be attached. Number or sys id of change request are expected. Validation of this change request will be performed before change task creation and procedure will fail if it does not exist. |
PropertySheet for procedure result | Property Sheet where procedure results should be stored. |
CheckChangeRequestStatus
This procedure checks the status of one or more change requests. When you select the "Check All" parameter, all the change requests are retrieved. When you select and specify other parameters, specific change requests are retrieved. When the "Requested By", "Assigned To", "Configuration Item", "Category", "Priority", "Risk", and "Type" parameters are all specified, CloudBees CD searches for and retrieves change requests that match all of these parameters. When the same change requests are retrieved using either the "Number(s)" parameters or a combination of the other parameters as the search criteria, CloudBees CD retrieves the change requests once.
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the CheckChangeRequestStatus procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | The name of the configuration. (Required) |
Check All | If selected, all change requests are retrieved. |
Number(s) | The change request number. You can specify more than one change request number, separating them with commas. |
Requested By | The sys_id of user who requested the change request. |
Assigned to | The sys_id of user who is assigned the change request. |
Configuration Item | The sys_id of configuration item associated with the change request. |
Category | The category assigned to the change request. |
Priority | The priority assigned to the change request. |
Risk | The risk assigned to the change request. |
Type | The type of change request. |
CreateIncident
This procedure creates an incident in ServiceNow.
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the CreateIncident procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | The name of the configuration. (Required) |
Description | Short description of the incident. (Required) |
Assignee | User or group to which the incident is assigned. |
Impact | The effect an incident has on business. Specify the impact level as an integer. |
Urgency | The extent to which the incident’s resolution can be delayed. Specify the urgency level as an integer. |
Priority | How quickly the service desk should address the incident. Specify the priority level as an integer. |
Content | JSON representation of the request content that will be used as content. To add a short description, you can use next JSON: |
PropertySheet for procedure result | The property sheet where the procedure results should be saved. The default is /myJobStep. |
DeleteIncident
This procedure deletes an incident in ServiceNow.
GetChangeTasks
This procedure is designed to retrieve change tasks from ServiceNow Change Tasks table.
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the GetChangeTasks procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Provide the name of the configuration to use. |
Change Task Retrieval Type | A type which will be used for change task retrieval. Available types:
|
Record Id | A Record Id of ServiceNow ChangeTask to retrieve. |
Change Request Record Id | Specify the record Id of change request to which change task should be attached. Number or sys id of change request are expected. Validation of this change request will be performed before change task creation and procedure will fail if it does not exist. |
ServiceNow QL | A ServiceNow QL query, that could be copied in ServiceNow instance table navigation by "Copy query" link. |
Result Property Sheet | Property sheet where procedure results should be saved. |
GetRecord
This procedure returns a record from ServiceNow.
Input
-
In the Main Menu, select Admin > Plugins to open the Plugin Manager.
-
Go to the GetRecord procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Name of the configuration. (Required) |
Record ID | Universal field for ServiceNow records identification. SysID, Number, or Table may be specified. For example, INC00001 will be parsed as number, incident will be parsed as table, d1552ef84f0e4200a94bdd211310c79f as sys_id and incident.d1552ef84f0e4200a94bdd211310c79f as sys_id from incident table. Few identifiers also may be specified. Numbers should be separated by comma. For unsupported or custom tables and prefixes should be used format "table.number". For example: INC00001, INC00002, d1552ef84f0e4200a94bdd211310c79f, incident.d1552ef84f0e4200a94bdd211310c79f, incident my_table.MYPREFIX0123456 |
Filter | JSON filter for the results. |
PropertySheet for procedure result | The property sheet where the procedure results should be saved. The default is /myJobStep. |
SetChangeRequestStatus
This procedure sets the status of one or more change requests. When the "Requested By", "Assigned To", "Configuration Item", "Category", "Priority", "Risk", and "Type" parameters are all specified, CloudBees CD retrieves the change requests that match all of these parameters and updates their status. When the same change requests are retrieved using either the "Number(s)" parameters or a combination of the other parameters as the search criteria, CloudBees CD retrieves, updates, and displays them once.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the SetChangeRequestStatus procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | The name of the configuration. (Required) |
New State | The new state for one or more change requests that match the search criteria: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped. The default is Pending. (Required) |
Number(s) | One or more change request numbers. You can specify more than one change request number, separating them with commas. |
Requested By | The sys_id of user who requested the change request. |
Assigned to | The sys_id of user assigned to the change request. |
Configuration Item | The sys_id of configuration item associated with the change request. |
Category | The category assigned to the change request: Software, Hardware, Business Service, Systems Software, Applications Software, Network, Telecom, Documentation, or Other. |
Priority | The priority assigned to the change request: 1 - Critical, 2 - High, 3 - Moderate, 4-Low, 5-Planning, or None. |
Risk | The risk assigned to the change request: Very High, High, Moderate, Low, or None. |
Type | The type of change request: Routine, Comprehensive, Emergency, or None. |
UpdateIncident
This procedure creates an incident in ServiceNow.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the UpdateIncident procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | The name of the configuration. (Required) |
Description | Short description of the incident. (Required) |
Sys ID | The Sys ID (sys_id) of the incident. (Required) |
Assignee | User or group to which the incident is assigned. |
Impact | The effect an incident has on business. Specify the impact level as an integer. |
Urgency | The extent to which the incident’s resolution can be delayed. Specify the urgency level as an integer. |
Priority | How quickly the service desk should address the incident. Specify the priority level as an integer. |
Content | JSON representation of the request content that will be used as content. To add a short description, you can use next JSON: |
PropertySheet for procedure result | The property sheet where the procedure results should be saved. The default is /myJobStep. |
UpdateRecord
This procedure returns a record from ServiceNow.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the UpdateRecord procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Name of the configuration. (Required) |
Record ID | Universal field for ServiceNow records identification. SysID, Number, or Table may be specified. For example, INC00001 will be parsed as number, incident will be parsed as table, d1552ef84f0e4200a94bdd211310c79f as sys_id and incident.d1552ef84f0e4200a94bdd211310c79f as sys_id from incident table. Few identifiers also may be specified. Numbers should be separated by comma. For unsupported or custom tables and prefixes should be used format "table.number". For example: INC00001, INC00002, d1552ef84f0e4200a94bdd211310c79f, incident.d1552ef84f0e4200a94bdd211310c79f, incident my_table.MYPREFIX0123456 |
Filter | JSON filter for the results. |
Content | JSON representation of the request content that will be used as content. To add a short description, you can use next JSON: |
PropertySheet for procedure result | The property sheet where the procedure results should be saved. The default is /myJobStep. |
UpdateTasksStatuses
This procedure sets the status of one or more tasks. When the "Requested By", "Requested For", "Assignment Group", and "Approval" parameters are all specified, CloudBees CD retrieves the tasks that match all of these parameters and updates their status. When the same change requests are retrieved using either the "Number(s)" parameters or a combination of the other parameters as the search criteria, CloudBees CD retrieves, updates, and displays them once.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the UpdateTasksStatuses procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | The name of the configuration. (Required) |
New State | The new state for one or more change requests that match the search criteria: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, and Closed Skipped. The default is Pending. (Required) |
Number(s) | One or more change request numbers. You can specify more than one change request number, separating them with commas. |
Requested Item | The sys_id of requested item associated with the task. |
Requested for | The sys_id of user for whom the request was created. |
Assignment Group | The sys_id of group assigned to the task. |
Approval | The approval value for the task: Not Yet Requested, Requested, Approved, or Rejected. |
CreateRecord_NextGen
This general-purpose procedure can be used to create records in ServiceNow in place of granular procedures that have been already exposed in this plugin. This procedure integrates with ServiceNow using the REST Table API and supports the scenario wherein a User can optionally pass Display Values as opposed to System Identifiers.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the CreateRecord_NextGen procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Previously defined configuration for the plugin. |
Table | Target table on ServiceNow instance, where record should be created. For example, Table = change_request, if you are creating a Change Request Table = change_task, if you are creating a Change Task |
Short description | Short description for creating record. Note: some tables doesn’t have "short_description" field. |
Content | JSON representation of the request content. Will be used as content. For example, you can set short_description with next JSON: |
Get Display Values | Based on this value, retrieve the display value and/or the actual value in records fields. Possible values:
|
Use Input Display Values | If checked treat input values as display values. |
GetRecords_NextGen
This general-purpose procedure can be used to retrieve records from ServiceNow in place of granular procedures that have been already exposed in this plugin. This procedure integrates with ServiceNow using the REST Table API and supports the scenario wherein a User can optionally pass Display Values as opposed to System Identifiers.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the GetRecords_NextGen procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Previously defined configuration for the plugin. |
Retrieval type | A type which will be used for records retrieval. Possible values:
|
Table | Table on ServiceNow instance, where records should be searched. For example, Table = change_request, if you are searching a Change Request Table = change_task, if you are searching a Change Task |
Sys IDs | SysIDs of the target records, separated by comma, whitespace and/or newline. |
Numbers | Numbers of the target records, separated by comma, whitespace and/or newline. |
ServiceNow QL | A ServiceNow QL query, that could be copied in ServiceNow instance table navigation by "Copy query" link. |
Get Display Values | Based on this value, retrieve the display value and/or the actual value in records fields. Possible values:
|
UpdateRecord_NextGen
This general-purpose procedure can be used to update records in ServiceNow in place of granular procedures that have been already exposed in this plugin. This procedure integrates with ServiceNow using the REST Table API and supports the scenario wherein a User can optionally pass Display Values as opposed to System Identifiers.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the UpdateRecord_NextGen procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Previously defined configuration for the plugin. |
Table | Target table on ServiceNow instance, where record should be updated. For example, Table = change_request, if you are updating a Change Request Table = change_task, if you are updating a Change Task |
Sys ID | Sys ID of the target record on ServiceNow instance. |
Content | JSON representation of the request content. Will be used as content. For example, you can set short_description with next JSON: \{"short_description" : "New Short Description"} |
Get Display Values | Based on this value, retrieve the display value and/or the actual value in records fields. Possible values:
|
Use Input Display Values | If checked treat input values as display values. |
DeleteRecord_NextGen
This general-purpose procedure can be used to delete records in ServiceNow in place of granular procedures that have been already exposed in this plugin. This procedure integrates with ServiceNow using the REST Table API.
Input
-
In the Main Menu, click Admin > Plugins to open the Plugin Manager.
-
Go to the DeleteRecord_NextGen procedure.
-
Enter the following parameters:
| Parameter | Description |
|---|---|
Configuration Name | Previously defined configuration for the plugin. |
Table | Target table on ServiceNow instance, where record should be deleted. For example, Table = change_request, if you are deleting a Change Request Table = change_task, if you are deleting a Change Task |
Sys ID | Sys ID of the target record on ServiceNow instance. |
ServiceNow native extension plugin
Refer to the ServiceNow Marketplace for more details about this plugin. The following information is provided for the purposes of cross referencing.
This plugin refers to the CloudBees CD plugin that is installed in ServiceNow to facilitate an Approval or Rejection of a Change Request by a ServiceNow user to perform an action in CloudBees CD (through a Rest API call to CloudBees CD) based on a Business Rule associated with change_request table. This integration would call run procedure API and run a job on CloudBees CD server. This job would approve a specified stage’s Exit Gate and move a pipeline to the next stage.
Setup steps
-
Install the CloudBees CD Application available in ServiceNow Store in your ServiceNow Instance going as an Admin user.
-
Upon installation the plugin will create a special user group called ServiceNowChangeApprovers with appropriate access rights in CloudBees CD.
-
Activate your application.
The following demo CloudBees CD and the setup required for it, is provided to illustrate the bidirectional integration between CloudBees CD and ServiceNow.
Demo CloudBees CD setup
Create a pipeline in CloudBees CD as follows:
-
Create Change Request as first pipeline task using CreateChangeRequest procedure. Set Correlation Id and Correlation display as follows:
-
Correlation id:
-
/flowRuntime/$[/myPipelineRuntime/id]/stage/%StageName%/gate/post/taskName/%GateName%
-
Correlation display:
ElectricFlow Pipeline Gate
-
Create gate with approve step on that pipeline.
-
Create task that should be performed only if pipeline gate has been approved.
Demo CloudBees CD
-
User creates change request on ServiceNow instance using EC-ServiceNow plugin on CloudBees CD.
-
After change request becomes approved (or rejected) on ServiceNow side, ServiceNow, using CloudBees CD application, sends notification to CloudBees CD where EC-ServiceNow is installed.
-
EC-ServiceNow, using an internal procedure, approves (or rejects) Pipeline Gate, that is waiting on decision.
-
Pipeline is continued or aborted.
Release notes
EC-ServiceNow 3.1.0
-
Plugin has been improved to support new plugin management system and new configurations.
-
Added session validation.
EC-ServiceNow 3.0.0
-
The plugin is switched to new Perl now. No backward compatibility with releases prior 10.3. Starting from this release new agent is required to run this plugin’s procedures.
EC-ServiceNow 2.9.0
-
New features have been added to CollectReportingData procedure: TableAPI support and "dot-walking" feature.
EC-ServiceNow 2.8.0
The following new procedures have been added to provide a Robust Integration with ServiceNow using Rest Table API. In addition, a user can optionally pass Display Values as opposed to system identifiers.
-
CreateRecord_NextGen
-
GetRecords_NextGen
-
UpdateRecord_NextGen
-
DeleteRecord_NextGen
AttachChangeTasksToChangeRequest procedure has been fixed to handle the scenario wherein the ServiceNow instance does not have AgileManagement tables.
GetRecord procedure has been fixed to handle the scenario wherein the ServiceNow instance does not have AgileManagement tables.
EC-ServiceNow 2.7.0
-
Added AttachChangeTasksToChangeRequest procedure.
-
Added GetChangeTasks procedure.
-
Improved CreateConfiguration and EditConfiguration procedures. Now it is possible to test connection to endpoint.
-
Improved CreateChangeTask procedure. Now it is possible to attach Change Task to existing Change Request during creation.
-
Fixed minor issue with a configuration form when warning was displayed when the widget was opened.
-
Fixed logging to property.
-
Fixed missing newline in log messages.
EC-ServiceNow 2.5.0
-
Added CreateChangeTask procedure.
-
Improved CreateConfiguration and CreateChangeRequest procedures. Now it is possible to use CreateChangeRequest and CreateChangeTask procedures without installed ElectricFlow Release application on ServiceNow side.
-
Improved ApproveOrRejectPipelineGate procedures. Added possibility to approve manual tasks in pipeline steps.
EC-ServiceNow 2.4.0
-
Added support for ServiceNow Agile/Release Module Objects.
-
Improved error message when using unknown record ID number prefix.
-
Fixed creating configuration by user with "@" in username.
EC-ServiceNow 2.3.0
-
Filter field of CollectReportingData procedure now supports ServiceNow query language.
-
Support of Release Command Center 9.0 has been added.
EC-ServiceNow 2.2.1
-
Fixed a bug when ApproveOrRejectPipelineGate was not able to approve or reject pipeline gate sometimes.
EC-ServiceNow 2.2.0
-
Support for HTTP Proxy has been provided. Customers who use HTTP proxy can specify Proxy Information (Host, Port and Credentials at the configuration level) and all procedures will use the Proxy as second credentials for authentication.
EC-ServiceNow 2.1.4
-
Configured the plugin to allow the ElectricFlow UI to create configs inline of procedure form.
-
Icon for ElectricFlow Dashboards has been added.
EC-ServiceNow 2.1.3
-
Configured the plugin to allow the ElectricFlow UI to render the plugin procedure parameters entirely using the configured form XMLs.
-
Enabled the plugin for managing the plugin configurations in-line when defining an application process step or a pipeline stage task.
EC-ServiceNow 2.0.1
-
The Content parameter was replaced with the Tagsmap parameter in the CreateIncident and UpdateIncident procedures.
EC-ServiceNow 2.0.0
-
The Plugin procedures now use the ServiceNow REST API instead of SOAP.
-
Plugin now is incompatible with previous releases.
-
Added the UpdateIncident procedures.
-
The Plugin was rewritten from scratch.