Various enhancements to improve the security of the software.

When the SQL Server database time stamp increases by more than 231 and you make a change to the configuration of a server, the system performs a full reload of its configuration, which may cause issues.

When using the reverse connection to FrameWorX, the requests sent to a gateway are pending and waiting for a response forever.

The Configuration point manager does not return the installation details data set (cfg:InstallationDetails) when requested from a remote server.

The Configuration Point Manager does not update real-time points when changes to the configuration occur.

Using AssetWorX via the OPC UA interface may lead to timeouts, making some operations very slow.

Hyper Alarm Logger Powershell modules are missing from the installation.

Updated Alert Sierra acknowledgment support to handle services that exclude a leading 1 in the reply SMS number.

When changing the Input Type to Adjustable, you cannot write to the input from GraphWorX until Hyper Alarm Server has been restarted.

The ICONICS AnalytiX-BI Point Manager service may crash unexpectedly after a change in the configuration is applied while the service is running.

The ICONICS AnalytiX-BI Point Manager service may subscribe to the same trigger tag multiple times, creating unnecessary points in its session with the FrameWorX server.

When Create new report file(s) is selected in a report with a custom name, a time stamp is appended to the report name in File/Web redirectors, which should not happen.

ReportWorX64 Express does not download configured data when more than 35 sheets are created in a report.

When using the Chinese language and editing a historical data source in Excel, the Aggregate Name field displays an error and the Global Parameters tab cannot be opened.

The Data Source configurator in ReportWorX64 Express freezes when a header tab is selected.

Hiding a sheet that contains a mapped data source causes the download to hang or returns an error.

In rare instances, ReportWorX64 Express cannot download the data for the configured data sources. An "Index was outside the bounds of the array" error is displayed.

When the client and server are in different time zones, the HTML5 AlarmWorX64 Viewer displays historical alarms in the server time zone.

In certain instances, the HTML5 AlarmWorX64 Viewer incorrectly resolves global colors in alarm condition styles.

The HTML5 AlarmWorX64 Viewer blinking style background and foreground does not correctly resolve the global color.

In HTML5, the Jump Mode setting in AlarmWorX64 Viewer is now supported. Once an alarm collection changes, you can configure whether the control stays in its current position, or jumps to the top or to an updated alarm.

In HTML5, the VisibleTotal, VisibleActive and VisibleNotAcked placeholders in AlarmWorX64 Viewer are not resolved to actual values in the status bar.

In HTML5, when using Commanding on events, a set global alias that uses the @@row.index context variable does not resolve for real-time alarm subscriptions.

In HTML5, row sorting in the AlarmWorX64 Viewer does not work if configured to sort on more than one column.

Global aliases in the details pane only resolve after data is refreshed.

In HTML5, the Manage Favorites dialog does not open if Asset Navigator is hosted in an embedded GraphWorX viewer.

In some cases, it's not possible to edit notification recipients in BACnet view in Data Explorer.

There is inconsistent sample coloring between Desktop and HTML5 SPC charts.

In HTML5, the GridWorX Viewer displays an incorrect Y-axis range when a very small value is specified for Use Specific Y-Range.

A new event, Data Committed, has been added, which is executed when a user commits changes made in the GridWorX table. This event comes with two new context variables—@@commit.result and @@commit.message—which can be used to give a user visual feedback on the commit operation result.

You can now use the Set Visibility command to change the visibility of a GridWorX Viewer chart series in HTML5.

The HTML5 GridWorX Viewer cell blinking style is not properly applied when a SimpleTagSubscription connection is used.

In HTML5, scrolling in the GridWorX Viewer causes the wrong rows to blink.

In HTML5, the Recipe Grid does not display recipe values when an older display is loaded and data is read through the new recipe API.

The foreground color does not apply to labels in an HTML5 Sankey diagram.

Parentheses that are used in the names of schedules or related objects prevent schedules from working. This has been resolved by changing Workbench to prevent the use of parentheses in the names of schedules, value sets, or folders of those objects.

