v4.4.14
1 October 2024
Integrations
Feature
Our new Meta Agent allows you to run scripts on input values and use the results in your data stream. Similar to the Metablock, the scripts can be written in languages other than C# and leverage 3rd party libraries.
Enhancement
Updated to latest NuGet package. We recommend upgrading your MySQL server to the latest version in response to medium CVE-2023-3817 security update.
Enhancement
Implement the new ITSAConnector interface and naming aligned to the Time Series Analysis block.
Common
Security
Various NuGet and NPM packages upgraded for AD, AI and DS:
Upgraded database access packages (System.Data.SqlClient, Microsoft.Data.SqlClient) to address security vulnerabilities
Updated Azure.Identity package to latest secure version
Updated Microsoft.VisualStudio.Web.CodeGeneration.Design to resolve NuGet package vulnerabilities
Enhancement
We're improving our multilingual capabilities:
Your preferred language can be entered at signup, rather than once you've logged in for the first time.
The signed out pages, where your preferred language is not known, are now available in Brazilian Portuguese, with other languages to follow.
Subscription Manager is now available in Brazilian Portuguese, with other languages to follow.
App Designer
Fix
Several issues were corrected on the Metablock:
The default functions (onDataLoaded, onDataChanged, and onValueMappingLoaded) did not execute when added to a script tag on the HTML page.
The Value Mapping was being called twice.
The Value Mapping was not optional
Fix
I created a new Recommendation, but when I opened the Version blade I noticed the title was blank. The title of a new Recommendation default to "Initial Version".
Fix
I am the owner of a Recommendation, but I cannot view it's timeline - yet my colleague with Run Access can. Users with design access are able to view a Recommendation's timeline.
Stream Host
Fix
I accidentally used the incorrect password on an MQTT agent and published the data stream. The stream did not start due to the connection error on the agent, but I noticed the agent continues attempting to connect to the MQTT broker. The Stream Host ensures that if a data stream fails to start or is unpublished, all of that stream's agents (whose Create() methods have already run) are destroyed.
Last updated
Was this helpful?