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

ServiceNow Bidirectional Collibra Integration (Python)

Published by: Collibra Marketplace
Latest version: 1.0.0
Released: October 16, 2024
Contact Publisher
PackageDocumentation
Community Offering

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

Overview

Community Offerings” are offerings published by third parties or Collibra within the Collibra Marketplace community.  Community Offerings are free and made available “as is” by Collibra.  Your master commercial agreement with Collibra for the Collibra Service DOES NOT apply to your use of the Community Offerings (including any warranties, support services and service levels referenced therein).   Your use of Community Offerings is subject to the Collibra Marketplace License Agreement, as may be modified from time to time by Collibra.  Collibra encourages users to seek assistance for Community Offerings from peers and other Data Citizens via the Collibra Community platform.

Overview

ServiceNow is a cloud-based platform designed to streamline enterprise operations by managing digital workflows, particularly in IT Service Management (ITSM). It is widely used for resolving internal IT issues, offering a robust system for managing service incidents.

The goal of this ServiceNow Bidirectional Collibra Integration is to synchronize Collibra Issues with ServiceNow Incidents, ensuring seamless communication between both platforms. Key information such as Name, Description, Status, Caller, Assignee, and Comments is synchronized bidirectionally. Additionally, the integration includes an Operating Model, which, once imported into your Collibra instance, will automatically generate all necessary custom prerequisites for proper synchronization.

Use Cases

The integration lifecycle can begin in either Collibra or ServiceNow. When a Collibra Issue is created within the Collibra Platform, it can be automatically transferred to ServiceNow as an incident. Similarly, if an incident is created in ServiceNow, the integration will automatically generate a corresponding Issue in Collibra.

This bidirectional synchronization ensures that updates in either system—such as changes to the issue status, comments, or assignee information—are reflected in the other platform. Both systems remain aligned throughout the issue resolution process, regardless of where the lifecycle begins.

The integration offers flexible configuration options for status synchronization, allowing users to control when and how statuses are synced based on the direction of the sync. For example, if a Collibra Issue is created with the status “New,” no ServiceNow Incident will be created until the status changes to “Accepted.” Similarly, this can be configured for synchronization from ServiceNow to Collibra. Custom status mapping can also be defined within the configuration Asset for precise control over how statuses between the two platforms align.

In the configuration Asset, you can specify Assets with which Asset Types and Domain ID should be synchronized between Collibra and ServiceNow.

  • If an asset is created in Collibra, a corresponding ServiceNow Incident will be created, and a Caller will be assigned. This Caller can be configured within the configuration Asset.

  • Conversely, if an incident is created in ServiceNow, when the corresponding asset is created in Collibra, the Assignee of the incident will be updated. The Assignee can also be specified within the configuration Asset, ensuring the correct assignment of responsibility across both platforms.

Media

More details

Release Notes

Initial release

Compatibility
  • Collibra Data Intelligence Cloud
Dependency
  • python 3.11+
License and Usage Requirements

Reviews

Rating
Leave a review