Unsupported Screen Size: The viewport size is too small for the theme to render properly.

ServiceNow Bidirectional Collibra Integration

Published by: Collibra Marketplace
Latest version: 1.0.3
Released: August 4, 2022
Package Documentation
Community Offering

Your use of Community Offerings is subject to the Collibra Marketplace License Agreement. Read more.

Overview

For this specific integration (and all other Custom Integrations listed on the Collibra Marketplace), please read the following disclaimer:

  • This integration is a template that has been developed in cooperation with a few select clients based on their custom use cases and business needs.
  • While all effort has been made to encompass a range of typical usage scenarios, specific needs beyond this may require chargeable template customization.
  • With this in mind, we have made sure that the template is available as source code and readily modifiable to suit the client's particular use case.

ServiceNow is a cloud computing platform to help companies manage digital workflows for enterprise operations. It provides an IT Service Management system for resolving everyday internal IT issues.

The aim of this bidirectional integration is to synchronize Collibra Issues to the ServiceNow Platform as either Incident or Request Tickets. This integration is able to synchronize information between both platforms such as Name, Description, Status, Priority, Caller, Assignee, Direct links, Ticket types, and Comments. This integration has two methods of activation, the first being via a timed scheduler, and the second via an HTTP endpoint request. A CMA file is also included. This ensures that once this CMA file is imported within your Collibra instance, all the custom prerequisites will be generated automatically.

Use Cases

The Lifecycle event for this integration begins at Collibra, where Collibra Issues may be created within the Collibra Platform. Whether this issue will be transferred to ServiceNow will depend on the Issue Type. The Issue type will also determine whether this issue will be transferred to ServiceNow as either an Incident or a Request ticket.

This integration features a centralized configuration asset, which allows to create or modify attributes required by the integration to function. This allows manipulating configuration details dynamically, without having to change any files within the integration and without restarting the integration to simply apply changes. Any Collibra Issue Type can be used by being defined within the configuration asset. This Issue type will then simply require a few custom attributes to be attached.

Once the Issue is created on the Collibra Platform, the integration will detect the newly created issue and begin the process of creating the issue as either an Incident or Request on ServiceNow. Once the Issue is created successfully on ServiceNow, the integration will update the Collibra Issue with more ServiceNow details. Such details include Status, Assignee, Caller, Direct Link to ServiceNow, Ticket Type, Impact, and Urgency.

Elements in Scope

When modifying a ServiceNow Incident/Request from Collibra, the integration allows the following details to be updated:

  • Name
  • Description
  • Priority (Impact and Urgency)
  • Comments

When modifying a ServiceNow Incident/Request to Collibra, the integration will synchronize details such as:

  • Description
  • Status
  • Assignee
  • Caller
  • Priority (Impact and Urgency)
  • Additional Comments

Closing an Incident/Request from Collibra would simply involve changing the issue status within the Collibra platform.

Closing an Incident/Request from ServiceNow would require the status of the Incident/Request to be changed to the predefined status configured within the Configuration Asset in Collibra.

To receive support on this item, you can engage our Professional Services team or post any questions in the Data Citizens Community.

Media

More details

Release Notes
  • Feature Request change for multiple values for attributes ‘Close Incident State’ and ‘Close Request State’ in the Configuration Asset

Compatibility
  • Spring Boot Framework
  • Eclipse IDE
  • Collibra Cloud
  • Collibra 5.7.5 and newer
Dependency
  • Java Runtime Environment 1.8
  • Spring Boot Integration Library
License and Usage Requirements
  • Collibra Catalog
  • ServiceNow

Release History

Version 1.0.2
July 31, 2022
Release Notes
  • Updated CMA file with workflows

Compatibility
  • Spring Boot Framework
  • Eclipse IDE
  • Collibra Cloud
  • Collibra 5.7.5 and newer
Dependency
  • Java Runtime Environment 1.8
  • Spring Boot Integration Library
License and Usage Requirements
  • Collibra Catalog
  • ServiceNow
Version 1.0.1
July 30, 2022
Release Notes
  • Added Requestor Email to ServiceNow
  • Integration Library updated to v1.1.8
  • Docker Package Release
  • Configuration Asset Import Excel Sheet
  • Optimizations
Compatibility
  • Spring Boot Framework
  • Eclipse IDE
  • Collibra Cloud
  • Collibra 5.7.5 and newer
Dependency
  • Java Runtime Environment 1.8
  • Spring Boot Integration Library
License and Usage Requirements
  • Collibra Catalog
  • ServiceNow
Version 1.0.0
July 27, 2022
Release Notes

Initial release with Docker image added.

Main features:

  • Synchronizes Collibra to ServiceNow
  • Synchronizes ServiceNow to Collibra
Compatibility
  • Spring Boot Framework
  • Eclipse IDE
  • Collibra Cloud
  • Collibra 5.7.5 and newer
Dependency
  • Java Runtime Environment 1.8
  • Spring Boot Integration Library
License and Usage Requirements
  • Collibra Catalog
  • ServiceNow

The following terms shall apply to the extent you receive the source code to this offering.

Notwithstanding the terms of the Binary Code License Agreement under which this integration template is licensed, Collibra grants you, the Licensee, the right to access the source code to the integrated template in order to copy and modify said source code for Licensee’s internal use purposes and solely for the purpose of developing connections and/or integrations with Collibra products and services.

Solely with respect to this integration template, the term “Software,” as defined under the Binary Code License Agreement, shall include the source code version thereof. Except with respect to the foregoing, all remaining terms of the Binary Code License Agreement shall apply to the license of integration template hereunder.

Reviews

Rating
Leave a review