Please read the information below prior to installing ClearSCADA 2017 R2 for important information on any known issues.
As in the previous release, ClearSCADA 2017 R3 will require one Data Access license per system from each ‘active’ ClearSCADA server connected to the IIS instance. By ‘active’ this means the connected server of the redundant connection setup. This is independent of the number of users connected to IIS, and is part of your ClearSCADA Server license.
ClearSCADA 2017 R3 will also require one WebX client license per logged-in user from each ‘active’ ClearSCADA server connected via the IIS instance. By ‘active’ this means the connected server of the redundant connection setup. The WebX client licenses you purchase and install on a server can be used simultaneously with Original WebX (where the usage is shown in the Server Status tool) and the IIS WebX (where the usage is logged in the WebX.log file).
While additional users above your licensed limit per server can be logged-in, using either Original WebX and IIS WebX simultaneously or using multiple separate IIS WebX instances, this is a transition for licensing and you are expected to purchase licenses equivalent to your usage. Future releases of ClearSCADA are expected to enforce license limits. This will be highlighted in Release Notes.
Please see the updates on this page.
High resolution displays that are configured to use Text Scaling can result in displays of ClearSCADA's Map Displays and Lists to be noticeably pixelated and blurry. The impact for Map Displays is aesthetic only and should not impact useability, however applying non-standard scaling impacts the display of Lists because the table content becomes too wide for the column width, obscuring some content from view.
Translated strings for a user with the user set to the locale for those translations, a trend created and an internal digital point's processed history trace added to it. Annotations are then added to the trend with the translation string: @this. ViewX and original WebX displayed the translation for @this correctly, but (new) WebX displays @this instead of the translation for @this.
Text alarms are not displayed within the HTML5 Alarm Banner in WebX. Text Alarms are typically associated with Server Licensing, Archiving, or Historic Granule Monitoring Alarms, although can also be generated by some drivers or via methods in Logic and Scripting. These Text Alarms are displayed correctly within the Embedded Alarm List.
A problem with exporting Crystal Reports on Windows 8 and 8.1, and Windows Server 2012 and 2012 R2 has been identified. It is triggered by the report containing Boolean parameters with the "Exclusive group" option enabled. Subject to confirmation, the likely cause is the SAP crystal runtime rather than ClearSCADA 2017.
On a clean installation of ClearSCADA 2017, the classes for OPCDA, OPCAE and OPCHDA servers are not registered. The user would need to open the Client Configuration dialog and click OK on the configured connection for the classes to be registered. This was changed to add support for the Systems.xml file.
An issue has been identified within the Wonderware Historian (WWH) interface whereby it does not operate correctly after upgrades from ClearSCADA 2015 and 2015 R2, and causes a ClearSCADA server exception when starting the database.
This can be resolved by performing a "repair" on the ClearSCADA 2017 Server installation in Windows Control Panel. After a repair of the installation has been performed, a restart of the ClearSCADA server should result in successful system operation.
The following problems were identified:
- When clicking on the 'List All <class> Objects' from a class information page in the database schema, the list of objects may not display correctly. This is a problem with the Internet Explorer's XSL transformation related to elements with content and children.
- Script functions such as 'Mimic.OpenInset' and 'App.OpenWindow' may not display properly on IE9/10/11.
- Hyperlinks to lists may not display correctly due to the cross site scripting security filter in Internet Explorer. This also includes links to trends generated using the TrendSpec specification in ClearSCADA. The workaround for this is to disable the Cross-Site Scripting (XSS) filter in the web browser.