| \n\nXanadu\n\n | \n\n- **Now Assist in Conversational Spokes**\n\nUse Now Assist in Conversational Spokes to utilize the conversational ability of Integration Hub Spoke actions. Now Assist in Conversational Spokes offers generative AI capabilities to make spoke actions conversational. With this, you can perform business actions and automate business workflows through conversational interface.\n\nInstall Now Assist for Conversational Spokes plugin and start utilizing the conversational ability of the Look up User spoke action in Microsoft Active Directory v2 spoke. You can call this action from a conversational interface like Now Assist.\n\n\n- **[Send and receive messages in an Avro format with Stream Connect](https://www.servicenow.com/docs/access?context=schema-management&family=xanadu&ft:locale=en-US)**\n\nImport and create Avro schemas to store in the Stream Connect Schemas \\[stream\\_connect\\_schema\\] table. Stream Connect producers and consumers use the schemas to convert plain-text JSON messages into an Avro binary format and back. Using an Avro format can reduce the size of the payload and simplify your integration to your local Apache Kafka instance.\n\n- **[Track incoming requests for SOAP and REST APIs, and URL Export](https://www.servicenow.com/docs/access?context=integrationhub-usage-dashboard&family=xanadu&ft:locale=en-US)**\n\nView the data egress details in the enhanced Usage dashboard. Using the dashboard, you can track the data egress usage per source over time. This information is presented in a line chart and, if needed, you can view the amount of data transfer by source on any given date within the specified date range. The dashboard retrieves data from the Data Egress Count table \\[data\\_egress\\_count\\].\n\n- **[Enable parallel loading in custom \\(load by script\\) type data sources](https://www.servicenow.com/docs/access?context=custom-type-data-source&family=xanadu&ft:locale=en-US)**\n\nUse a script to partition data into smaller sections, then load the sections in parallel. Parallel loading can enable your integrations to finish faster and reduce the impact on other tasks.\n\n- **[CyberArk credential storage integration](https://www.servicenow.com/docs/access?context=c_CyberArkCredStorageIntegrate&family=xanadu&ft:locale=en-US) Use the CyberArk Digital Vault to store and access your OAuth 2.0 credentials**\n\nUse the ServiceNow® MID Server to access your OAuth 2.0 credentials stored on the CyberArk Digital Vault. The MID Server uses this information to generate OAuth 2.0 tokens for client credentials grant type that are then used to make REST API calls to the third-party server.\n\n- **[Make outbound REST and SOAP calls through a MID Server using mTLS](https://www.servicenow.com/docs/access?context=mtls-mid-server&family=xanadu&ft:locale=en-US)**\n\nStore mTLS password and certificate information on the instance, in a vault, or in a configuration file. The MID Server uses this information to make outbound REST and SOAP calls with the mTLS protocol.\n\n- **[Use the Personal Authentication dashboard](https://www.servicenow.com/docs/access?context=personal-auth-dashboard&family=xanadu&ft:locale=en-US)**\n\nUse your personal credentials to connect to third-party integrations. View, authenticate, revoke, and renew your personal authentications through a simplified, consolidated interface.\n\n- **[Enhancements to the external trigger endpoints](https://www.servicenow.com/docs/access?context=generate-endpt-oauth2&family=xanadu&ft:locale=en-US)**\n\nGenerate an endpoint for webhooks in the third-party applications that support [OAuth 2.0 authentication](https://www.servicenow.com/docs/access?context=generate-endpt-oauth2&family=xanadu&ft:locale=en-US). The endpoint enables webhooks to connect with your ServiceNow instance.\n\nGenerate the endpoints by updating the base system external event sources on your ServiceNow instance. After that, you can configure the endpoint on the third-party application and enable it to send a webhook to the ServiceNow instance to execute a flow. Based on the authentication type that the third-party system supports, you can generate a hash, secret, or token, or add roles or a user to the external event source. Finally, you generate the endpoint that you can use on the third-party system webhook.\n\n- **[Automatically generate a JSON payload for the JSON Builder step](https://www.servicenow.com/docs/access?context=json-build-step-action-designer&family=xanadu&ft:locale=en-US)**\n\nEnter a JSON payload into the step's script editor to automatically de-serialize the payload into structured input.\n\n- **[Enhanced OpenAPI step](https://www.servicenow.com/docs/access?context=open-api-step-action-designer&family=xanadu&ft:locale=en-US)**\n\nChoose to import an OpenAPI specification or a Postman Collection of a third-party outbound REST web service for building an integration. The OpenAPI step is now enhanced to support Postman API collections and is renamed as **OpenAPI/Postman step**.\n\n\n |
| \n\nYokohama\n\n | \n\n- **[Check data usage in the Stream Connect dashboard](https://www.servicenow.com/docs/access?context=stream-connect-dashboard&family=yokohama&ft:locale=en-US)**\n\nView total data usage and data usage per month and topic with the Stream Connect dashboard. Data usage history is available for the last 12 complete months plus the current month.\n\n\n - **[View producer statistics in the Stream Connect dashboard](https://www.servicenow.com/docs/access?context=stream-connect-dashboard&family=yokohama&ft:locale=en-US)**\n\nGet detailed information about Stream Connect producers and their performance, including a producer’s status and type, the number of bytes and messages produced to a topic, and producer data trends over time, in the Stream Connect dashboard.\n\n\n - **[Stream Connect for Apache Kafka alerting](https://www.servicenow.com/docs/access?context=stream-connect-alert&family=yokohama&ft:locale=en-US)**\n - Get alerts for your Stream Connect integrations. Stream Connect uses both active and scheduled monitoring to detect events across multiple Stream Connect components. If an issue is detected, an alert is created, and a message is logged to the Stream Connect Log.\n - Specify alert thresholds by configuring alerting properties. For example, you can specify a maximum amount of time to process the current message queue. If the estimated processing time exceeds your specified time, an alert is generated.\n - Receive alert notifications via email, SMS, or the ServiceNow® mobile app. Notifications contain detailed alert information, including the alert number, level, and a description. You can configure notification settings based on alert types, severity, and user preferences.\n- **[Use error evaluation with Data Stream actions](https://www.servicenow.com/docs/access?context=data-stream-actions&family=yokohama&ft:locale=en-US)**\n\nCatch step errors and specify error behavior for each step in a Data Stream action. Create your own error conditions by specifying when an action returns an error state and the status codes and messages they return.\n\n- **[View connection aliases in integration actions](https://www.servicenow.com/docs/access?context=managing-connections-integration-hub&family=yokohama&ft:locale=en-US)**\n\nEdit, configure, and create connection aliases in the Action Properties section of actions in ServiceNow® Workflow Studio. View connection error details for connection aliases that are not set up or configured.\n\n\n |
| \n\nZurich\n\n | \n\n- **[View alerts in the Stream Connect dashboard](https://www.servicenow.com/docs/access?context=stream-connect-dashboard&family=zurich&ft:locale=en-US)**\n\nGet detailed information about alerts, including their severity level, state, type, and the affected entity in the Stream Connect dashboard.\n\n\n - **[Generate the parsing phase for REST-based Data Stream actions](https://www.servicenow.com/docs/access?context=data-stream-actions&family=zurich&ft:locale=en-US)**\n\nAutomatically configure the splitter step, script parser step, and outputs for REST-based Data Stream actions. The **Test REST step** functionality in REST-based Data Stream actions executes a request to the configured REST endpoint, analyzes the response payload, and automatically sets up the parsing and output components.\n\n- **[Stream Connect enhancements](https://www.servicenow.com/docs/access?context=stream-connect-apache-kafka&family=zurich&ft:locale=en-US)**\n - Use a MID Server cluster, instead of a single MID Server for [message replication](https://www.servicenow.com/docs/access?context=stream-connect-message-replication&family=zurich&ft:locale=en-US). With a MID Server cluster, if one of the MID Servers fails, the other MID Servers can share the load of the failed MID Server.\n - In the [Kafka subscription record](https://www.servicenow.com/docs/access?context=kafka-subscriptions-statistics&family=zurich&ft:locale=en-US), view the estimated time required for a consumer to process the current queue. The subscription record also links to the consumer record, so that you can see which consumer is processing the queue.\n - Specify a compression format for Stream Connect producers with the **com.glide.kafka\\_producer.compression\\_type** system property. Stream Connect supports the GZIP and LZ4 compression formats.\n- **[Test connection aliases directly from configuration templates](https://www.servicenow.com/docs/access?context=test-alias-configuration-template&family=zurich&ft:locale=en-US)**\n\nFor aliases using a configuration template, you can configure a Test Action field. This field enables you to test a connection from within the Action Properties section of actions in Workflow Studio.\n\n- **[Support for PowerShell version 6.0 or later in the PowerShell step](https://www.servicenow.com/docs/access?context=powershell-step-action-designer&family=zurich&ft:locale=en-US)**\n\nEnable the PowerShell step to use a newer version of PowerShell by adding the MID Server property **mid.property.ihub.prefer\\_powershell6Plus** and setting it to `true`.\n\n- **[Use WS-Security in a SOAP step on a MID Server](https://www.servicenow.com/docs/access?context=soap-step-action-designer&family=zurich&ft:locale=en-US)**\n\nEnable a WS-Security policy in a SOAP step running on a MID Server.\n\n- **[Delay parallel loading in custom \\(load by script\\) data sources](https://www.servicenow.com/docs/access?context=custom-type-data-source&family=zurich&ft:locale=en-US)**\n\nConfigure a delay for parallel loading in custom data sources. When the data source is called, the parallel loading is scheduled to run after the configured amount of time.\n\n- **Spoke-specific AI agents**\n\nAI agents that implement different agentic workflows are available for various spokes. Use these spoke-specific AI agents to execute agentic workflows.\n\n- **[Save draft, publish, update external trigger definition, and support domain separation](https://www.servicenow.com/docs/access?context=create-saved-external-trigger&family=zurich&ft:locale=en-US)**\n\nThe external trigger definition is updated to match the trigger builder so that the external trigger definition supports the saving of draft, publishing, updating external trigger definition, and supporting domain separation.\n\n- **[Create and manage external event sources](https://www.servicenow.com/docs/access?context=manage-external-event-sources&family=zurich&ft:locale=en-US)**\n\nDefine and manage custom trigger definitions after creating external event sources.\n\n\n |
| \n\nAustralia\n\n | \n\n- **[Stream Producer](https://www.servicenow.com/docs/access?context=stream-producer&family=australia&ft:locale=en-US)**\n\nAutomatically stream changes from ServiceNow tables to Kafka topics with Stream Producer. Stream Producer uses change data capture \\(CDC\\) technology to capture inserts, updates, and deletes on selected tables. The captured changes are formatted as messages and sent to a Kafka topic, enabling real-time data synchronization with external applications.\n\n- **[Stream Producer schemas](https://www.servicenow.com/docs/access?context=schema-management&family=australia&ft:locale=en-US)**\n\nStream Producer supports the Avro serialization format for message payloads. When using an Avro format, Stream Producer uses the selected table's auto-generated schema to convert CDC payloads to Avro before sending them to Kafka.\n\n\n - **[OAUTHBEARER authentication for Stream Connect message replication](https://www.servicenow.com/docs/access?context=hla-data-input-kafka-credentials&family=australia&ft:locale=en-US)**\n\nAuthenticate using OAUTHBEARER as part of the SASL credential framework for Stream Connect message replication. OAUTHBEARER authentication lets Stream Connect administrators meet customer requirements, improve security, and align with existing OAuth capabilities on the platform, enabling seamless integration with Kafka environments that require advanced authentication.\n\n\n - **[Stream Connect Dashboard updates](https://www.servicenow.com/docs/access?context=stream-connect-dashboard&family=australia&ft:locale=en-US)**\n - The Topics menu displays topic aliases, Hermes topics, and Direct Kafka topics.\n - The **Data usage** tab shows data for the Hermes cluster or the Direct Kafka cluster. Use the **Kafka Cluster** list to select which cluster data to display.\n - The Consumers and Producers menus reference topic aliases instead of Hermes topics.\n\n - **[Use Direct Kafka to integrate your on-premise ServiceNow instance with your local Kafka environment](https://www.servicenow.com/docs/access?context=direct-kafka&family=australia&ft:locale=en-US)**\n\nConfigure a custom Kafka connection to enable your on-premise instance to connect directly to your local Kafka environment.\n\n- **[Create topic aliases for Stream Connect topics](https://www.servicenow.com/docs/access?context=manage-topic-alias&family=australia&ft:locale=en-US)**\n\nUse topic aliases to simplify topic management in Stream Connect. A topic alias is a unique topic name that can be connected to any underlying Hermes or Direct Kafka topic. A topic alias can be moved to different instances and, wherever they’re moved, connected to an underlying topic.\n\n- **[View the Remote Process Sync Dashboard](https://www.servicenow.com/docs/access?context=remote-process-sync-dashboard&family=australia&ft:locale=en-US)**\n\nView detailed statistics and monitor the health of your Remote Process Sync \\(RPS\\) integrations. The Remote Process Sync Dashboard provides real-time visibility into key metrics, including records processed, queue sizes, processing times, and system status. Use this dashboard to identify issues, track performance trends, and promote smooth operation of your RPS integrations.\n\n- **[Produce messages to Hermes via a MID Server](https://www.servicenow.com/docs/access?context=MID-hermes-API&family=australia&ft:locale=en-US)**\n\nSend message payloads to Hermes with MID script includes.\n\n- **[View usage metrics for Direct Kafka](https://www.servicenow.com/docs/access?context=direct-kafka-usage-metrics&family=australia&ft:locale=en-US)**\n\nTrack data usage between your instance and Direct Kafka systems. The Direct Kafka Usage metrics table provides administrators with visibility into data transfer volumes for bytes produced and consumed. View metrics aggregated by hour, day, or month at the cluster and topic level. Usage records are automatically retained for 13 months.\n\n- **[Use the read-only role for Stream Connect](https://www.servicenow.com/docs/access?context=stream-connect-apache-kafka-roles&family=australia&ft:locale=en-US)**\n\nUse the new read-only role for Stream Connect to grant users view-only access to Stream Connect resources. Users with this role can view Stream Connect configurations and runtime statistics across all related modules, but can’t create, modify, or delete any Stream Connect settings.\n\n- **[View logs for Stream Connect producers](https://www.servicenow.com/docs/access?context=producer-statistics&family=australia&ft:locale=en-US)**\n\nGet detailed log information for producers in the Stream Connect logs. Use the **glide.ih.kafka.producer.message\\_bytes\\_to\\_log** property to specify how much of the message to display in the logs.\n\n- **[Configure alert thresholds for undelivered messages in Stream Connect](https://www.servicenow.com/docs/access?context=sc-alert-properties&family=australia&ft:locale=en-US)**\n\nSet alert thresholds for undelivered messages based on how long a topic has gone without receiving new messages. Use this configuration to trigger INFO, WARNING, or CRITICAL alerts when message delivery stops for a specified period.\n\n- **[Configure alert thresholds for unprocessed messages in Stream Connect](https://www.servicenow.com/docs/access?context=sc-alert-properties&family=australia&ft:locale=en-US)**\n\nSet alert thresholds for messages that remain unprocessed in a topic. You can trigger alerts based on how long messages sit in a topic without being consumed, helping to identify lagging or failing consumers.\n\n- **[Get metadata information for Stream Connect consumers](https://www.servicenow.com/docs/access?context=configure-script-consumer&family=australia&ft:locale=en-US)**\n\nView the partition, offset, datacenter ID, and timestamp epoch for the script consumer and Kafka Message trigger.\n\n- **[View message timestamps in the Stream Connect script consumer](https://www.servicenow.com/docs/access?context=configure-script-consumer&family=australia&ft:locale=en-US)**\n\nGet the message timestamp in the script consumer as a UTC time-zone string. You can use the UTC time-zone string to convert the timestamp to a **GlideDateTime** object.\n\n- **[Use an error subflow template to create your own error subflows in Remote Process Sync](https://www.servicenow.com/docs/access?context=getting-started-with-remote-process-sync&family=australia&ft:locale=en-US)**\n\nCopy and modify the RPS Error Subflow Template to create error subflows. The template enables you to select notification methods for when the Inbound and Outbound States are errored.\n\n- **Specify attachment details in Remote Process Sync actions**\n\nSpecify the max attachment size and allowed attachment extensions in the [Identify New Attachments action](https://www.servicenow.com/docs/access?context=identify-new-attachments-action&family=australia&ft:locale=en-US) and the [Get Attachment Metadata for Local Record action](https://www.servicenow.com/docs/access?context=get-attachment-metadata-local-record-action&family=australia&ft:locale=en-US).\n\n- **Use a new retry policy for Remote Process Sync actions**\n\nRetry failed requests at specified intervals with the RPS Push Attachment Policy. This policy works with the [Identify New Attachments action](https://www.servicenow.com/docs/access?context=identify-new-attachments-action&family=australia&ft:locale=en-US) and the [Get Attachment Metadata for Local Record action](https://www.servicenow.com/docs/access?context=get-attachment-metadata-local-record-action&family=australia&ft:locale=en-US).\n\n- **[SASL authentication support for Apache Kafka connections](https://www.servicenow.com/docs/access?context=hla-data-input-kafka-credentials&family=australia&ft:locale=en-US)**\n\nConfigure SASL authentication for your Apache Kafka connections with support for SASL\\_SSL and SASL\\_PLAINTEXT security protocols. Kafka credentials now support multiple SASL mechanisms: PLAIN- SCRAM-SHA-256, SCRAM-SHA-512.\n\n\n |
\n