Various enhancements to improve the security of the software.

Under some circumstances, the tags coming via the Reverse Net point manager indicate "Bad - Server Closed Connection" quality.

Added an IdleTimeoutSeconds parameter to Ico.FwxServer.Net.NetPointManager.The parameter sets the timeout for all connections (the default is 30 seconds). The valid range is 1 to 3,600. To change the setting, go to Platform Services Configurator > Point Managers > Networking.

Note: If the setting isn't there, you will need to add it manually to:

C:\ProgramData\ICONICS\FwxServer.PointManagers.config

When Tag Counting Mode is set to AssetWorX Tags (for Basic SCADA), the Hyper Historian SQL Query engine does not work.

Added support for Recipe Management Runtime Info tags.

A crash occurs when opening a display in GraphWorX64 Runtime that contains a GraphWorX64 Viewer linked to a display with a Recipe Grid.

Audit messages are missing the user and machine name when recipes are remotely modified using the Recipe Grid control.

The Recipe Navigator control causes context menu operations such as New Recipe Item to fail when connected to a remote server.

Fixed a memory leak in the BACnet with SC schedule and calendar views.

Workbench crashes in the calendar control when the Holiday has invalid XML.

In the audit log, security changes are logged only in English.

Fixed an issue where dynamic AssetWorX tags do not work in the Cc and Bcc fields.

You must select the Use UA Points option on the Email Settings tab.

If the AlertWorX service is slow to start, it will initially fail to load the configuration. When this occurs, the configuration doesn't load until a configuration change occurs.

Workbench crashes when creating an alarm with a type that includes an input with the Boolean constant type and no default value.

Fixed an issue where a new alarm type could not be created without adding the Severity field.

When an alarm type input is changed from Constant to Adjustable in runtime, the alarms of that type do not trigger or change until Hyper Alarm Server is restarted.

When the display scale in Workbench is set to 175% or more, the scroll bar on the General and the Expression tabs on the Alarm Types screen (Alarms and Notifications > Hyper Alarm Server > Types) is missing and it is not possible to view all of the content on the tabs.

The Alarm State Storage feature with the Data Flush Period set to 0 doesn't update the .bin file when the server shuts down.

The Update Adjustable Inputs feature does not work for Asset alarms.

When retrieving equipment properties via the Dimensions > Asset Property step in an AnalytiX-BI data flow, the HasHistoryValues flag incorrectly returns False for properties configured as Hyper Historian tags.

The AnalytiX-BI point manager crashes when a data model is brought offline while clients are connected to it, and then is brought online again.

Queries with an ORDER BY clause may fail with a "Column name is not unique" error if they use the same aggregate over the same column twice, even if the columns have unique aliases.

The AnalytiX-BI server may become unresponsive if one or more tables are connected to data sources that take an extensive amount of time (more than 4 minutes) to return their data. Also, queries that use predicates with many conditions (more than 20 conditions) will cause a large spike in memory consumption and will execute slowly.

When creating an AnalytiX-BI data flow that retrieves data from a custom AnalytiX-BI query with column aliases, the query incorrectly returns non-aliased column names.

If you use the Test Transaction button to execute a transaction, the parameters string has extra < and > characters.

A Connected Field Service Workers source that is connected to Azure Active Directory imports guest users when it should only import member users.

When Sort workers by location is set for worker lookup, the default expression does not work with Hyper Alarm Server.

The Energy AnalytiX license requirements have been simplified. Now, the EnergyAnalytiX license only needs to be accessible from the node where Energy AnalytiX and AssetWorX are deployed.

Improved an error message explaining that Energy AnalytiX calculation expressions do not support calculations of type x= {[meter:*.*}} + constant because these types of calculations cannot be mapped to a related historian calculation expression.

Energy dashboards display data with different time stamps on the Yearly dashboards when compared to similar periods on the Long-Term dashboards.

If you upload a template to ReportWorX64 when the file is open in Excel, it appears to work fine until you apply the changes, and then it displays the error, "Value cannot be null. Parameter name: bytes."

When the name of a worksheet is changed and the Excel file is immediately saved, the file gets corrupted, and the ReportWorX64 Express configuration can no longer be loaded.