In HTML5, when adding a new event on the Weekly tab in the BACnet/SC Schedule Control, the weekdays are not translated to match the language settings of the browser.

In HTML5, the Table control becomes gray when refreshing data and appears to blink.

When you add an image column to a Table and then load that table into an embedded GraphWorX Viewer, the next Load Display action will load a blank display instead of the desired display.

In HTML5, a Table does not wrap content when a column has the Width Automation property set to Fill and the Text Wrapping property set to Wrap.

The Table control may leak memory when toggling the visibility of table columns.

Pens occasionally cannot be deleted when using commanding in HTML5

In some cases, the TrendWorX64 Viewer cursor moves unpredictably in HTML5 when the control is placed in an embedded window and the root display is scaled.

When the legend contains multi-line text, the visibility checkbox and color mark in the legend are sized incorrectly.

Global aliases in the NumericFormat property of a TrendWorX64 Viewer pen don't work properly in HTML5.

BACnet Classic alarm values are mapped incorrectly in Workbench.

TrendLog objects with Notification Class 4194303 are not initialized and trend logging for those objects is disabled.

The Who-Is-router-to-network message is not sent by the BACnet with SC module.

When the BACnet with SC module attempts a Read Property Multiple (RPM) request and receives an Error or Abort response, the BACnet with SC module does not fallback to a Read Property (RP) request.

The BACnet point manager incorrectly uses the Read Property Multiple (RPM) service instead of Change of Value (CoV).

Cannot add an object to runtime when adding a device manually.

When the BACnet/SC point manager is stopped, some subscribed notification classes are not unsubscribed.

BACnet with SC incorrectly initializes foreign devices and BBMDs (BACnet Broadcast Management Devices).

In some cases, a bad quality PresentValue is incorrectly set to a Good status code.

When a new channel is created and This is the Default Channel is not selected, and immediately afterward it is set as the default channel, an error appears.

You can now filter out vendor properties by default. To do so, in the GlobalOptions section of the BACnAPI.config.json configuration file, add the FilterOutPropertiesByVendorID property with a value of True.

When creating a new data source in Workbench and a period (.) is included in the Data Source name, it causes the associated run-time data point to stop working.

In rare cases, a write operation to an OPC UA tag gets stuck when many values are read from the OPC UA server.

Fixed a rare timing issue that could cause a crash when using the InitialValue property of a GraphWorX dynamic.

Custom popup confirmation messages in GraphWorX64 do not resolve clone aliases.

Touch screen activation of a data entry field does not work if the data entry field is inside an embedded GraphWorX viewer and the embedded GraphWorX viewer has a pick dynamic on it.

When in Express mode, Hyper Historian tags fail to log with a status of Bad - License Failed, even though there are sufficient GENESIS64 tags in the license.

Historian Data Exporter is incorrectly disabled when the license for Hyper Historian (Standard or Enterprise) is not available.

After restarting the Hyper Historian Logger service, merged tags do not log.

When some tags stop providing good-quality data for a long period of time and MROT is enabled, Hyper Historian Logger stops logging and memory consumption increases.

The following error message repeatedly appears in the IoT Subscriber TraceWorX log when connecting to an MQTT broker:

[Connector/MQTT] Invalid MessageType Topic

In rare cases, the IoT Subscriber does not successfully load the configuration or process incoming data.

Fixed a crash in KPIWorX that occurred when assets from Asset Navigator were added to favorites, and then opened twice in the Favorites panel.

KPIWorX dashboards cannot not be deleted when saved to a folder.

When renaming a folder while viewing a dashboard in that folder results in an error stating that it can't find the <new folder name>.kpix file.

If you expand the navigation sidebar over a calendar control, the numbers from the control seem to show through and are visible in the navigation sidebar.

After upgrading from 10.97.2 to 10.97.3, HTML5 displays are not loaded and display the following error:

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Multiple flashing color dynamics with the same flash rate are now synchronized with each other, even if they are activated at different times.

The default language of a logged-in user is ignored in HTML5.

HTML5 popups, when loaded with a width and height set to automatic, are positioned incorrectly.

