Differences

This shows you the differences between two versions of the page.

--- general:apps:appstoreconnect:releasenotes [2024/01/26 10:20] – su
+++ general:apps:appstoreconnect:releasenotes [2024/03/19 11:35] – su
@@ Line 2: / Line 2: @@
 This page describes the release notes for [[https://appstore.intelligentplant.com/Home/AppProfile?appId=a73c453df5f447a6aa8a08d2019037a5|App Store Connect]]. Your App Store Connect will automatically download the update. You can configure the update schedule for your App Store Connect by following the instructions available [[https://appstore.intelligentplant.com/wiki/doku.php?id=data_core:app_store_connect_updates|here]].
+==== 2024-03 ====
+Release Date: 2024-03-22
+Build Number: 3.2.20136
+This release brings the following changes:
+General:
+  * ''[Enhancement]'' General layout improvements for the App Store Connect UI, including a better experience on smaller screen devices.
+  * ''[Enhancement]'' Layout improvements to the configuration UI for data sources, event sources and event sinks. It is now easier to navigate between setting categories and apply filters to locate the setting(s) that you are looking for.
+  * ''[Enhancement]'' Layout improvements to the data stream UI. You can quickly switch between the latest observations and the rule definitions using a tabbed view.
+  * ''[Enhancement]'' Improvements to relative timestamp parsing in data queries. In addition to using ''*'' as a placeholder for the current time, it is now also possible to specify a number of additional relative time origin keywords, including the start of the current hour, day, week, month and year. The time zone for the relative time origin can be specified using the ''tz'' query string parameter or ''X-TimeZone'' request header on any API call. The time zone is specified using the IANA time zone database format (e.g. ''America/New_York'') or the Microsoft time zone identifier (e.g. ''Eastern Standard Time'').
+    * Timestamp parsing improvements have been made possible by delegating parsing to Intelligent Plant's [[https://github.com/intelligentplant/IntelligentPlant.Relativity|Relativity]] library.
+  * ''[Fix]'' Fixes an issue where clicking on a link in the UI to view details for a tag or script tag was not always able to load the details page. This was caused by an issue with the way the UI was handling some encoded names/IDs.
+  * ''[Fix]'' Fixes an issue where script tags that were triggered by snapshot value changes in referenced tags would not trigger if the referenced tag was another script tag.
+  * ''[Fix]'' Renaming a source or destination tag used in a data stream tag mapping now correctly removes the last observation for the old mapping from the UI.
+Azure Event Hub/IoT Hub Driver:
+  * ''[Enhancement]'' When parsing ad hoc JSON payloads, the consumer driver now supports parsing the payload using custom JavaScript. The script is invoked for every incoming message, but can opt to pass the payload onto the default parser. This allows for more complex parsing scenarios than the default parser can handle.
+IP Historian/Edge Historian Driver:
+  * ''[Enhancement]'' When configuring a linked interface tag for an IP Historian tag, it is now possible to specify the direction of the link (i.e. whether the linked tag is a source or destination for the IP Historian tag).
+  * ''[Enhancement]'' When configuring an IP Historian data stream rule, you can choose if the rule is an ingress rule or an egress rule. The interface tag link direction for IP Historian tags is used to determine if the tag supports ingress or egress.
+  * ''[Enhancement]'' An automatic egress rule can be configured for IP Historian data sources, in addition to the existing automatic ingress rule.
+  * ''[Enhancement]'' The publish intervals for automatic ingress and egress rules are now configuraable via driver settings.
+  * ''[Enhancement]'' Improvements to the in-memory tag definition cache.
+MQTT Consumer Driver (alpha package only):
+  * ''[Enhancement]'' New preview driver for receiving messages from MQTT brokers supporting all versions of MQTT up to and including v5.0. The existing legacy MQTT driver does not support MQTT 5.0.
+MQTT Server Driver (alpha package only):
+  * ''[Enhancement]'' New preview driver that runs an MQTT broker, allowing external clients to publish messages that are converted into tag values.
+    * The driver supports the same ad hoc JSON parsing rules as the Azure Event Hub and RabbitMQ drivers.
+    * The MQTT broker is for ingress only; it does not allow clients to subscribe to receive value changes or messages from other Data Core sources.
+OPC UA Driver:
+  * ''[Enhancement]'' Adds support for writing tag values.
+    * Writing array values is not currently supported.
+  * ''[Enhancement]'' Asset model nodes and tags now include the access permissions that the driver has on the tag or node.
+  * ''[Enhancement]'' Server certificates that fail validation are now logged so that the certificate can be inspected and trusted if required.
+  * ''[Enhancement]'' Client certificates no longer need to have a trusted root certificate to be used for client authentication. This simplifies the use of self-signed client certificates.
+RabbitMQ Driver:
+  * ''[Enhancement]'' When parsing ad hoc JSON payloads, the consumer driver now supports parsing the payload using custom JavaScript. The script is invoked for every incoming message, but can opt to pass the payload onto the default parser. This allows for more complex parsing scenarios than the default parser can handle.
 ==== 2024-01 ====