Knowledge Discovery 25.2.1
25.2 Release Notes

# ServiceNow Connector

## 25.2.0

There were no new features or resolved issues in this release.

## 25.1.0

There were no new features or resolved issues in this release.

## 24.4.0

There were no new features or resolved issues in this release.

## 24.3.0

There were no new features or resolved issues in this release.

## 24.2.0

There were no new features or resolved issues in this release.

## 24.1.0

### New Features

- The connector supports ServiceNow instances hosted on domains other than `service-now.com`. To specify the domain that hosts your ServiceNow instance, set the new configuration parameter `ServiceNowDomain`.

### Resolved Issues

There were no resolved issues in this release.

## 23.4.0

### New Features

- The `synchronize` action supports a new optional parameter, `identifiers`. The `identifiers` parameter accepts a comma-separated list of document identifiers that specifies the documents to synchronize.

### Resolved Issues

There were no resolved issues in this release.

## 23.3.0

There were no new features or resolved issues in this release.

## 23.2.0

### New Features

- IDOL documents that the connector creates to represent attachments now include all of the metadata from their parent record, in a document field named `SN_PARENT`. To add only some of the parent metadata, you can set the new configuration parameter `ParentMetadataMatchesRegex`, which allows you to choose metadata fields that match a regular expression.
- The configuration parameters `RecordContentFields` and `MetadataMatchesRegex` have been added. `RecordContentFields` allows you to convert large metadata fields into document content pages (when the IDOL document has no associated file). `MetadataMatchesRegex` can be used to discard metadata fields before documents are ingested.

### Resolved Issues

- An issue with paging meant that the connector did not retrieve all of the records that were present in ServiceNow.
- The connector could return an error, "Failed to get record", when a user attempted to a view a record.
- The PurgeDatastore action, or Purge Datastore button in the NiFi advanced configuration interface, silently failed and did not remove any data from the connector's datastore. This issue affected both internal datastores and external ODBC datastores.

### Notes

- Due to an issue with the storage of OAuth tokens in previous versions of the connector, you might need to obtain OAuth tokens again. After upgrading to this version of ServiceNow Connector, re-run the OAuth guided setup wizard (in NiFi) or the OAuth configuration tool (for the standalone connector).

Copyright 2025 Open Text
Version 25.2.1 | Last updated April 2025

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery 25.2.1

Topic Title: ServiceNow Connector