Integration Hub release notes
Summarize
Summary of Integration Hub Release Notes Washington DC
The Washington DC release of ServiceNow® Integration Hub enhances workflow automation by enabling integration of your instance data with external systems. Key features introduced streamline processes and improve security and connectivity options.
Show less
Key Features
- Stream Connect Enhancements: Utilize Stream Connect message replication to seamlessly replicate data between your local Apache Kafka environment and ServiceNow, eliminating the need for third-party tools.
- OAuth 2.0 Integration: Connect with on-premise OAuth authorization servers through a MID Server for secure token requests, facilitating integration with third-party services.
- Code Signing Security: Enhanced multi-layer caller inspection requires valid certificates for each layer that accesses the ECC queue, increasing security for record updates.
- OpenAPI Step Improvements: New functionalities include saving request responses, configuring retry policies, modifying resource paths, and utilizing advanced schema properties.
Key Outcomes
With the Washington DC release, ServiceNow customers can expect improved integration capabilities, enhanced security measures, and streamlined workflows. The enhancements simplify data management and improve the reliability of external integrations, enabling organizations to automate processes more effectively.
The ServiceNow® Integration Hub application extends the ServiceNow® Flow Designer workflow automation capabilities by enabling you to integrate your instance data with data in external systems. Integration Hub was enhanced and updated in the Washington DC release.
Integration Hub highlights for the Washington DC release
- Simplify your Stream Connect integrations by using Stream Connect message replication to replicate data from your local Apache Kafka environment.
- Use the improved OpenAPI step for integrating with third-party REST web services.
- Authenticate the OAuth client credential grant type with the on-premise authorization server, and integrate with the corresponding resource server after successful authentication.
- Use the code signing feature that has been enhanced with multi-layer caller inspection of records in the call stack to be signed before going to the ECC queue.
See Integration Hub for more information.
New in the Washington DC release
- Stream Connect for Apache Kafka Enhancements
- Use Stream Connect Message Replication to replicate data between your local Apache Kafka environment and ServiceNow. With Stream Connect Message Replication, you no longer need a third-party replicator and can manage message replications from your ServiceNow instance.
- Use Stream Connect Message Replication to enable a MID Server to create the access certificates required to connect to the Hermes Messaging Service. The MID Server can automatically generate the necessary certificates, so you don't need to configure them manually.
- Send messages with an updated Kafka Producer step. Select a topic from a drop-down list and configure values for the message header.
- OAuth 2.0 credentials
- Connect with an on-premise third-party OAuth authorization server that resides behind a firewall through a MID Server that sends the request for an OAuth token on behalf of your ServiceNow instance. You can use this functionality when you create an application registry for a third-party OAuth provider and in the form, set the Grant type as Client Credentials.
- Increased security in code signing with multi-layer caller inspection
- The code signing feature has been enhanced with multi-layer caller inspection of records. Multiple layers can call each other before a record or entity can update the ECC queue table. Now, each layer must have a valid certificate and validated before the MID server accesses the record or entity. The ServiceNow platform provides a property that enables you to inspect three caller layers by default.
Changed in this release
- Open API step enhancements
- The OpenAPI step has several improvements. You can now:
- Save the request response as an attachment record.
- Configure a retry policy to retry a request if the previous one fails or encounters any issues.
- Sync step inputs and step outputs with action inputs and action outputs. Edit step outputs if required.
- Modify the resource path, HTTP methods, query parameters, and headers of a request.
- Add or remove error mapping to an action while resetting action inputs and action outputs.
- Use oneOf and anyOf schema object properties in the schema.
- Multi-layer caller inspection of records going to the ECC queue
- Previously, there would be a single layer inspection of records or entities entering the ECC queue. Now, multiple layers calling each other must have a valid certificate and be validated before the record enters the ECC queue. By default, you can support the inspection of three layers.
Deprecations
Starting with Washington DC release, OpenAPI support in the REST step is being prepared for future deprecation. It will be hidden and no longer available for activation but will continue to be supported. For details, see the Deprecation Process [KB0867184] article in the Now Support Knowledge Base.
Activation information
Integration Hub is included in Automation Engine and is available with activation of an Automation Engine subscription package. For details, see https://www.servicenow.com/products/automation-engine.html.