v4.4.1
27 Mar 2024
Last updated
27 Mar 2024
Last updated
| Change Type | Name | Description |
|---|---|---|
| Change Type | Description |
|---|---|
| Change Type | Description |
|---|---|
| Change Type | Description |
|---|---|
New
Bring data from REST API into your App.
New
Lightweight, self-healing, frictionless messaging Agents.
New
Read and update Coupa invoices from within your Data Stream.
Enhancement
Support variables and standardize property names.
Enhancement
Support combining the count and delay buffer options into Count with Delay.
Enhancement
Data Stream names are auto-populated during import (when exported using v4.4.1+).
Enhancement
The "Enable Luigi Preview" feature flag, introduced in v4.3.9 for beta testing of the new Stream Host core, has been replaced with the "Enable Legacy Core" feature flag. The new, improved Stream Host core is now the default in all new installations, in line with the recommendation made in v4.4.0.
Please reach out should you want to revert to the old core as we'd like to understand why and guide you through the process.
Feature
New Blocks added:
Visual Media Capture - enrich your events with an image or video captured using your device input.
Location Capture - capture the precise geographical coordinates of an asset or incident using your device.
ChatGPT Copilot - bring ChatGPT into your App.
Azure Copilot - bring Azure's OpenAI into your App.
Enhancement
Recommendation names are auto-populated during import (when exported using v4.4.1+).
Enhancement
Fix
When using the Image Map, clicking on a hyperlink in either Dynamic or Static content does not work - the navigation on action is not working. I can navigate to the configured action for both Dynamic and Static content in an Image Map.
Note that the Dynamic Template's Data Source and Data must be configured for dynamic content to appear at runtime.
When using the , the Time Series Chart's performance is enhanced with optimized client-side querying (v4.3.2). The new ITSCConnector interface instructs the Time Series Chart to use optimized client-side querying. Use it when building new TSC Connectors that pre-process large volumes of data and return it in buckets.