Differences

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

--- general:apps:appstoreconnect:releasenotes [2023/04/28 09:36] – [2023-04] su
+++ general:apps:appstoreconnect:releasenotes [2024/05/02 07:12] (current) – 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-04 ====
+Release Date: 2024-05-03
+Build Number: 3.2.20238
+This release brings the following changes:
+General:
+  * ''[Enhancement]'' Performance improvements when applying authorization rules.
+  * ''[Enhancement]'' All data sources now support the ability to force data writes to go to snapshot or history.
+Alarm Analysis Driver:
+  * ''[Enhancement]'' Facit annotations are now treated as read-only and have had their "more info" links amended.
+Azure Event Hub/IoT Hub Driver:
+  * ''[Enhancement]'' Improvements to JSON payload parsing to support MQTT-style wildcards when including or excluding properties from the JSON document.
+CSV Driver:
+  * ''[Enhancement]'' Reduced memory usage.
+IP Historian/Edge Historian v2 Driver:
+  * ''[Enhancement]'' The tag cache can now be disabled to reduce memory usage. Tag searches will be slower when the cache is disabled.
+  * ''[Enhancement]'' The health status for a running IP Historian driver now includes the health status of the Elasticsearch cluster that the driver is connected to.
+IP Historian/Edge Historian v3 Driver:
+  * ''[Enhancement]'' Alpha package includes a preview driver for IP Historian v3.
+    * IP Historian v3 is a major update to IP Historian that requires Elasticsearch v7 or later. You must provide your own Elasticsearch cluster to use IP Historian v3.
+Met Office Driver:
+  * ''[Enhancement]'' Updated to consult the latest Met Office Data Hub (https://datahub.metoffice.gov.uk/)
+    * Supported weather plans now include: Global hourly spot, Global three hourly spot and Global daily spot.
+  * ''[Enhancement]'' Changes to how three-hourly forecast are recorded.
+  * ''[Enhancement]'' Significant Weather description accompanies Significant Weather Code - e.g. 1 : Sunny Day
+RabbitMQ Driver:
+  * ''[Enhancement]'' Improvements to JSON payload parsing to support MQTT-style wildcards when including or excluding properties from the JSON document.
+==== 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 ====
+Release Date: 2024-01-26
+Build Number: 3.2.19859
+This release brings the following changes:
+General:
+  * Miscellaneous performance improvements, in particular to data streams.
+  * All setting names in ''DataCore.settings.json'' are now case-insensitive.
+  * ''DataCore.settings.json'' now allows settings to be specified using nested JSON objects. For example, the following configuration is now valid and is equivalent to specifying a non-nested property named ''DataCore:Application:Name'':
+<code json>
+{
+  "DataCore": {
+    "Application": {
+      "Name": "My App Store Connect"
+    }
+  }
+}
+</code>
+  * The default file system-based key/value store can now buffer pending changes in memory and periodically flushes them to disk. In particular, this improves performance when the system is configured to run large numbers of script tags or in-memory buffer tags that persist values to disk. Background flush is enabled by setting the ''DataCore:DataStore:FlushInterval'' configuration setting in ''DataCore.settings.json'' to a time span value e.g. ''00:00:10'' for a 10 second flush interval.
+  * The C# script tag engine now allows compilation to be skipped for script tags built from templates. This can significantly improve startup time when using large numbers of script tags. Compilation skipping can be enabled by setting the ''DataCore:ScriptEngine:CSharp:SkipTemplateCompilation'' configuration setting in ''DataCore.settings.json'' to ''true''.
+CSV Driver:
+  * The driver now correctly applies both per-tag and per-query sample limits.
+In-Memory Buffer Driver:
+  * When configured to persist tag values, the buffer now provides a setting to specify if values should be persisted to a single data store key, or if one key per tag should be used. The latter option is the default behaviour as it mirrors the existing behaviour of the buffer. The former option can be used to reduce the number of keys that need to be read from or written to disk when using a file system-based data store, which can help to improve performance when buffering large numbers of tags.
+IP Historian/Edge Historian:
+  * Better handling of data queries that specify tags that do not exist.
+  * Performance improvement when writing large numbers of samples to the driver.
+Microsoft Azure Event Hub/IoT Hub Driver:
+  * Fixes an issue where the consumer driver was not correctly processing messages received from the Event Hub.
+Remapper Driver:
+  * Tag searches for script tags now work correctly.
+==== 2023-09 Hotfix 1 ====
+Release Date: 2023-10-02
+Build Number: 3.2.19629
+This hotfix patches the following issues:
+AVEVA OSIsoft PI/AF Drivers:
+  * Fixes an issue where all tag values returned from PI and AF queries were being assigned the current UTC time as their timestamp.
+RabbitMQ Consumer Driver:
+  * Fixes an issue in the Rabbit MQ consumer driver where messages that were sent without any custom headers could not be processed.
+==== 2023-09 ====
+Release Date: 2023-09-29
+Build Number: 3.2.19623
+This release brings the following changes:
+General:
+  * All drivers can define a startup delay to wait for before the driver will be initialised.
+  * Significant performance improvements when performing a bulk creation of tag definitions in the App Store Connect UI.
+  * Fixes a memory leak that could occur when running a driver out-of-process causing the external executable to eventually crash. This issue was typically observed when using the OPC Classic (DA/HDA/AE) driver, which needs to run in a 32-bit process.
+  * Data stream rules can now filter values that get sent to destination tags using value change, exception and compression filtering. This is a preview feature that does not currently have a configuration UI. Please contact us for more information!
+  * Updates to the latest version of the [[https://github.com/intelligentplant/AppStoreConnect.Adapters|App Store Connect adapters toolkit]]. Among other things, this update fixes issues where toolkit-based drivers could cause the App Store Connect UI to display the incorrect runtime health status for the driver.
+  * Ensures that unmanaged resources created by drivers such as TCP listeners are correctly stopped when the App Store Connect runtime is being stopped in order to apply an update.
+AVEVA Wonderware Driver:
+  * Integer-based tags now automatically provide a visualisation hint that they should be displayed using stepped lines.
+In-Memory Buffer Driver:
+  * When persisting values to disk, the buffer now ensures that values that are waiting to be trimmed are not saved.
+Microsoft Azure Event Hub/IoT Hub Driver:
+  * Significant performance and memory usage improvements.
+  * Adds the ability to batch multiple observations together into a single Azure Event Hub message, and to compress the message payload.
+Modbus Driver:
+  * Robustness improvements to handle scenarios where the Modbus device crashes.
+  * CSV mapping files now support configuring a factor and offset for a mapping. If specified, this takes precedence over the "scale low" and "scale high" columns.
+OpenTelemetry Metrics Driver:
+  * Adds min/max tags for histogram instruments.
+TCP Printer Driver:
+  * Adds settings to control if event messages are trimmed before being emitted to remove leading and trailing white space, and if event messages that consist solely of white space are emitted or discarded.
+Prometheus Driver (canary stream only):
+  * New driver for reading metrics from HTTP endpoints that use the [[https://prometheus.io/docs/instrumenting/exposition_formats/#text-based-format|Prometheus exposition format]].
+RabbitMQ Driver:
+  * Improvements to connection resiliency and telemetry.
+  * Significant performance and memory usage improvements.
+  * Adds the ability to batch multiple observations together into a single RabbitMQ message, and to compress the message payload.
@@ Line 27: / Line 221: @@
 CSV Driver:
   * Memory usage is reduced, in particular for large CSV data sets.
-  * Fix an issue where querie for best-fit or interpolated data over large numbers of raw samples could cause a lage spike in memory.
+  * Fix an issue where queries for best-fit or interpolated data over large numbers of raw samples could cause a lage spike in memory.
-  * Fix an issue where the "Maximum Raw Query Sample Count" was not being correctly applied when retrieving raw samples for aggregation.
+  * Fix an issue where the "Maximum Raw Query Sample Count" setting was not being correctly applied when retrieving raw samples for aggregation.
 IP Historian/Edge Historian