A custom column that uses a formula that references another sheet (such as =Sheet2!A1) breaks when the data is downloaded.

AlarmWorX64 Viewer does not resolve language aliases in specific cases when a control appears on the screen for the first time.

(MobileHMI and HTML5 WebHMI)The context variable @@row.index does not work in commands executed from an HTML5 AlarmWorX64 Viewer.

Some tooltips for the History Control in the AlarmWorX64 Viewer are not properly localized.

Under some circumstances, AlarmWorX64 Viewer may ignore aliases set by the Load Graphics Display command.

(MobileHMI and HTML5 WebHMI) If an alarm was previously active in the viewer and was acknowledged and returned to normal, and then becomes active again, it briefly displays the time stamp of the previous alarm.

Fixed an issue in HTML5 where pushpins were located incorrectly in displays that contained culture-specific static values for latitude/longitude data sources. These values are now automatically converted into culture-invariant strings.

Resolving and updating tags in column headers in HTML5 is not consistent with the desktop (WPF) viewer.

When the display scale is set to 250% or more, the OK and Cancel buttons aren't visible in the pop-up window in GridWorX Viewer Runtime in GraphWorX64.

A crash occurs when opening a display in GraphWorX64 Runtime that contains a GraphWorX64 Viewer linked to a display with a Recipe Grid.

Recipe Navigator may crash when global aliases are used.

The Schedule Control initially appears blank until you start scrolling.

Fixed an issue in the BACnet with SC Schedule View that was causing a failure to read the protocol revision of a BACnet device.

(MobileHMI and HTML5 WebHMI) If the Time Shift property of a pen is changed in runtime via global aliasing, the time in the legend does not update with the new value.

A Pen Removed event provides an incorrect value for the pen index.

(MobileHMI and HTML5 WebHMI)The Create Pen command on a pick action with Drag Drop set to True cannot be dragged and dropped onto a TrendWorX64 Viewer.

(MobileHMI and HTML5 WebHMI) An Edit Trend Chart command with a Summary Interval parameter updates the trend interval instead of the summary interval.

Improved the speed of data import after Network Discovery.

When you disable a channel or remove a device or object, AssetWorX continues to display the invalid alarms.

The BACnetRuntimeID property has an incorrect value.

Reading all the data from the propertyList property causes a buffer overflow error and does not fall back to reading the propertyList property in smaller chunks.

In property discovery, scanning uses the propertyList property every time it scans the properties even when Protocol Revision is less than (<) 14.

Fixed an issue in the BACnet/SC ScheduleWorX64 Viewer that was causing a failure to read the protocol revision of a BACnet device.

When two devices with identical names are on a BACnet network, the import fails.

The conversion of single or double values fails in the EDE Exporter.

Added a vendor-specific property, DisableRouting, to the Network Port object.

BACnet object names aren't correctly displayed in IoTWorX in the ISO 10645 UCS-2 character set on Linux.

Some objects generate a "Bad - no such object" warning even though the object and the property are valid.

BACnet alarms are not visible in AlarmWorX Viewer when the root bac: is selected. If the source is different (for example, a channel or a device), the alarms are visible. This occurs when the BACnet configuration database is loaded or imported.

EDE export fails when there are proprietary objects.

EDE export consumes a lot of Workbench resources.

The RemoveListElement operation is not performed when alarms, trends, or history alarms are disabled.

Hyper Historian doesn't merge data from BACnet trend buffers.

When loading a GraphWorX64 display, direct Modbus tags hang at "Bad - Waiting for initial data" quality.

