v4.4.7
25 June 2024
Integrations
Change Type | Name | Description |
---|---|---|
Enhancement | Repackaged to update the Neo4J icon. | |
Fix | Added the Azure Client DLL to resolve an error when opening the Agent's configuration. | |
Fix | Fixed the update to update not create | |
Fix | Fixed the update to update not create |
App Designer
Change Type | Description |
---|---|
Feature | New Blocks added to make your interactions with Recommendation Alerts composable:
The Recommendation Alert Form Block, introduced in v4.4.6, has been renamed Alert Form. |
Enhancement | The Metablock Block, introduced in v4.4.6, has added presentation and styling file options, which empowers designers to increase reuse while reducing complexity. |
Enhancement | The Lookup Block no longer makes multiple read calls on page load. |
Fix | I changed the data type of one of the data stream tags from a double to a string, refreshed the recommendation rule, and now the rule logic box is no longer editable. The error is appended to the data stream tags in the rule logic box to communicate the problem to the designer, e.g. "(INVALID DATA TYPE STRING)". |
Fix | I'm using a Unity v2022 model, but it doesn't load cached data when launched and there is also a zooming in/out issue. The Unity Block's cached data and zoom works as expected. |
Data Stream Designer
Change Type | Description |
---|---|
Enhancement | Notes are now distinct per version rather than per Data Stream, thus allowing the notes to track the differences between versions. |
Enhancement | We've further improved the Agent upgrade experience: the button name changes to 'Downgrade' if the Agent is on the latest version and the list of versions includes the same information as the Agent's version blade, i.e. the date it was added and the number of data streams in which it is used. |
Enhancement | We've reduced the size of the Data Stream Designer application package by decoupling the Stream Host installer download. From v4.4.7 onwards, ensure your network policy allows access to the |
Fix | I cannot upload the 'Tier 5 - Agents.zip' file even though it meets the requirements - the compressed size is 31.7 MB and the pre-compression contents are 88.2 MB. Bulk adding agents validates the 100 MB limit using the XMP file size, not the converted JSON object size. |
Stream Host
Change Type | Description |
---|---|
Fix | I've upgraded my Stream Host to v4.4 and my Data Stream that contains the Azure IoT Hub Listener Agent has errors in the log. Upgrade the Azure IoT Hub Listener Agent to v3.06, released earlier this year, with the newer version of Microsoft.Azure.Amqp.dll. |
Last updated