Xanadu |
- Xanadu Patch 3
- Now Assist in
Conversational
Spokes
-
Use 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.
Install 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.
- Send and receive messages in an Avro format with Stream Connect
- Import 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.
- Track incoming requests for SOAP and REST APIs, and URL Export
- View 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].
- Enable parallel loading in custom (load by script) type data sources
- Use 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.
- CyberArk credential storage integration Use the CyberArk Digital Vault to store and access your OAuth 2.0 credentials
- Use 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.
- Make outbound REST and SOAP calls through a MID Server using mTLS
- Store 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.
- Use the Personal Authentication dashboard
- Use your personal credentials to connect to third-party integrations. View, authenticate, revoke, and renew your personal authentications through a simplified, consolidated interface.
- Enhancements to the external trigger endpoints
-
Generate an endpoint for webhooks in the third-party applications that support OAuth 2.0 authentication. The endpoint enables webhooks to connect with your ServiceNow instance.
Generate
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.
- Automatically generate a JSON payload for the JSON Builder step
- Enter a JSON payload into the step's script editor to automatically de-serialize the payload into structured input.
- Enhanced OpenAPI step
- Choose 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.
|
Yokohama |
- Stream Connect for Apache Kafka alerting
-
- 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.
- 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.
- 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.
- View producer statistics in the Stream Connect dashboard
- Get 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.
- Check data usage in the Stream Connect dashboard
- View 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.
- Use error evaluation with Data Stream actions
- Catch 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.
- View connection aliases in integration actions
- Edit, 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.
|
Zurich |
- Generate the parsing phase for REST-based Data Stream actions
- Automatically 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.
- Stream Connect enhancements
-
- Use a MID Server cluster, instead of a single MID Server for message replication. 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.
- In the Kafka subscription record, 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.
- 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.
- View alerts in the Stream Connect dashboard
- Get detailed information about alerts, including their severity level, state, type, and the affected entity in the Stream Connect dashboard.
- Test connection aliases directly from configuration templates
- For 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.
- Support for PowerShell version 6.0 or later in the PowerShell step
- Enable 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.
- Use WS-Security in a SOAP step on a MID Server
- Enable a WS-Security policy in a SOAP step running on a MID Server.
- Delay parallel loading in custom (load by script) data sources
- Configure 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.
- Spoke-specific AI agents
- AI agents that implement different agentic workflows are available for various spokes. Use these spoke-specific AI agents to execute agentic workflows.
- Save draft, publish, update external trigger definition, and support domain separation
- The 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.
- Create and manage external event sources
- Define and manage custom trigger definitions after creating external event sources.
|