OPC UA server folder and tag names that have the left square bracket ([) in their name (such as Item[0]) cannot be browsed and have a quality of Bad - Invalid point name.

An OPC UA connection might not work when it is renamed to a name that was previously deleted (for example, connection A was deleted, and then connection B was renamed to A).

(MobileHMI and HTML5 WebHMI) A web browser control inside an embedded GraphWorX64 Viewer control is not positioned correctly when the display uses IsScalable = true and PreferredStretch = Uniform.

(MobileHMI and HTML5 WebHMI) When confirming a write, the Yes button is not selected by default in the confirmation dialog like it is on the desktop (WPF).

(MobileHMI and HTML5 WebHMI) A pick action with an Initial Click and a global command with at least one constant parameter (for example, a string or a number) is not executed.

(MobileHMI and HTML5 WebHMI) A pick action with a Shortcut Key and a global command with at least one constant parameter (for example, a string or a number) is always disabled and cannot be executed.

Fixed an issue where it was possible to click buttons in a GraphWorX64 display before the display had finished loading.

The OK, Cancel, and Help buttons aren't visible in the Smart Tile Configuration window when the display scale is 250% or more on a high DPI monitor.

(MobileHMI and HTML5 WebHMI) A layer set with No Zoom, No Pan, and No Scaling that also has horizontal or vertical alignment set might not remain in the correct place. In some cases, it loads off to the side where it isn't visible.

The Data Exporter cannot export array and non-array values to the same SQL table column. If one tag logs number values, while another tag logs number arrays of length 1, and the Column Type of the exported data set is set to Value, the array values will cause the export task to fail. If the Column Type is set to Array of Values with the index set to 0, then the non-array values will cause the export task to fail. Changes have been made to address this issue and ensure that these types of tasks don't fail anymore (see ID 5319).

If you need to export the individual values of both tags to the same column, set the Column Type to Calculated, and set up the expression like this:

IF isarray({{Value}})
THEN getat({{Value}},0)
ELSE {{Value}}

When Tag Counting Mode is set to AssetWorX Tags (for Basic SCADA), the Hyper Historian SQL Query engine does not work.

When upgrading Hyper Historian from version 10.97.1 CFR 2 to 10.97.3, the configuration does not load when Use Advanced Configuration Cache is enabled.

When sending a negative integer value via MQTT Sparkplug B, the received value in GENESIS64 is not converted properly.

IoTWorX isn't showing devices as online in Workbench even though they are publishing data.

Newly added tags to the publish list are not sending buffered data.

IoTWorX devices are not displaying the All Available Data and Published Data folders via Dynamic List.

A Sparkplug B data point browsed via a FrameWorX network node creates an endless, browsable tree structure.

BACnet object names aren't correctly displayed in IoTWorX in the ISO 10645 UCS-2 character set on Linux.

Real-time data updates are dramatically slower when Local and Cloud Buffering is enabled.

IoT Subscriber point manager stops receiving updates for one subscription, but other subscriptions still work.

If you scan a QR code in the AppHub when another display is open, it does not open the display that is linked to the QR code.

When the dynamic data source type is changed during runtime (for example, from Boolean to a number), HTML5 sometimes writes a 0 for the tag instead of the actual process point value that was entered by the user.

The first time an HTML5 client connects to a server, the :ClientIPAddress tag fails to resolve if the display contains a process point that uses both language aliasing and global aliasing.

When there is no internet access, the Abbreviated What's New does not display even if the Help is installed locally.

Product Help buttons are not properly linked to the Help.

During system configuration, it's now more obvious when user credentials are invalid.

Disabling FrameWorX in Configure Application(s) Settings might disable other core services that provide OPC Classic connectivity and simulation.

Disabling a FrameWorX application causes the ICONICS Simulator Point Manager service to be stopped and disabled.

Part of the Apply & Close and Apply & New buttons are hidden when the language of the operating system is set to French.

In the Japanese translation, the Cancel button is not translated in the Filter Wizard popup in AlarmWorX64 Logger.

Enabling or disabling applications from Workbench overwrites point manager settings that have been changed in Platform Services Configuration. This occurs only when Enable and run only the services for the applications that are in the project is selected.

Added a PowerShell parameter for ignoring a GUID. For example, when importing an Asset configuration:

Import-WbConfiguration -Root $key - Provider Assets -Path [path_to_file] -Format Csv -Delimiter ',' -ImportMode CreateAndUpdate -IgnoreGuid True

When packing and unpacking a project using find and replace, the primary and secondary computer names in the redundancy settings for Hyper Alarm Server and Hyper Alarm Logger cannot be replaced.

The project reporting database is not installing the proper version, and Workbench does not notify the user that an upgrade is needed.

An option (Purge database) in the Import/Export dialog is not correctly translated in French and is misleading for users.

Importing certain invalid IFC files can cause GraphWorX64 to crash.

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 maps.

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.