A memory leak occurs in the w3wp.exe process when HTML5 clients use displays with a Trend Viewer or Alarm Viewer.

Global aliases and local aliases that are used in a pop-up text property are not resolved.

Improved the accuracy of client station allocation.

A smart property that is bound to another smart property by an expression is not resolved.

In HTML5, rotation dynamics ignore the SkipInitialDuration property. They behave as if this property is always set to false.

In HTML5, the http://localhost/anyglass/account/status page doesn't provide a descriptive error message when the FrameWorX service isn't running.

When an HTML5 display loses the connection with a FrameWorX Server, global aliases that were passed as URL parameters are lost.

When Signalr is enabled, inactive tabs in Google Chrome or Microsoft Edge reload after about two minutes.

BACnet Classic - All Objects does not correctly report all the details about BACnet objects.

Added an INI setting in C:\ProgramData\CONICS\IcoCustomSetup.ini that allows you to disable automatic refresh for the MonitorWorX viewer. To do so, add the following line in the IcoCustomSetup.ini in the [User] section.

EnableAutoRefresh=0

The FrameWorX configuration database is not created properly while using the Chinese (Simplified) language.

A CSV file or a template exported from Modbus OPC Server 3.7 or 3.8 cannot be imported into the Modbus point manager in Workbench.

Resolved a Workbench crash that occurred when the File Size in TraceWorX Viewer was set to empty and the Enter button was pressed.

Resolved a crash that occurred while trying to edit a tag with an unusually high maximum range value in Workbench.

A warning now appears when Ignore GUID is selected during import/export to highlight the fact that the operation may be disruptive and prevent data from being logged.

The FrameWorX configuration is missing when unpacking a package created with version 10.97.2 or earlier.

Importing certain invalid IFC files can cause GraphWorX64 to crash.

If you change your operating system display language, reboot, and then create a new FrameWorX configuration, it is created in the language that you were using before the reboot. You need to reboot a second time for the FrameWorX configuration to be created in the correct language.

The AlarmWorX64 MMX Configurator (Workbench Classic) does not support upgrading AlarmWorX64 MMX configurations when they are contained in databases with other ICONICS configurations (such as unified configuration databases). You can only update these configurations using the installation or the Configure System utility.

The BACnet Classic trend buffer is not synchronized correctly (creating a gap in the historical trend) when the Hyper Historian Logger Service has been stopped for a period of time (at least 15 minutes, but it’s more likely to happen the longer that the logger has been stopped).

HTML5 does not currently support Esri map connections that use ArcGIS Portals and Servers.

On Windows 7 and Server 2012 systems, the ICONICS services can take an excessively long time starting (10 minutes or more). This can delay services that are needed to allow connections via Remote Desktop or Hyper-V console, which means that it can take more than 10 minutes before the system can be accessed.

The workaround for this issue is to change the start-up type for some services to Automatic (Delayed). Use the Services control panel or the Configure Services dialog in Workbench to change any ICONICS service running as Automatic to Automatic (Delayed). The ICONICS services still will be slow to become responsive, but users will be able to remote into the system in the meantime.

Do not use Powershell cmdlets to add Energy AnalytiX extensions and related energy calculations to meter tags as the related AssetWorX equipment properties (including their connection to Hyper Historian) will not be automatically created, leaving the product in an invalid state.

Alarm acknowledgment may not succeed when acknowledging many alarms at once that originate from an IoTWorX device. However, users can work around this issue by acknowledging alarms in smaller batches.

If the AssetWorX configuration doesn't meet the following requirements, the sample Energy AnalytiX dashboards will have no data and the EnergyAssetsDimBi table under any of the three energy data models in AnalytiX-BI will display an error status:

• The Energy AnalytiX extension must be added to the topmost equipment under Assets > Equipment.
• Each piece of equipment that has the Energy AnalytiX extension must be configured with one of the following levels: Enterprise, Area, or Site. Use the General tab to configure the level.

To resolve these errors, ensure that your AssetWorX configuration meets the above requirements. See knowledge base article 4970 to learn how to refresh the data model.