ClearSCADA 2017

Software for Telemetry and Remote SCADA Solutions

Release Notes
July 2018 Update

Copyright © 2016 Schneider Electric Industries SAS

Contents

Refreshing the ClearSCADA Brand .................................................................. 5

New Features................................................................................................. 6
Location Support, Mapping and GIS Integration............................................................. 6
GPS Location for all Objects ............................................................................................................ 6
Update of Users’ Location from Clients .......................................................................................... 6
Geographic Regions ........................................................................................................................ 7
Displaying it all on a Map ................................................................................................................ 7
Alarming and Redirection ............................................................................................................. 11
Location-Based SQL Queries ......................................................................................................... 13
Centralized User Management .................................................................................... 15
Creating Users Automatically from Group Membership .............................................................. 15
The Login Process.......................................................................................................................... 17
Automated Control Validation .................................................................................... 19
Control Feedback Alarm................................................................................................................ 19
Uncommanded Change Alarm ...................................................................................................... 19
Return to Normal Alarm for Analog and Counter Points .............................................................. 20
Device Integration....................................................................................................... 21
Advanced Trio Diagnostics ............................................................................................................ 21
Lacroix SOFREL RTU....................................................................................................................... 21
SCADAPack E 8.14.1 Firmware Support ........................................................................................ 22
Realflo 6.94 and 6.95 Firmware Support ...................................................................................... 22
Updated bundle of OPC Factory Server (OFS) .............................................................................. 23
System Administration and Security ............................................................................ 24
ClearSCADA able to run as Non-System User ............................................................................... 24
System Commands Now Require User Credentials ...................................................................... 25
New Utility to Clean Unused Areas of Interest ............................................................................. 25
Changes to Management of User Security Configuration ............................................................ 26
Tightened Super User Credentials ................................................................................................ 26
Administration of the Wonderware Alarm Provider .................................................................... 26

ClearSCADA 2017 Release Notes – July 2018 Update Page 2 of 49

 Updated Prerequisites .................................................................................................................. 27
Mobile Companion Installation..................................................................................................... 27

Enhancements ............................................................................................. 28
A Note Regarding the Evolution of ViewX .................................................................................... 28
ViewX User Interface – General .................................................................................................... 29
ViewX User Interface – Multi-Monitor Configurations & Super Favorites ................................... 29
WebX Alarm Banner Row Limit ..................................................................................................... 30
Enhanced Backup Functionality .................................................................................................... 30
Server Synchronization ................................................................................................................. 30
Online Help – Frequently Asked Questions .................................................................................. 31
Online Help – Technical Reference Guides ................................................................................... 31

Recent Updates ........................................................................................... 32

Resolved Customer Issues – July 2018 Update ............................................................................. 32
Resolved Customer Issues – June 2018 Update ........................................................................... 33
Resolved Customer Issues – May 2018 Update ............................................................................ 33
Resolved Customer Issues – April 2018 Update ........................................................................... 34
Resolved Customer Issues – March 2018 Update ........................................................................ 35
Resolved Customer Issues – February 2018 Update .................................................................... 35
Resolved Customer Issues – January 2018 Update ...................................................................... 36
Resolved Customer Issues – December 2017 Update .................................................................. 37
Resolved Customer Issues – November 2017 Update .................................................................. 37
Resolved Customer Issues – October 2017 Update ...................................................................... 37
Known Issues – September 2017 Update ..................................................................................... 38
Resolved Customer Issues – September 2017 Update ................................................................. 38
Resolved Customer Issues – August 2017 Update........................................................................ 38
Product Enhancements – July 2017 Update ................................................................................. 39
Resolved Customer Issues – July 2017 Update ............................................................................. 39
Resolved Customer Issues – June 2017 Update ........................................................................... 40
Resolved Customer Issues – May 2017 Update ............................................................................ 40
Resolved Customer Issues – April 2017 Update ........................................................................... 40
Resolved Customer Issues – Initial Release (March 2017) ........................................................... 42
Vulnerability Disclosure ................................................................................................................ 48

ClearSCADA 2017 Release Notes – July 2018 Update Page 3 of 49

ClearSCADA 2017 Release Notes – July 2018 Update Page 4 of 49
Refreshing the ClearSCADA Brand

The release of ClearSCADA 2017 signifies the departure from our StruxureWare SCADA
Expert ClearSCADA brand, and reinforces our alignment with the Schneider Electric
Software Business by adopting the Schneider Electric brand and refreshing the ClearSCADA
graphics and product icons.

This move is aimed at simplifying the customer experience, eliminating confusion in the
marketplace and boosting customer perception while leveraging the strength and history of
our renowned ClearSCADA brand, all while reinforcing ongoing product investment in
ClearSCADA.

To reduce any impact of changes to ClearSCADA branding, modifications to ClearSCADA

application icons are listed below:

Application Old Icon New Icon Application Old Icon New Icon

Dynacard Export
ViewX
Client

Mobile
Service Manager
Configurator

Database Manager Bulk Edit Tool N/A

Certificate
Server Status N/A
Generator

Area of Interest
Server
Cleaner (new N/A
Configuration
application in 2017)

Configure PLC to OPC

N/A
Connections Conversion Tool

Save All
QueryPad N/A
Documents

ClearSCADA 2017 Release Notes – July 2018 Update Page 5 of 49

ClearSCADA Server Icon changes are listed below:

Server Operational State Old Icon New Icon

Not Running

Running as Main

Running as Standby

Starting

Stopping

Synchronizing

Invalid Configuration

NOTE: Branding has not been changed for separate applications or stand-alone
documentation libraries that are bundled with ClearSCADA, as listed below:

Application Icon

Field Exchange Utility

Wonderware Historian Publisher

ClearSCADA Client API Guide, and

ClearSCADA Mobile Administration Guide

ClearSCADA 2017 Release Notes – July 2018 Update Page 5 of 49

New Features

Location Support, Mapping and GIS Integration

ClearSCADA 2017 introduces location-based alarming, filtering and visualization. There is a
suite of new objects and configuration options within ClearSCADA to support the above,
each of which are explored below.

GPS Location for all Objects

All objects can have a set of static or dynamic WGS84 coordinates which can include
Latitude, Longitude, Height, Accuracy (XY and Z), and Date/Time of last location update.
Coordinates are stored as degrees; positive for latitude N and longitude W, and a height in
meters. If the location of an object is read and the location setting is configured to inherit, the
parent object’s coordinates are recursively read to find its location.

When configured to store a dynamic location, User Account objects will have their location
updated by the User Interface (see below). An API is also available to support update of
locations (for Users or otherwise) by Logic applications or external tools, allowing existing
location-tracking systems (for example vehicle tracking) to be fed into ClearSCADA.

If an object is configured to store a dynamic location, this includes Heading and Speed, and
any configured static figures are overridden by the dynamic data. If optional items are not set
(for example Height, or Speed), they can be read as NULL and as a Boolean status.

Update of Users’ Location from Clients

ClearSCADA clients can update their location to the server on a regular basis. This includes
the ViewX, IIS WebX and ClearSCADA Mobile UI (as was enabled in a recent update to
ClearSCADA Mobile iOS and Android applications). The User object now has three
additional checkbox options, one per UI, to control which can cause the location to be
updated.

For ViewX and WebX the updates will be on logon, logoff, and resuming a locked session
(ViewX only) and for Mobile, on significant change of location (approximately 100 meters)
and no more than one update per minute from a device.

The full position and accuracy is sent to the server.

ClearSCADA 2017 Release Notes – July 2018 Update Page 6 of 49

Geographic Regions
A new Region object type is available that allows a user to define a circular, rectangular or
irregular shape in geo-space.

• A Circular Region is defined using the coordinates of the center and a radius (in
meters).
• A Rectangular Region is defined as upper left and lower right coordinates.
• An Irregular Shape Region is defined by an arbitrary, ordered set of points in
standard GeoJSON format. Irregular shapes are to be defined in a clockwise
direction, with excluded 'holes' defined in an anticlockwise direction.

A User (and the User Groups they are a member of) can be configured with references to
multiple Region objects to define that user’s area of operational responsibility, and alarm
notification rules (E-Mail and Pager) can be defined to automatically notify a specific User,
User Group or Roster for any alarms occurring within a specific Region. Alarm redirections
configured on Group objects can also be filtered by a reference to a Region (see Alarming
and Redirection below).

A Region can also be used for location-based queries within the database, to return a
specific collection of objects for display in a list or on a Map (see Displaying it all on a Map
and Location-Based SQL Queries below) or Alarms (see Alarming and Redirection below).

Displaying it all on a Map

A new Map Source object has been created to configure the links to online mapping data.
Internet-only sources include either Bing Maps or OpenStreetMap, and internet/intranet
sources are ArcGIS layers or the generic Web Map Service (WMS) layers, which can be
used for Weather or other online sourced data. The Map Source object also defines:

• The default zoom level for the map source

• The API Key to be used for authentication (Bing Maps only)
• Which of the available layers are enabled by default (Bing Maps only)
• A Source URL for retrieval of remote mapping data (ArcGIS and WMS only)

Map Sources can be displayed on their own, or displayed within a Map Set. The Map Source
also has the following additional options for ArcGIS and WMS Sources to facilitate display of
the map layers within a Map Set(s):

• A Layer Title, for display within the Legend when integrated into a Map Set
• Selection of whether the map data is an Overlay Layer
o Configuration of an Overlay Layer’s Opacity
o Configuration of an Overlay Layer’s Refresh Frequency
o Selection of whether an Overlay Layer is enabled on a Map Set by default

ClearSCADA 2017 Release Notes – July 2018 Update Page 7 of 49

A Map Set is a new object that enables the grouping of a number of Map Sources into a
collection, allowing these to be viewed within a single map view. The Map Set uses an array
to define the Map Sources that form part of the Set, where the order of the sources defines
the order of their display when the Map Set is displayed.

Map Sets can also integrate User Queries, which is described more in the Adding User
Queries for Map Markers section below.

The Root group of the ClearSCADA Database allows a Map Source or, with more
functionality, a Map Set object to be configured to enable default map displays from a
location-enabled Object Pick Menu and Alarm Pick Menu: 'Display on Map'. (See ‘Display on
Map’ Object Menu Option below).

Note: Maps are requested and displayed by the ClearSCADA client. The server does not
require access to the map services. Map services can be hosted by internet or intranet
depending on the capability of the Map Source type. For example, your organization might
have an internal source of WMS or ArcGIS map data.

Note: If the map contents are not displayed, an Administrator-privileged user can press F12
to show the Debug window. The “Network” tab should display the data received from the
Map Source you pan/zoom the Map Document, and can be used to debug errors with your
network connection (like an invalid proxy, invalid credentials, and so on).

Display Maps using Hyperlinks

Map Sources and Map Sets can also be launched via a hyperlink which accepts the
following additional parameters, overriding the configured Map defaults where necessary:

• Zoom : Integer
• Latitude : Double
• Longitude : Double
• Query : String

For example, the following hyperlink will display the “Map Set” object configuring the zoom
and position:

SCX:////CGISMapSet/Map Set#zoom=18&Latitude=40&Longitude=40

Displaying Markers on Maps for Asset Locations

An SQL query can also be specified as part of the above Hyperlink to display a single set of
markers on the map corresponding to locations of assets configured within the ClearSCADA
database. By way of example, the following Hyperlink will display a map marker for all
database objects configured with a location:

ClearSCADA 2017 Release Notes – July 2018 Update Page 8 of 49

 SCX:////CGISMapSet/Map
Set#zoom=18&Latitude=40&Longitude=40&Query=SELECT FULLNAME,
GISLOCATION->LATITUDE, GISLOCATION->LONGITUDE FROM CDBOBJECT

Adding User Queries for Map Markers

As a simpler alternative to specifying the Query SQL within the Map Set Hyperlink as above,
a User Query object can be used to hold a configured database query of ClearSCADA
objects to be displayed on maps. When configured, a ‘Display Query Results’ context menu
on the User Query object will display the query results in a list, which is useful for testing the
SQL query. Each individual entry within the SQL query list should translate to a Map Marker
when shown on a map, although entries with the same location will appear superimposed
over each other, obscuring view of some markers. Data referred to by the SQL query will be
updated when the map moves or once per minute only.

The following SQL column names are used to define the behavior of the marker:

• FullName (used as the Object Reference for the Pick Menu)

• Foreground
• Background
• Blink, and
• Tooltip (an optional extension to override the text shown in the hover tooltip).

Map Sets also allow a list of User Query objects to be linked directly to the Set. When the
Map Set is displayed, the referenced User Queries are used, in order, as separate
controllable layers of map markers. The ‘Display by default on Map Set’ option on the User
Query object is used to specify that the respective map marker layer is to be visible by
default when a Map Set containing that query is displayed.

When multiple User Queries are added to a Map Set, each query is dynamically allocated a
symbol to be used for the Map Marker. The symbols rotate through three varieties of shape;
Triangle, Diamond, and Square. The allocation of the above shapes is repeated until all User
Queries for the Map Set have been assigned a shape.

A Circle Map Marker is reserved for when a Query is referenced within a Map Set Hyperlink
(see Display Maps using Hyperlinks above) or a Map Set is opened via the “Display on Map”
Object Menu (see ‘Display on Map’ Object Menu Option below).

SQL queries within hyperlinks to display assets on a map need to contain the following
columns as a minimum:

• FullName (object name – used to generate the default tooltip and context menu)
• GISLocation->Latitude (Latitude)
• GISLocation->Longitude (Longitude)

ClearSCADA 2017 Release Notes – July 2018 Update Page 9 of 49

However, the SQL can also include additional columns of “Foreground”, “Background”,
“Blink”, and “Tooltip” to manipulate the display of the marker as listed above. The above
columns are parsed based on Name rather than Attribute, allowing for color animations to be
customized as required. The tooltip can contain HTML formatting codes.

As an example, the following map hyperlink uses the AlarmSetCount, AlarmAcceptedCount

and AlarmClearedCount variables on CGroup to manipulate the Foreground color, adjusting
the color used to display the associated map icon for each Group. The ordering of the result
set will display the assets with active alarms on top of those without, if there is any overlap:

SELECT FULLNAME, FULLNAME || '<br>Highest_Severity:_' ||

AlarmSeverityDesc as "TOOLTIP", GISLOCATION->LATITUDE, GISLOCATION-
>LONGITUDE,
CASE WHEN AlarmSetCount > 0 THEN 255
WHEN AlarmAcceptedCount > 0 THEN 255
WHEN AlarmClearedCount > 0 THEN 150*256 ELSE 0 END AS
"Foreground", Background,
CASE WHEN AlarmSetCount > 0 THEN 1 ELSE 0 END AS "Blink",
AlarmSetCount, AlarmAcceptedCount, AlarmClearedCount
FROM CGROUP
ORDER BY AlarmSetCount, AlarmAcceptedCount, AlarmClearedCount

Query column names are not case-sensitive, and should not contain the table name or alias;
therefore, a column alias should be used if more than one table is referenced in the query.
The following example will display a smooth range of colors as the symbol foreground based
on the value of a point associated with a group’s location:

SELECT g.Id as "Id", g.FullName as "FullName",

g.FullName || '<br>Value: ' || FormatValue (r.Walk Using '0.00') as
"Tooltip",
g.GISLOCATION->LATITUDE as "GISLOCATION->LATITUDE", g.GISLOCATION-
>LONGITUDE as "GISLOCATION->LONGITUDE",
case
when r.Walk < 50 then (cast(r.Walk/100*2*255 as INT) + 255*256)
when r.Walk > 50 then (255 + cast( (100-r.Walk)/100*2*255 as
INT)*256)
end as "Foreground",
255+256*255+256*256*255 as "Background", 0 as "Blink"
FROM CGROUP AS g left join CRandom as r on r.ParentGroupId = g.Id
WHERE g.FULLNAME LIKE 'Sites.%'

ClearSCADA 2017 Release Notes – July 2018 Update Page 10 of 49

‘Display on Map’ Object Menu Option

A new context menu item is available to all objects, but is displayed only when that object
has a valid geographical location and a Default Map Source or Set has been configured on
the $Root object.

When this menu option is selected from an object’s context menu, the map is displayed
centered on the object and at the zoom level configured on the Map Source. A circular
marker shows the location of the selected object.

Alarming and Redirection

Alarm Filtering

A Region filter has been added to the Alarm List link syntax. The filter specifies whether an
alarm is within the named Region object, where multiple regions can be combined.

Alarm filters 'OR' within their class, and 'AND' across classes. For example, specifying two
Regions and a database path name will result in the Alarms List displaying the alarms in that
path which are members of either Region.

The Alarm Filter dialog has been extended to allow a user to specify one or more Region
objects.

To use this filter manually, the filter syntax for a Region is:

SCX:////AlarmList/Region="East.RegionObj"&Region="North.RegionObj"

This allows a menu action to be built which shows a page of the alarms within one or more
named regions.

Filtering of Alarm Redirection by Region

An additional column has been added to the Alarm Redirection aggregate

(CAlarmRedirectionList) to filter the action based on the alarm's presence within a Region,
as below. If configured with a valid Region, the redirection action will only be executed when
the alarm's location is within the Region.

ClearSCADA 2017 Release Notes – July 2018 Update Page 11 of 49

Sending of Messages to Users with Applicable Regions

The redirection of alarms now includes filtering by the presence of users within the regions of
that alarm, and other filters based on the location of the alarm and the configuration of the
User, User Group or Roster.

Users, User Groups and Rosters now each have a list of 'Responsible' Regions assigned by
configuration. Alarm Redirection Actions which refer to Users (in other words E-mail Action
and Pager Action) have their User field replaced by a drop-down list and associated fields as
below. A new drop-down list has been added to specify whether Regions are used to
filter/direct the e-mails or SMS messages.

There are four entries to the drop-down to specify what happens;

a. 'User, Group or Roster' - the user can configure a User, User Group, or Roster as
was previously available. This functionality has not changed.
b. 'By Matching User Location against Alarm Region'. The alarm will be redirected to all
Users which have their location (static or dynamic, whichever applies) being within
any Region which contains the location of the alarm. The User's Group or Roster
object locations are ignored.
c. 'By Matching Set User Region'. The alarm will be redirected to all Users which have
one of their Regions (see above) which contain the location of the alarm. In other
words, this includes Regions configured on the User or the User's Group or Roster.
d. 'To Region Users' - the User can configure a Region. The alarm will be redirected to
Users or the User's Group or Roster which have one of their Regions (see above)

ClearSCADA 2017 Release Notes – July 2018 Update Page 12 of 49

 matching the Region configured within the Action. (Note this option does not examine
the user or alarm's location).

If (b), (c) or (d) are selected above, the additional ‘Find in Region’ section is activated and a
User, Group, or Roster can be configured with the E-Mail Contact field. These fields are
enabled by the checkbox. If the box is checked and the tests for (b), (c) or (d) have not found
a match, the alarm will be redirected to this other User, Group or Roster as configured,
therefore acting as a fallback.

Alarm Redirection text (the subject and message contents of e-mails and the messages for
SMS) can have trip characters to retrieve database fields.

These are able to show:

• the location of an object in alarm, using %OGISLocation.GEOPosition%

• the location of the user receiving the alarm, using %UGISLocation.GEOPosition%
• the region specified in option (d) above, using %rRegion% (or similar, whichever
redirection object's field name is used)

Location-Based SQL Queries

The SQL Engine has been extended to enable the database to be queried for geographical
information.

Data Types

Two new data types are supported by the SQL engine:

• LOCATION - the absolute position of an object

• REGION - a regional outline

To be efficient and flexible, both of these types use the Aggregate structure sub-objects in
their design, which could make querying them more complex. However, there are shortcuts
built in to simplify access to data.

Location

The LOCATION type can either be:

• A database field returning a location:

Obj.GEOPosition

This is a shortcut to the location field of the aggregate.

ClearSCADA 2017 Release Notes – July 2018 Update Page 13 of 49

 Or

• A literal location with additional optional fields, using the LOCATION keyword and a
string type:
o LOCATION 'latitude, longitude [,accuracy] [ALT altitude[,altitude-accuracy]
[DIR heading, speed] [TS 2016-04-26 12:01:23]'
o Where decimal digits specify latitude, longitude, accuracy, altitude, altitude
accuracy, heading, speed and the last-update timestamp is a standard literal
time string.
o For example: LOCATION '12.3456,34.56789'

Note: Timestamp is specified in UTC. When shown in the View Status box or
displayed in a database list result, the user's time zone is used to offset the
timestamp.

Region

The new CGISRegion class can be one of three types of Region – circle, rectangle and
irregular shape. The CGISRegionType field has a special field GeoRegion to be used within
queries.

This field can be used to test if an object is in a region as follows:

SELECT CDBObject.FullName FROM CDBObject

LEFT JOIN CGISREGION ON (CGISREGION.FullName = 'Regions.West')
WHERE (CDBObject.GEOPosition WITHIN CGISRegion.GeoRegion)

This exploits the special nature of GeoRegion, which supports the WITHIN keyword
comparison.

If the GeoRegion field is selected as a data field or just shown on a mimic as a field, a 'text
representation' of it is returned, similar to Circle(12.34,5) or Rectangle(12.34,56.78) or
Polygon( [some GeoJSON] ). A literal rectangular region can also be defined as two
locations, specified in turn as database locations or literal locations:

REGION Obj.GEOPosition TO '12.34,4.56'

Aggregates

Also note that the '->' operator can now also be used to follow links within database
Aggregates, which will mean that JOIN operations are not necessary for this kind of
Aggregate query.

When an object has no co-ordinates, or none have been set on any parent, reading them will
give NULL values.

ClearSCADA 2017 Release Notes – July 2018 Update Page 14 of 49

Centralized User Management
ClearSCADA 2017 now incorporates tighter integration with Active Directory for centralized
user management, allowing new ClearSCADA User Accounts to be created automatically
when a new user first requests logon to ViewX or WebX using their Windows® Domain
credentials, and manages permission assignment in accordance with the Active Directory
structure by linking ClearSCADA User Groups with Active Directory Groups.

Creating Users Automatically from Group Membership

Windows User Authentication settings have been moved to their own section (called
External Authentication) within the Server Configuration Tool, and expanded to include an
option to “create users automatically from group membership” which, when enabled, allows
User Groups within ClearSCADA to be linked with Groups in Active Directory.

A “Logon type” selection has also been added when Active Directory or “LogonUser”
authentication is selected, providing a choice of either Interactive or Batch logon.

A new “connection failure cached password expiry” timer has also been included to allow for
successful re-logon for Windows/LDAP users when the Active Directory server is temporarily
unavailable.

ClearSCADA 2017 Release Notes – July 2018 Update Page 15 of 49

User Group objects have been extended to support association with an AD group, as
follows:

Matching to Active Directory Groups will be by the “Windows/LDAP Group Name” field,
which cannot be blank when this functionality is enabled.

The “User Pattern” is configured with a reference to a new User Pattern object, and is the
master User for that Group (see below). The “Create Users in Group” field is a link to a
location in the database hierarchy where new User Accounts should be created. Priority is
used to determine which User Pattern is chosen if there are more than one that apply for a
specific User (since a User can be associated with multiple User Groups), where the higher
priority number takes precedence.

User Pattern

The User Pattern is a new object that is a nearly identical object to a User, except that it
cannot be enabled or be configured with a password. The User Pattern object has a disabled
'Enable' check box. The User Pattern is used to define the initial settings for the User and
configuration options to control the presentation of ViewX and WebX. When a new user is
created by the Active Directory authorization process, the User Pattern is copied. Once
copied there is no further relationship between the User Pattern and the resulting User.

ClearSCADA 2017 Release Notes – July 2018 Update Page 16 of 49

The Login Process
With "Create users automatically from group membership" Enabled

When a user with an unknown ClearSCADA Username (or a valid Windows username
configured on a ClearSCADA user) attempts to log in, the server will attempt to find an
AD/LDAP user with the entered name.

1. If not found, login is rejected.

2. If the 'Windows user login enabled' option is not checked and the username entered
does not meet ClearSCADA naming rules, then the login is rejected.
3. If found, the group membership in AD/LDAP will be read, and the names of the
AD/LDAP sub-groups will be read recursively.
4. A pattern for the user to be created, and the group location of the user, is set from
the ClearSCADA User Group configuration properties.
a. The matching Group found which has "Allow Automatic User Creation"
enabled and the highest priority will be used.
b. This Group configuration points to a User Pattern from which the new User is
to be copied.
c. The user will be created in Group as specified.
d. If no User Pattern is found attached to any Group in the list, then no User is
created and the login is rejected.
e. Any User Groups configured on the User Pattern which do not have “Link to
Windows/LDAP Group” enabled would remain and the others removed, to be
replaced by those in the LDAP/AD group list read for that Windows User.
5. The user will be added to additional ClearSCADA User Groups if any ClearSCADA
User Group "Windows/LDAP Group Name" corresponds to any of the AD/LDAP
Group names.
6. Characters in the user name which are not acceptable to ClearSCADA will be
mapped to valid characters (for example “.” to “_”). It will not matter if this user is
subsequently renamed, users can continue to login with the Windows/LDAP User
Name. Manually created users with their separate Windows User Name would also
be used in the same way. In the event of a clash with an existing username, the login
will be rejected and a User will not be created.
7. The user is logged in.

ClearSCADA 2017 Release Notes – July 2018 Update Page 17 of 49

When a User with an AD/LDAP valid username logs in and "Use External Authentication"
is set on their User Account object:

1. The group membership in AD/LDAP is read and the names of the sub-groups are
read recursively.
2. The group membership of the linked ClearSCADA User is adjusted accordingly:
a. If the ClearSCADA User Account object had references to Groups which do
not have “Link to Windows/LDAP Group” enabled then they will be retained,
others with this flag enabled will be added/removed if they have changed.
3. The user is logged in.

Note: Only ViewX clients running ClearSCADA 2015 R1 or later versions that have secure
connection enabled will be able to initiate the automatic creation of a new User Account via
Active Directory at time of logon, if one does not already exist. ViewX clients from previous
versions of ClearSCADA will first need to have their User Account created in the
ClearSCADA database, either by having the account manually created, or by first logging on
to the system via a newer ViewX client or WebX client (which will trigger the creation of the
account automatically).

Note: Case sensitive usernames are now disabled by default for new installations of
ClearSCADA. Automatic user creation and case sensitive usernames cannot be enabled at
the same time.

ClearSCADA 2017 Release Notes – July 2018 Update Page 18 of 49

Automated Control Validation
Control Feedback Alarm
Validation rules can now be configured for Output Controls such that an alarm will be raised
when the output state or feedback from an input variable does not reach the desired
state/value within the configured timeout. A number of comparison types are supported for
flexibility, including:

• Equals Target “Value”

• Equals Controlled “Value”
• Between Low and High Limit
• Outside Low and High Limit
• No less than Low Limit
• No greater than High Limit
• Within “Value” of Controlled Value
• Changes by at least “Value”

When a control is successfully performed, the feedback point changes state/value and
reports to the master station. If the control has been performed, but the Feedback point has
not changed to the expected (successful) state/value by the end of the Feedback Time an
alarm or event message is generated.

If no value was received at the end of the Feedback time, and the feedback check shows a
successful value, no alarm will be raised.

Uncommanded Change Alarm

Similar to the above, validation rules can also be configured for Output Controls such that an
alarm will be raised when an associated point state/value changes and was not controlled to
do so. The following comparison types are available:

• Equals Target “Value”

• Equals Controlled “Value”
• Between Low and High Limit
• Outside Low and High Limit
• No less than Low Limit
• No greater than High Limit
• Within “Value” of Controlled Value
• Changes by at most “Value”

Controls start a configured duration timer which prevents the feedback check. When
comparing against 'Controlled Value', the last control action value is used. If no control has
been executed ever, then these tests will not raise an alarm.

ClearSCADA 2017 Release Notes – July 2018 Update Page 19 of 49

Return to Normal Alarm for Analog and Counter Points
To achieve consistency across Digital, Analog and Counter points within ClearSCADA, a
new option 'Fleeting' has been added to the Normal Severity field ‘NormalSeverityType’ for
Analog and Counter points. The ‘Fleeting’ option enables configuration of the Alarm Severity
Type (None or Fleeting) and of configuration of a specific Severity for the Normal State.

Upon a Return to Normal value change, the Fleeting alarm will be raised if configured,
notifying the Operator of the return to Normal state. When acknowledged, the fleeting alarm
will be removed from the alarm list.

ClearSCADA 2017 Release Notes – July 2018 Update Page 20 of 49

Device Integration
Advanced Trio Diagnostics
ClearSCADA 2017 includes a refreshed Trio Diagnostics driver using the Advanced Driver
Framework, providing enhanced communication capabilities for the diagnostics information
received from a Trio Radio network.

This includes support for the same functionality as is available in the existing 'Simple' Trio
Diagnostics driver, plus support for Auto-Diagnostics so you can receive diagnostics
information from E, M and K series radios in a network without the need to generate a poll,
and configuration of an IP address per radio for efficient communication with J- and Q-series
Radios.

The new Advanced Trio Diagnostics driver also supports Digital Output controls for Base
Radios, allowing a user to remotely control the Relay Outputs, remotely apply a ‘Force Base
Online’ command, and Clear Alarms.

Lacroix SOFREL RTU

ClearSCADA 2017 introduces native support for Lacroix’s SOFREL RTU family, including
S500 series RTUs via both SOFBUS-PL and LACBUS-RTU protocols S50 series RTUs, as
well as Cellbox Data and Telbox RTUs using the SOFBUS-PL protocol.

This feature-rich connectivity includes support for importing of SOFREL configuration files
from SOFTOOLS in tab-delimited value format into an outstation object using a new "Import
Configuration..." pick action, compatible with both SOFBUS-PL and LACBUS-RTU
connected devices. Device configuration can also be uploaded directly into the ClearSCADA
database from S500 series RTUs connected via LACBUS-RTU protocol.

The configuration of the RTU stored in ClearSCADA includes operational parameters, and
contains a list of call recipients who can receive direct notifications from the RTU (via
PSTN/GSM, GPRS, E-mail, and so on). Operating parameters (call recipients) can be
downloaded to SOFREL RTUs from ClearSCADA directly, and provides the user selection of
whether to download ‘All parameters’ or ‘Changed parameters only’. In addition, operating
parameters can be uploaded from the SOFREL RTU into the ClearSCADA database,
however this doesn’t support reading of Master and RTU type call recipients.

Two-stage controls are supported from ClearSCADA, by way of a 'Control and Lock' method
to issue a locked control for LACBUS-RTU devices (S500 series RTUs) and a 'Control and
Force' method to issue a forced control for SOFBUS-PL devices (S500 series, S50 series
Cellbox Data and Telbox RTUs).

ClearSCADA also supports inbound IP connections from outstations using LACBUS-RTU

protocol.

ClearSCADA 2017 Release Notes – July 2018 Update Page 21 of 49

SCADAPack E 8.14.1 Firmware Support
Enhanced SCADAPack E Smart RTU functionality available in new firmware up to version
8.14.1 will be supported within ClearSCADA 2017 to provide continued interoperability. The
enhancements are as follows:

• Firmware version 8.12.2:

o Trend sampler trend streams have a compression disabled option for digital
trend streams.
• Firmware version 8.12.5:
o Support for additional system points exposed from Remote IO to Main
SCADAPack E controller to better identify Remote IO firmware version.
• Firmware version 8.14.1:
o Ability to disable IP Forwarding using binary system point 50190.
o Ability to define Default Gateway route using Analog system point 54052.

Please refer to associated SCADAPack E Smart RTU documentation (firmware version

8.12.2, 8.12.5, or 8.14.1 respectively) for further information on the new functionality
available in these firmware releases.

Realflo 6.94 and 6.95 Firmware Support

Enhanced Realflo Gas and Liquids functionality available in Realflo 6.94 and 6.95 is
supported within ClearSCADA 2017 to provide continued interoperability. The
enhancements are as follows:

• Realflo 6.94.1:
o Meter Station Total Accumulators
o API Gravity Alarm Limits
o Extension of Liquid Calculation Ranges
• Realflo 6.95.1:
o AGA-3 (2013) Calculation of Orifice Meter Expansion Factor
o AGA-11 Enhancements
o Support for Promass 100 Coriolis meter
o Support for Emerson Micro Motion Coriolis meter models

Please refer to associated Realflo documentation (version 6.94.1 or 6.95.1 respectively) for
further information on the new functionality available in these firmware releases.

ClearSCADA 2017 Release Notes – July 2018 Update Page 22 of 49

Updated bundle of OPC Factory Server (OFS)
The installation of Schneider Electric’s OFS has been updated to v3.60 SP3, which includes
the following enhancements:

• Support for communications redundancy to Unity PLCs

• Adjustments to the communication flow recovery
• Support for PLC timestamped variables
• Enhanced Unity Pro types conversion
• PL7 arrays conversion
• Access to the status of data dictionary in OFS server for an alias, and
• An update to the communications drivers for Modbus Serial, PLC USB, UniTelway
and XIP.

Please refer to associated OFS v3.60 SP3 documentation for further information on the new
functionality available in this release.

ClearSCADA 2017 Release Notes – July 2018 Update Page 23 of 49

System Administration and Security
ClearSCADA able to run as Non-System User
As an additional security measure in ClearSCADA 2017, ClearSCADA can now be
configured to run under a local Administrator account rather than the Windows® System
User, maintaining access to the necessary Windows® services. It is also possible for
ClearSCADA to run under a Windows® virtual account (or other) with reduced functionality
according to the permissions assigned to that user account. The functionality which will be
lost is the ability for ClearSCADA to perform System Commands and print Crystal Reports.

This is configured within the properties of the ClearSCADA Server service in Windows®
Services (accessible from the ‘Computer Management’ console), as below:

In addition, the following services now run under a less privileged Windows virtual account,
instead of the Windows® Local System account, for improved security:

• Port Server
• License Server
• AE Printer

ClearSCADA 2017 Release Notes – July 2018 Update Page 24 of 49

System Commands Now Require User Credentials
System Commands (also known as System Calls) are used to perform tasks within
Windows® externally to ClearSCADA, for example to automatically copy specific data to a
third-party application. System Commands can be triggered by ClearSCADA automatically
or on request by a user, and from a number of places within ClearSCADA:

• IEC 61131-3 Structured Text (ST) Logic

• System Command object
• System Command Action via Alarm Redirection

As an additional security measure in ClearSCADA 2017, System Commands now need to

be configured with a valid Windows User Account before they can be used by ClearSCADA.
A new enable/disable option for System Calls has been added to the Server Configuration
Tool, and when enabled will enforce that a Windows® user is specified.

The ClearSCADA server now checks that System Calls are enabled and have been
configured with valid user credentials before queuing a System Command. If System Calls
are disabled or the configured credentials are invalid, then an error will be reported. A new
‘Exit Code’ column has been added to the 'Database\Latest System Calls' page in the
ClearSCADA Server Status Tool to show the exit code of the process when the command
completes to aid in diagnosis.

Note: The above restrictions are automatically applied on upgrade to ClearSCADA 2017, so
all System Commands will cease working until a valid user account is configured.

New Utility to Clean Unused Areas of Interest

A new utility has been added to ClearSCADA to facilitate the quick removal of unused Areas
of Interest on your database, which is valuable when the list of Areas grows too large. This
utility is installed alongside the ViewX client in the ClearSCADA Program Files directory.

To run the AOI Cleaner utility, you can either:

• Run the utility directly from Windows Explorer, which will use default parameters.
• Run the utility from a Command Prompt window, where you can specify various
options to control some of the utility's activities and output. Use the “-?” or “--help”
argument for a full explanation of parameters that can be used.

In conjunction with this new utility to clean the Area of Interest hierarchy, the import facility
has been changed so that new Area of Interest items are now only imported from a SDE file
if used by objects in the database.

Note: If you have a large number of Areas of Interest in your database (for example, 500 or
more), it is recommended that you run the AOI Cleaner utility from a Command Prompt
window and specify options that optimize the deletion routine including “--reverse” and “--
delay”.

ClearSCADA 2017 Release Notes – July 2018 Update Page 25 of 49

Changes to Management of User Security Configuration
The Security Settings within the System Configuration section of the ClearSCADA Server
Configuration Tool has been modified to simplify management of Security Options.

Selecting a pre-defined security level no longer disables editing of the individual User
Account options; instead these options remain available for direct editing (by an
Administrator with appropriate permissions).

When a security option is changed to a value that deviates from the pre-defined security
level settings, the security level is automatically set to Custom. In the event that the options
are changed from a custom configuration to match a pre-defined security level, the system
will automatically select that level.

Tightened Super User Credentials

As in previous versions of ClearSCADA, a Super User is created during installation, although
it is recommended that this Super User is used only to create a suitable Administrator User
Account within the database, and then is disabled via the Server Configuration utility.

To reinforce implementation of best practice security, the Super User now enforces a 12-
character password to discourage extended use when a local Administrator User Account
object should be used instead.

When upgrading to ClearSCADA 2017, if the existence of a Super User account is detected,
you might be asked to enter new credentials to comply with the above changes.

Administration of the Wonderware Alarm Provider

New options have been added within the Global Parameters section of the Server
Configuration Tool to manage the Wonderware Alarm Provider (WWAP), allowing users to
enable/disable the Alarm Provider functionality altogether.

Enabling the Alarm Provider without InTouch or System Platform installed may, over time,
have an impact on the performance of the ClearSCADA server. For this reason, this option
defaults to False on upgrade to ClearSCADA 2017 and therefore should be enabled (and
then the server restarted) if the Alarm Provider is in use.

Note: For existing ClearSCADA users that wish to continue to use the WWAP service, it is
recommended that immediately after upgrade to ClearSCADA 2017 the WWAP service is
enabled via the Server Configuration Tool, and the ClearSCADA server restarted to avoid
loss of cached alarms.

ClearSCADA 2017 Release Notes – July 2018 Update Page 26 of 49

Updated Prerequisites
The prerequisite installers have been updated to use a new .Net 4.6.1 redistributable. As a
result, when upgrading to ClearSCADA 2017 you may be prompted to reboot the machine in
order to complete the installation.

Mobile Companion Installation

The ClearSCADA Mobile Companion installation was bundled with the new WebX installer
for ClearSCADA 2015 R1 and 2015 R2. The bundling of the Mobile Companion and WebX
installation has been reversed in ClearSCADA 2017, such that the Mobile Companion is now
a separate feature that can be selected during installation of the ClearSCADA Server.

ClearSCADA 2017 Release Notes – July 2018 Update Page 27 of 49

Enhancements

A Note Regarding the Evolution of ViewX

ClearSCADA ViewX up to and including ClearSCADA 2013 R2 used a Win32 application which
lacked flexibility for window arrangement and delivered a visual appearance that was not
modern. In these versions, ViewX could support multi-head (multi-monitor) displays by running
up to five separate ViewX instances, using command line switches to link them so that a limited
number of operations could be passed between heads. For example, a single logon could be
used across all heads, and alarm context menus could load displays on selected other heads. A
HEAD() function could be used in animations to place a head in a different display mode, and a
function in script could open a window on another head.

In ClearSCADA 2014 R1 a new ViewX client application was released that used WPF (Windows
Presentation Framework) technology, which enables us to take advantage of new windowing and
User Interface capabilities. ViewX now has the ability to manage multiple heads within the one
running instance, which delivers greater flexibility and interaction between displays. We have
recently included the capability for windows to be dragged and docked across heads, while future
capability could allow 'yoking' of heads and displays, so that a nominated head could
automatically show windows with their detail controlled by a parent head.

To aid transition between the different ViewX client applications mentioned above, from
ClearSCADA 2014 R1 ViewX has the ability to run multi-instance, and the ability to disable the
alarm bell from each head separately (available in ClearSCADA 2017). However, we are not
intending to add the ability to open windows across different heads or provide a single logon.
These features are available when ViewX is run as a single instance with multiple heads. In this
latter mode, multiple heads are set up in an XML file, which has a default name, or can be
specified in the ViewX command line.

The new features of ViewX which will be available in ClearSCADA 2017 and Service Packs of
ClearSCADA 2015 R1 and ClearSCADA 2015 R2 include:

• Super Favorites (that which saves multiple windows with all of their positions and layout)
will be saved across all heads.
• Support of the HEAD() expression (with non-shared embedded mimics).
• Drag and dock of any window between heads.
• Full operate and configure of any window on any head.

We do not expect the performance of ViewX in this mode to be significantly different, although
the ability to host many more heads can naturally affect throughput. When ViewX is extended
across many additional heads, the performance of ViewX may be susceptible to graphics
configuration that is improper or inefficient.

We are pleased that we have created this new ViewX user interface environment to facilitate the
enhancements outlined above, and the positive feedback we have received confirms that it is
delivering value to our users. We believe the changes in ViewX provide an enhanced user
interface.

ClearSCADA 2017 Release Notes – July 2018 Update Page 28 of 49

ViewX User Interface – General
ClearSCADA 2017 includes the following enhancements to ViewX:

• Shortcut key support for Ctrl-A (Select All) and Ctrl-C (Copy to Clipboard) has been
added to the Alarm Banner in ViewX.
• The ViewX Alarm Bell sound can now be disabled per-instance using a command
line switch '/bellSilenced'.
• The HEAD() function has been improved such that it returns the correct window
container for non-embedded and non-shared, embedded mimics. Calling the
HEAD() function from a shared, embedded mimic will return the primary window
container.
• Opening a document for the first time, or re-opening an existing document in a new
mode now switches the ViewX ribbon to the document's preferred ribbon tab.
o Mimic documents will set the ribbon tab to "Graphics" if they are opened in
design mode. If they are opened in run mode, the ribbon tab will not change.
o Script documents will set the ribbon tab to "Script".
o Logic documents will set the ribbon tab to "Logic".
• The ViewX User Interface is now hidden when a user session is locked after time-
out, displaying only the ‘Confirm Password’ window. If running ViewX across multiple
monitors, the multi-head applications are temporarily reduced to display only a single
icon in the Windows® Taskbar. Once a user successfully confirms their password to
logon again, logs on as another user, or ends their session by logging out, the full
ViewX User Interface is displayed once again (across one or more monitors, as was
the case before the session timed out).

ViewX User Interface – Multi-Monitor Configurations & Super Favorites

The functionality of Secondary window containers when using ViewX in a multi-monitor
environment has been improved, as follows:

• Horizontal and vertical tab groups and floating windows are now supported in both
Primary and Secondary window containers, allowing documents to be freely ‘dragged
and dropped’ to configure an ad-hoc document layout on any multi-monitor container.
• Windows may now be dragged and docked between containers.
• Editable documents can be placed into Design Mode (according to user privilege) in
a Secondary container.
• The most recently active document now has a different highlight color for its tab
control (if docked) or caption bar (if floating).
• Commands from the Ribbon and Quick Access Toolbar (QAT) now act upon the
most recently active document, regardless of which container it is in.

The Current Window and Insets option for saving of user Favorites has been removed in lieu
of the newer All Windows and Layout option. Existing user Favorites saved under the

ClearSCADA 2017 Release Notes – July 2018 Update Page 29 of 49

Current Window and Insets option will be interpreted and displayed, however the windows
will all be loaded as top-level (docked) windows, including those that were previously saved
as Inset Windows. These configurations should be adjusted and re-saved using the newer
All Windows and Layout option to maintain and restore layout preferences in full.

NOTE: A multi-monitor configuration is not intended for users restricted to Single Document
Interface mode, as this will impact the user experience. For example, in this scenario All
Windows and Layout Favorites will not operate as described above.

WebX Alarm Banner Row Limit

A new limit has been applied to WebX which, by default, restricts the Alarm Banner display
to list only the top 100 entries. When alarms are not able to be shown due to the above
restriction, an entry is added to the bottom of the Alarm Banner list stating that “Maximum
alarms for WebX shown”, followed by a count of the alarms that are not visible.

The default limit of 100 should be suitable for most users, although can be increased by
adjusting the “MaxAlarms” WebX Application Setting within IIS Manager.

NOTE: Increasing the MaxAlarms setting can negatively impact WebX performance. The
performance of WebX is dependent on your network bandwidth and rate of alarm updates,
so care should be taken when increasing the number of alarms displayed in the Alarm
Banner.

Enhanced Backup Functionality

The integrated Backup functionality within ClearSCADA 2017 has been expanded to save
the ClearSCADA Registry Keys of the Main server, capturing the Server Configuration
settings along with the Database configuration and Historical, Event and Alarm data (if
selected).

The Backup object now also includes an option to automatically create a .zip archive of the
saved Configuration and Data, allowing the user to configure the level of archive
compression applied, and following this the intermediate files can optionally be removed to
save disk space.

Server Synchronization
ClearSCADA Standby servers are now able to resume synchronization after momentary
glitches in connectivity, reducing the time required to achieve full synchronization.

The Standby server will only resume an interrupted synchronization when it has remained in
the Standby state (and not assumed Main server responsibility) and when the Main server
has not changed.

ClearSCADA 2017 Release Notes – July 2018 Update Page 30 of 49

Online Help – Frequently Asked Questions
A new 'Frequently Asked Questions' topic has been added to the help to answer some of the
questions you might have about ClearSCADA. You can find the topic in the 'Getting Started'
branch.

Online Help – Technical Reference Guides

The Server Automation Guide and SQL Technical Reference Guide have been incorporated
into the main Online Help documentation. With previous releases of ClearSCADA, these two
guides were only available as separate .chm help files. Both guides now appear in the
'Coding' section of the 'Core Reference' branch.

ClearSCADA 2017 Release Notes – July 2018 Update Page 31 of 49

Recent Updates

Resolved Customer Issues – July 2018 Update

• Fixed potential problem with FN TIMESTAMPDIFF in a SQL statement returning the
incorrect value.
• [SUP-9537] Improved dragging of horizontal and vertical lines in the ViewX mimic
editor.
• [SUP-9938] Extended GetState Poll filtering during Main Server Change-over, to
avoid late poll's processing resulting in spurious link state change.
• [SUP-9614] Corrected the latest values written by eDNA Historic export on startup.
• [SUP-10231] Fixed ViewX not subscribing to notify user messages.
• [SUP-9116] Changed all OPC quality database fields from DB_WORD to
DB_UWORD to correctly handle the full 16-bit quality value.
• [SUP-9967] Accommodate externally managed user groups being assigned to user
patterns. Previously this would result in the user having duplicate memberships,
raising a validation error.
• [SUP-10195] Retrieval of LDAP group memberships will now exclude distribution
groups and correctly handle loops in recursive group memberships.
• [SUP-10184] Fixed configuration change interest mechanism on standby servers
when an object is converted to a different type (so that both delete event for old
object and create event for replacement object are generated). This fixes an issue
with drivers running on the standby where they didn't receive the required interest
events to maintain their internal database, which then lead to issues once the server
become main.
• [SUP-10189] Fixed Advanced OPC driver crash when a point with persistence is
waiting for the persistence time to elapse when the point or its group is disabled.
• [SUP-10186] Fixed issue with moving a point with historic exports (WWH or eDNA)
into a template not removing the historic export data from the point, which would lead
to a server crash if the database was loaded on a a server without the appropriate
driver (WWH or eDNA) installed.
• [SUP-10050] Corrected behavior of ScxCmd HISSTRIP and CS historic
optimize/duty-duty merge functions with regard to record ordering and duplicate
removal. Previously records with the same timestamp and value could be incorrectly
detected as duplicates, even if they were not consecutive (for example, a point
rapidly toggling between two values). Additionally, records with the same timestamp
could be sorted into an incorrect order based on other attributes.
• [SUP-10056] Modified OPC-AE event subscription mechanism to give individual
event clients more control over sending simple and tracking events to clients. This
allows an individual client to subscribe to simple events whilst
DB\SendSimpleAndTrackingEventsToClients registry setting is set to false.
• [SUP-10120] Fixed error in logon counts when user is logged off due to inactivity.

ClearSCADA 2017 Release Notes – July 2018 Update Page 32 of 49

Resolved Customer Issues – June 2018 Update
• Caught exception when ViewX attempts to update user location on a standby server
with a different version to the main server (e.g. during server upgrade).
• [SUP-9770] Changed wording of warn user settings changes may not take effect until
next logon.
• [SUP-10161] Fixed pager messages with beep code.
• Fixed database integrity check failures on SCADAPack E Outstations with binary
points configured to read 16-bit Modbus register.
• [SUP-10048] Fixed an advanced driver crash when the creation of multiple objects
due to database changes is blocked waiting for the deletion of one object.
• [SUP-9389] Added range validation to the Password Expiry setting (0-365 days) and
the Password Expiration Warning setting (0-31 days)
• [SUP-9968] Fixed issue with incorrect configuration change logging when a template
contains an abstract object with a property override on a field, and then a second
template contains an instance of the first template in which the abstract object is
converted to a 'real' object and the overridden field is modified and the unmodified
configuration of the first template is re-imported. This also affected with all instances
of the second template.
• [SUP-9971] Updated database copying of objects so that an error is shown if the
user does not have 'Configure' privilege on the source object.
• [SUP-10122] Corrected ViewX to log events for inactivity logout.
• Updated the error message that is displayed when trying to edit a Crystal Report but
the SAP Crystal Reports application is not installed. The error lists the supported
versions of SAP Crystal Reports and has been updated to remove old versions which
have reached their end-of-life and to add the latest versions (2013 and 2016).
• [SUP-10041, SUP-8841] Prevented deletion of a template instance from inside
another template instance when the template instance object is configured to
reference different templates in the instance and the template.
• Fixed possible server crash when a template instance contains a group whose name
matches that of a template instance object in its controlling template. This can only
happen when a template Id field is property overridden.
• [SUP-10091, SUP-10105] Fixed server crash when converting an object with
aggregates during main-standby synchronization, and new object has different
aggregates to the original, for example converting a 'DNP3 Binary Output Point' to a
'DNP3 Pulse (NULL)' loses the 'Historic' aggregate.
• [SUP-9993] Fixed DNP3 driver crash when downloading configuration to a
SCADAPack E and the outstation sends an unexpected link layer response (e.g.
ACK) to the restart config command.
• [SUP-9977] ODBC v2.1 driver updates to avoid crashing Excel 'Get and Transfer'
features.
• [SUP-10129] Update Australia and New Zealand contact details in about boxes.

Resolved Customer Issues – May 2018 Update

• [SUP-10064] Fixed an issue with WebX menu item visibility not obeying its
Expression.

ClearSCADA 2017 Release Notes – July 2018 Update Page 33 of 49

 • [SUP-9803] Modified importing of historic data into a time profile to take account of
the time zone of both the profile and the user / client.
• Added NoCacheAttribute to all WebX API requests to prevent stale data.
• Ensured that user is returned to the login screen of WebX if DBServer is shutdown or
restarted.
• [SUP-9827] Fixed problem where animated items on a mimic could start to 'drift' out
of position after a long period of time. Switching between documents no longer
causes unexpected changes to animated items on a mimic.
• Added Spanish resource updates.
• [SUP-9782] Corrected Mobile Servers use of worker threads to check license status.

Resolved Customer Issues – April 2018 Update

• [SUP-9883] ViewX now supports documents which are in an 'error' state when saving
or loading a super favorite.
• [SUP-10015, SUP-10017, SUP-10011] Fixed “Locate In Database Explorer” causing
a crash in ViewX when the explorer bar hasn't been shown.
• [SUP-9950, SUP-10075, SUP-10073] Display dialogs relative to windows that have
requested pick action in ViewX.
• [SUP-9887] Removed form option and downloading of SCADAPack E Default
Gateway IP Address.
• [SUP-9885] Improved Advanced EWS driver handling of historic retrieval from
ClearSCADA EWS Server when no historic data is returned by the server.
• [SUP-9594, SUP-9975] Fixed the following issues with server-side expressions, as
used by calculation points, historic calculations, method calls (including user
methods, schedules, backups etc.), data grids, data set rows and template
expressions:
o A server-side expression could not be a Boolean expression, such as
"MyPoint.CurrentValue" = 10, except in a template expression.
o A server-side expression containing an extra token after the end of the
expression often didn't give a validation error, for example
"MyPoint.CurrentValue"wibble. The extra token was silently ignored.
• [SUP-9524, SUP-9998] Prevented possible stall of the configuration transaction
queue.
• [SUP-8107] Fixed standby server crash that could occur when syncing new
journal/config change/alarm summary streams while the streams are being accessed
by another operation (for example, journal stats calculation). Fixed fetching alarm
summary data from standby in a duty-duty system and removing alarm summary
data on standby in other cases.
• [SUP-10012] Fixed conversion of double precision floating point values and 64-bit
integer values from big endian to little endian when the most significant bit in the
value is set, for example 9.9. This effected the Advanced Modbus and Sofrel drivers
that convert from big endian (in the Modbus protocol) to little endian (x86), and was
leading to corrupted point values, including invalid floating-point numbers (NaN).
• Corrected API stream of Editing annotations via .Net.

ClearSCADA 2017 Release Notes – July 2018 Update Page 34 of 49

Resolved Customer Issues – March 2018 Update
• Added new configuration mapping format 2 for Wonderware eDNA driver.
• Updated Wonderware eDNA Libraries. (EzDnaApi64.dll, EzDnaApi32.dll version
2.24.0.182 and EZDnaServApi32.dll, EZDnaServApi64.dll version 1.25.8.7)
• [SUP-10009] Corrected SP50 Data Message 'DS' time delta parsing.
• [SUP-9957] Added support for formatting IP address field values in configuration
changes history using standard dot notation, e.g. 127.0.0.1, instead of showing raw
integer value.
• [SUP-9945] Fixed potential server crash when querying historic data or custom
historic tables.
• [SUP-9941] Ensured traces are correctly shown on XYZ Plot in WebX.
• Purge mimic from embedded mimic cache when embedded mimic is deleted from the
database.
• [SUP-9928] Improved detection of types in ViewX for pick action dialog parameters.
• [SUP-9782] Added protection to ensure the MobileCompanion service terminates
when requested. Added global exception handling to the MobileServer to detect
unexpected failures.
• [SUP-9903] Fixed resizing of insets when reducing window size.

Resolved Customer Issues – February 2018 Update

• [DEV-10180] Correct Pager UCP Response parsing of numerical values.
• [SUP-9937] Read Device Attributes on Startup property on DNP3 outstations is now
correctly copied when template instances are created.
• [SUP-9154] Corrected Pick action in Mimics losing context of aggregates.
• [SUP-9731] Prevent spurious removal of CS user group memberships for certain
failure cases during LDAP-based logon. Resolved possible inability to update group
memberships when an externally authenticated user logs in via their CS username.
• [SUP-8592] In addition to UPC Pager message limit, implemented expedient
handling of informal flow control.
• [SUP-9739] Fixed a DNP3 driver lock up that can occur when using a SCADAPack E
shared outstation with heartbeating enabled and a SCADAPack E Status Information
object with a scan group configured (for DNP3 level 3 polling)
• [SUP-9923] Prevented ViewX from attempting to bring a queries explorer node that
can't be displayed into view when switching users.
• [SUP-9903] Corrected problems with Navigate and Resize functionality within ViewX.
• [SUP-9731] Added timeout and retry count to LDAP queries during logon.
Configuration is currently via registry only.
• [SUP-9606] Fixed LicenceServer running under NT SERVICE\LICENCESERVER
account and improved logging of failure to initialise a licence file.
• [SUP-9909] Purged changed embedded mimic from mimic cache when altered and
not on screen.
• [SUP-9859] Added VC 2015 runtime binaries to WebX client cab.
• [SUP-9898] Corrected Duty Duty Mode initial sync of newer data on Standby server.
• [SUP-9846] Fixed shared mimic linking to incorrect target.

ClearSCADA 2017 Release Notes – July 2018 Update Page 35 of 49

 • [SUP-9828] Corrected back port, to fix WebX Trends named with Unicode special
characters.
• [SUP-9810] Prevented ViewX crash when connecting to a pre V78 server. Removed
"Display On Map" from pick action menus that can't be displayed on a map.

Resolved Customer Issues – January 2018 Update

• [SUP-9696] Keep embedded mimics in cache after the last mimic referencing them is
removed to improve loading times of mimics that use them. Embedded mimic cache
size defaults to 300.
• [SUP-9791] Fixed alarm list filtering so that when a new filter is applied which
excludes pending events for alarms that have just changed, that these events are not
sent to the client, causing the alarm list to show alarms that should be excluded by
the new filter.
• [SUP-9345] Fixed bug where LogOptions were being overwritten when log file
settings were edited on a stopped driver.
• [SUP-8654] Excluded disabled alarms from ActiveAck, ActiveUnack and
ClearedUnack calculations.
• [SUP-9823] Corrected ODBC Client Driver's handling of queries >32K characters.
• Fixed intermittent crash when shutting down ViewX.
• [SUP-9775] Updated MailKit, MimeKit and Bouncy Castle Libraries.
• [SUP-9565] Changed behavior of security tab on User form when external
authentication is selected.
• [SUP-9565] Fixed issues related to security tab on User Pattern forms.
• [SUP-9772] Fixed Server crash when using eDNA Historic Export.
• [SUP-9782] Improved logging for Mobile Server. Reduced the number of round trips
to the Mobile Server for requests navigating the database from the Mobile App.
• [SUP-9846] Improved handling of embedded mimic pick actions.
• [SUP-9627] Fixed WebX displaying processed historic traces to use local time zone.
• [SUP-8899] Removed SQL Compact from main installer.
• [SUP-9852] DNP3 Slave corrections:
o Corrected default value for StringEventObject property on DNP3 slave
outstations to Octet String (g111), rather than Not Generated. Note:. Any
database that has already been upgraded to 6.78 will need to be manually
changed to restore the original behaviour (from older versions).
o Fixed DNP3 slave outstations when string event objects are configured as not
generated. Events were still generated, but not reported in the response to a
class poll, only the response to group 111 or group 115 poll. A side effect of
these bugs was that the IIN class flags could indicate that events are
available, but a class poll by the master didn't retrieve the events, leading to
the IIN class flags becoming 'stuck'.
• [SUP-9856] Expression entry dialog corrected to allow keyboard navigation: now
preventing tab characters from being typed in the Expression entry dialog.
• [SUP-9873] Fixed SCADAPack Realflo configuration upload for version 6.76 to 6.89.

ClearSCADA 2017 Release Notes – July 2018 Update Page 36 of 49

 • Corrected Server Configuration tool to disable feature switch 'Protected Permanent
Standby Servers when increasing online period' on Permanent Standby servers –
only configured on Hot Standby servers.
• Fixed potential ViewX crash when editing embedded mimics.
• [SUP-9764] Fixed crash when querying CLUFKINSAMSOSDIRECT table.

Resolved Customer Issues – December 2017 Update

• [SUP-9664] Watchdog's default dump type changed to 'Normal' and ServerStatus
visibility improved.
• [SUP-8592] Fixed Pager UCP's send message limit, to ensure modem call is
dropped on reaching limit.
• [SUP-9769] Modified conversion of point instances to leave Process Count Time
unchanged.
• [SUP-9781] Fixed logging to archive files for Mobile services.
• [SUP-9785] Corrected handling of interaction with objects on mimics.
• [SUP-9785] Prevented embedded mimic pointers being cached longer than needed.
• [SUP-9774] Fixed mimic navigation history getting out of sync.

Resolved Customer Issues – November 2017 Update

• [SUP-9556] Fixed fonts not being created before attempting to draw Graph
documents in ViewX.
• [SUP-9728] Removed spurious QP 'UpdateProgress' diagnostic logging messages
when no client to be advised of updates.
• [SUP-9629] Fixed error in ClearSCADA backup feature when backing up the registry
for a non-default database.
• [SUP-9744] Allow clients to connect to fully synced standby servers when the
"Connect To Fully Synchronized Server Only" option is selected in the Client
Configuration.
• [SUP-9745] The Lufkin SAM driver now correctly converts downhole data time
stamps to UTC.
• [SUP-9715] Modified the Main/Standby process that checks for historic files changes
to use a database read lock rather than a write lock.

Resolved Customer Issues – October 2017 Update

• [SUP-9596] Expedient reduction in ViewX diagnostic logging associated with mimic
redrawing.
• [SUP-8592] Implemented Pager Driver UCP messages per call limit, as a server-
level configurable limit.
• [SUP-9711, SUP-9718] Prevented unexpected loss of comms with DBServer from
crashing ViewX.
• [SUP-9563] Updated WebX installer to handle upgrades more gracefully
• Fixed memory leak when performing queries with summary functions.
• [SUP-9654] Fixed the broken keyboard shortcut (F10) for displaying an Events List.
• [SUP-9613] Fixed issue where tuned limits are not copied by a Convert To operation.

ClearSCADA 2017 Release Notes – July 2018 Update Page 37 of 49

 • [SUP-9662] Fixed ViewX crashing when occasionally picking the wrong top level
window to use as a parent for modal dialogs.
• [SUP-9406] Fixed displaying ad-hoc trends for digital points with a ' in their name.

Known Issues – September 2017 Update

• An issue with the July and August updates has resulted in a need to repair ViewX
installation post upgrade. This can be done by repairing the ClearSCADA installation
immediately after the upgrade or when ViewX is first run it will automatically repair
itself. This issue does not affect the operation of ViewX in either the July/August
update or the September update.

Resolved Customer Issues – September 2017 Update

• [SUP-9637] Corrected Advanced OPC Analog's scaling functionality.
• [SUP-9605] Updated Base64 encoding to support Unicode characters in database
object names in WebX.
• Fixed problems with New WebX and object names with characters ~ or /. failing to
load.
• [SUP-9492] Corrected point persistence's handling of point updates made during a
persistence period which is ultimately cancelled.
• Corrected some issues with Trio Advanced Driver Copy/Save/Load.
• [SUP-9625] Corrected validation of template's Time Profile object when it has no
profile values.
• [SUP-9604] Fixed server exception when combining data tables with sub-queries.
• [SUP-9363] Fixed calculation of database backup diagnostic so the phase is
displayed correctly.
• [SUP-9511] Fixed Alarm banner not configuring properly on first creation if Guest
User can't view it.
• Updated Intended Use text on builds to be white and not bold.
• [SUP-9598] Improved the behavior of the embedded mimic cache with respect to
closing mimic documents.
• [SUP-9148, SUP-9193] Fixed issues with new points being updated with a quality
only change before the point has any data. This could cause an invalid historic data
record to be created (record has no value).

Resolved Customer Issues – August 2017 Update

• [SUP-9300] Corrected SCADAPack E Modbus scanner configuration for DNP3
binary points reading Modbus 16 bit registers.
• [SUP-9501] In the Server Configuration tool 'System Configuration | Alarms, Pre-
defined Alarm Comments' and 'System Configuration | Security, Client Access
Control List' are now correctly initialized.
• [SUP-9309] Modified the "Max Windows" dialog so that it updates itself as the user
closes selected windows.

ClearSCADA 2017 Release Notes – July 2018 Update Page 38 of 49

 • [SUP-9381] Modified Advanced Driver library so that it can safely handle point data
cache updates for the same outstation on different threads (caused by device
configuration error).
• [SUP-9217] Improved the inactivity logoff functionality within ViewX. Content which
previously remained onscreen during an inactivity logoff (usually, interop'd dialogs) is
now removed.

Product Enhancements – July 2017 Update

The July 2017 update of ClearSCADA 2017 includes the following enhancements:

• In conjunction with the update in April 2017 to allow ViewX to logout when the
inactivity timeout expires and there are no pending document changes, new options
have been added to configure ViewX Inactivity Shutdown, allowing for ViewX to both
log out the current user and shutdown after a period of inactivity, releasing its license
to be used by another concurrent user (if using a server-side floating license).

Resolved Customer Issues – July 2017 Update

• [SUP-9263, SUP-9494] Reduced frequency of Query Processor 'Progress Update'
messages to improve query performance.
• [SUP-9445] Fixed display of UTC time in the ViewX status bar.
• [SUP-9226] Fixed DNP3 slave outstation retrying of unsolicited responses when no
application confirm or data link ACK is received.
• [SUP-9280] Removed the SQL as part of the Error Message when there is badly
formed SQL in a list view so as not to obscure access to the 'return to the previous
query' or 'edit the current query' options.
• [SUP-9367] Fixed potential access violation that could occur when closing a mimic.
Improved the clearing of mimics from the embedded mimic cache when closing
ViewX.
• [SUP-9395] Corrected restarting of the WebServer, when WebX OPC-DA
Subscription Refresh occurring.
• [SUP-9406] Fixed parsing of TrendSpecs to allow for objects with ' in the source
name.
• [SUP-8979] Added version check to connection from ViewX to prevent trying to
connect to older unsupported server versions.
• [SUP-9160] Added password expiry warning dialog to ViewX.
• [SUP-9327] Fixed ViewX exception that could occur when mimic script is used to
get/set parameter values.
• [SUP-9384] Fixed server exceptions / memory leaks associated with closing a server
link (for a client, including drivers) whilst the server is executing a request from the
client on a worker thread.
• [SUP-9404] Added MinimizeRibbon option for primary window containers in the
ViewX StartupConfiguration.xml

ClearSCADA 2017 Release Notes – July 2018 Update Page 39 of 49

 • [SUP-9453] Improved caching of mimics within ViewX.

Resolved Customer Issues – June 2017 Update

• [SUP-9002] Resolved scenario where extending the duration of historic storage on a
Main server while a Permanent Standby server has greater duration of historic
storage could result in loss of historic data on Permanent Standby server.
• [SUP-9371] Fixed non-continuous accumulators to they don't reset on first update
following server startup.
• [SUP-9400] Fixed rack and slot number encoding in Simatic S7 packets. Added
validation for the values supplied by the user.

Resolved Customer Issues – May 2017 Update

• [SUP-9430] Fixed server delay which could occur when a QP link is closed and the
client still has a list on display from a query which then has an update to an item in
the list.
• [SUP-8596] Fixed display of popup menu from mimic so it appears on the correct
monitor in WebX.
• [SUP-8993] Fixed WebX exception that could occur when clicking on a mimic button
when mimic has not fully loaded.
• [SUP-9258] Documents may now be dragged and docked between any configured
heads within ViewX.
• [SUP-9372] Allowed Talus T4e WITS extension driver to add extra configuration files
to those downloaded and activated.
• [SUP-9423] Corrected QP's handling of UNION'ed queries using Interest and which
receive updated values.
• [SUP-9415] Improved SOAP requests (e.g. ViewX scripting) performed as Guest
user.
• [SUP-9329] Improved operation of ribbon commands for floating windows.
• [SUP-9343, SUP-8935] Modified DNP3 driver to allow for continuous polling of class
event data when 'Ignore Events Available Interval' is set to 0.
• [SUP-9353] Updated CEFSharp to version 57 to resolve some intermitting mapping
display issues.
• [SUP-9325] Improve .NET API secure socket performance.

Resolved Customer Issues – April 2017 Update

• [SUP-9170] Fixed scenario where users were not correctly logged off when their
account is disabled.

ClearSCADA 2017 Release Notes – July 2018 Update Page 40 of 49

 • [SUP-9191] Added an option to the Wonderware Historian object to specify whether
tag names include the aggregate name suffix. The option defaults to enabled when
upgrading existing databases, but disabled for new WWH objects.
• [SUP-7265] Improved DNP3 driver's solicited response state machine to correctly
handle receiving a fragment with the wrong sequence number when waiting for the
first fragment of a response, so that if the correct response is subsequently received
then it will be processed and not discarded.
• [SUP-9316] Added option to allow ViewX to logout without a dialog when the
inactivity timeout happens and there are no pending changes to documents for that
system.
• [SUP-9344] Fixed server exception that could occur when parsing a method call
containing an invalid group or object name, e.g. when receiving a pager message
containing a method call.
• [SUP-9336] Fixed modifying a range of values (from a trend) when a comment is
required.
• [SUP-9320, SUP-9324, SUP-9323] Fixed ViewX scripts using the Server object
giving access denied errors when user logged in using Windows username.
• [SUP-9070] Prevent possible Server exception that could occur when alarm
summary feature is enabled and an alarm is disabled and suppressed.
• [SUP-9232] Improved parsing of large integer literals bigger than 2^63, promoted
Unsigned 32 bit integer values to signed 64 bit values in Query Processor to improve
comparison operations.
• [SUP-8475] Re-implemented the creation of DBClient log files for processes that do
not set an explicit name for the log, for example OPC clients, ODBC clients, and the
server status utility.
• [SUP-9208] Extended OEM SDK for WITS extension drivers to provide interfaces for
getting a WITS outstation's profile data.
• [SUP-9285] Fixed import & merging an SDE file containing a group which has the
same name as an existing template instance; previously the instance was deleted
(including all the objects in the instance) and a new empty group was created, now it
converts the instance to a group. Fixed import & merging an SDE file containing a
template instance which has the same name as an existing group; previously the
import was aborted, whereas now it converts the group to an instance.
• [SUP-8972] Allowed New WebX to handle mimic names with asterisk ('*') characters.
Disallowed ActiveX Control from accepting backslash ('\') characters in mimic names.
• [SUP-9088] Reset Failed Logon Count upon successful logon to a Standby via WebX
and ViewX.
• [SUP-9138] Fixed drivers from queuing multiple hang-up modem requests after the
modem has dropped the connection, which can delay subsequent calls or cause
them to timeout. Fixed driver exception that could occur if an open line request to dial
an outstation times out (scanner command timeout). Improved operation so ATH0
command is sent to the modem when the modem has dropped the connection
(detected by DCD signal) and a "NO CARRIER" message is received from the
modem during the pre-guard wait (for command mode) before sending the ATH0
command.

ClearSCADA 2017 Release Notes – July 2018 Update Page 41 of 49

 • [SUP-9167] Datasets now support (and use by default) dynasets for faster interest-
based updates and reduced data transfer to clients.
• [SUP-9170] Standby servers now act on user accounts being disabled for logged on
users.
• [SUP-9213] Added missing serialization of off-scan alarm for advanced driver pulse
actions to resolve scenario that could cause an alarm to be permanently disabled on
standby server.
• [SUP-9238] Fixed ViewX exception that could occur when saving a Crystal Report
after the underlying Crystal Report Database Object has been deleted.
• [SUP-9249] Improved handling of SQL queries containing conditions such as
"WHERE (Col > X AND Col < Y)" when the lower bound X is greater than the upper
bound Y.

Resolved Customer Issues – Initial Release (March 2017)

• [SUP-5073] Fixed display of alarm time in WebX Alarm List to show local client time.
• [SUP-5717] Fixed current data retrieval on ViewXCtrl trends to resolve scenario
where a mix of timestamped and untimestamped responses from the server could
result in zig-zagging trace.
• [SUP-5723] Resolved server exception that could occur when importing a database
backup.
• [SUP-6536] Resolved exception in the Trio Diagnostics driver that could be caused
by a receive buffer overrun.
• [SUP-6544] Corrected misleading driver/communications log messages when a
DNP3 PSTN outstation dials in and send confirmed user data without a link reset.
• [SUP-6998] Fixed exception in ViewX that could occur when calling the Dynacard
Store's InsertRecords method with invalid arguments.
• [SUP-7231] Fixed display of partially synchronized watermark for empty WebX
queries.
• [SUP-7264] Fixed exception in the DNP3 driver that could occur at the transition
to/from daylight saving time when using a SCADAPack E outstation in the 'Local with
DST' time zone and the outstation was warm reset prior to the DST transition time.
Fixed scenario where the DNP3 driver was repeatedly attempting to set the DST flag
in a SCADAPack E outstations when DST is disabled in Windows (on main server),
but was previously enabled.
• [SUP-7355] Resolved exception that could occur in advanced drivers when On
Demand outstation with invalid host address attempts to connect.
• [SUP-7506] Fixed exception in the Advanced Driver that could occur when shared
outstation with heart-beating is promoted scanning.
• [SUP-7626] Improved handling of SQL parameters.
• [SUP-7687, SUP-8310] Fixed server exception related to non-thread safe code in
historian loaded granule lists.
• [SUP-7791] Fixed scenario where creating a new object in the database hierarchy
could jump the focus of the hierarchy to the $Root group

ClearSCADA 2017 Release Notes – July 2018 Update Page 42 of 49

 • [SUP-7834] Fixed next scan time calculations for simple drivers following the
server/scanner paradigm.
• [SUP-7851] Resolved channel lockup that can occur if the channel is reconfigured
while an incoming call is being handled.
• [SUP-7929] Fixed server exception that could occur when deleting large groups.
• [SUP-8071] Fixed scenario where a DNP3 outstation was not marked as “Failed”
after exceeding the maximum failed transactions, due to receiving at least one good
transport segment in the response to each of the unsuccessful requests.
• [SUP-8094, SUP-8102, SUP-8397] Modified historic flush parameters so they can
optionally be specified in absolute MB rather than percentages.
• [SUP-8137] Fixed scenario where incorrect data could be returned when using layers
within scripts.
• [SUP-8143] Expanded existing documentation to further explain the functionality
relating to 'End of Period Reset’.
• [SUP-8189] Limited the frequency of displaying SQL query progress messages
onscreen to reduce overflow of the Windows message queue which could result in an
exception.
• [SUP-8207] Converted an orphaned instance to a group on Import and Merge.
• [SUP-8210] Added support for Ctrl-A and Ctrl-C accelerator keys to the ViewX Alarm
Banner. Added the Copy context menu to log view of logic programs.
• [SUP-8215] Database tree interaction now selects the collapsed node if the selected
item has been hidden.
• [SUP-8219] Resolved a scenario that could result in a driver exception when saving a
SimaticS7 scanner after the scanned range changes.
• [SUP-8221] Resolved scenario where advanced driver point controls would not
correctly update point state based on controlled value.
• [SUP-8224] Fixed provisional logon when used in main-standby environments with
Windows authenticated users.
• [SUP-8236] Fixed an exception that could occur when closing mimics containing
embedded content.
• [SUP-8244] Fixed scenario that resulted in duplicate security errors when importing
objects with invalid security configuration.
• [SUP-8245] Improved support for XMLDA servers.
• [SUP-8247] Fixed exception that could occur in ViewX when navigating between
mimics using the script events Mimic_Load and Mimic_Navigate.
• [SUP-8257] Modified the ViewX application title to include the full name of the
currently open document.
• [SUP-8284] Fixed main-standby synchronization of an object with historic files which
is converted to a different type and the historic files persist across the conversion.
• [SUP-8295, SUP-8734, SUP-8449] Corrected display of the time field in the Event
List when using a custom format mask.
• [SUP-8308, SUP-8311] Fixed potential exception that could occur when closing a
trend, or navigating to another document.
• [SUP-8328] Corrected WebX iFrame display configuration.

ClearSCADA 2017 Release Notes – July 2018 Update Page 43 of 49

 • [SUP-8337] Improved Advanced Modbus Driver to fix memory leak that could occur
when polling string point and to fix an exception that could occur when writing string
values that span more than one packet.
• [SUP-8349] Fixed exception that could occur when displaying a mimic with an
embedded list.
• [SUP-8353] Fixed scenario where the final attempt to connect to a network direct on-
demand could be marked as “Failed” and left the outstation in the "Retry Connection
Pending" state when there are no requests to be retried.
• [SUP-8367] Corrected logging of User Inactivity in Original WebX and ViewX.
• [SUP-8378] Improved data table methods to make them consistent with data grids
and data sets.
• [SUP-8385, SUP-3893] Improved accuracy of query results when using empty string
criteria searches.
• [SUP-8386] Resolved “divide by zero” exception that could occur in WebX.
• [SUP-8388] Improved event message generated when a visible active alarm on a
suppressed object clears, so they are consistent with a normal alarm clearance event
message.
• [SUP-8391] Fixed scenario where the Method Call Command Alias would change
after a Main-Standby server changeover.
• [SUP-8408] Improved processing of updates on the standby server to enhance
Permanent Standby synchronization.
• [SUP-8413] Fixed data file cache so that size can be greater than 2047MB. Added
validation of data file cache size to enforce a minimum of 10MB. Added validation of
data file cache flush interval to enforce a minimum of 5 seconds.
• [SUP-8421, SUP-8533] Resolved an exception that could occur when opening a
mimic that contains one or more empty embedded mimics.
• [SUP-8428] Fixed exception in advanced OPC driver that could occur when an
asynchronous operation (e.g. a control) completes synchronously.
• [SUP-8440] Improved processing of adhoc trends in WebX.
• [SUP-8444] Fixed scenario where transfer of a datafile could cause all standbys to
disconnect and re-synchronize.
• [SUP-8450] Resolved exception in WebX server that could occur if
MobileSystemName is set to an empty string.
• [SUP-8451] Fixed GoBack and GoForward method from Mimic script.
• [SUP-8453] Corrected scenario where scripted hyperlinks to the same mimic would
not execute without the mimic being reopened.
• [SUP-8456, SUP-8470] Improved handling of links between WebX and DBServer.
• [SUP-8458] Allowed WebX maintenance to Repair and Exit from the installation
instead of relying on Cancel to exit with no changes.
• [SUP-8460] Historic Calculation's use of Historic Tags will now use Modified Historic
data, if 'Processed Uses Modified' configured.
• [SUP-8491] Fixed scenario where requests were becoming stuck in advanced drivers
when the connection to an incoming only TCP/IP direct on-demand outstation was
unsuccessful.
• [SUP-8498, SUP-6819, SUP-8586, SUP-7541] Corrected scenario where Simple
OPC driver would not process control commands.

ClearSCADA 2017 Release Notes – July 2018 Update Page 44 of 49

 • [SUP-8507, SUP-8846, SUP-8865] Improved handling of global keyboard shortcuts
within ViewX.
• [SUP-8519] Improved performance of trends in WebX.
• [SUP-8520] Improved display of trends in WebX.
• [SUP-8532, SUP-8415] Corrected downloading and uploading of configuration to
RealFlo outstations 4202GFC, 4202GFC_DS and SCADAPack 100 large memory
running version 6.71 and later firmware.
• [SUP-8536] Resolved exception of server that could occur when there was a
mismatch between Server Status structure and Server Status values.
• [SUP-8548] Fixed scenario where some mimics were incorrectly identified as empty
when embedded into other mimics.
• [SUP-8551, SUP-8563] Resolved server exception that could occur when deleting
large groups.
• [SUP-8556] Added support for generating secure session certificates on demand.
• [SUP-8563] Improved server stability when deleting large groups.
• [SUP-8569, SUP-8594] Resolved scenario where connecting older ViewX clients to
newer servers would incorrectly apply user profile settings.
• [SUP-8573, SUP-9379] Corrected the HEAD() function such that it returns the correct
window container for non-embedded and non-shared, embedded mimics.
• [SUP-8577, SUP-8856, SUP-8976] Fixed lockup of DBServer that could occur when
processing and generating a large number of text alarms.
• [SUP-8587] Applied improvements to resolve scenario where the browser would
freeze when using WebX.
• [SUP-8588] Fixed SQL Query Processor to allow INSERT of a LONG where the
LONG value is equal to LONG_MAX or LONG_MIN.
• [SUP-8591] The 'DownloadRequired' flag is no longer set on outstations that don't
support configuration download.
• [SUP-8593] Fixed scenario where receiving an unsolicited message would not reset
the number of failed transactions on an outstation, which could prevent an outstation
being marked as “Failed” despite many consecutive failed requests.
• [SUP-8598] Corrected the display of the time of server's Last State Change.
• [SUP-8605] Resolved scenario where ClearSCADA Mobile would try and check for
parents of $Root node. Cached MobileHelpLink during WebX and Mobile during a
lookup of an object in the database.
• [SUP-8607] Modified handling of Edit Security action so that object is revalidated
afterwards.
• [SUP-8609] Improved SCADAPack E Modbus Mapping Validation and generation.
• [SUP-8611] Cancel promoted scanning on ROC Plus and Total Flow drivers when
promotion time expires.
• [SUP-8626] The quality at the time when a point is overridden is now used when
logging a historic value if communication is marked as Failed.
• [SUP-8634] Added detection of runtime stack overflow in Logic.
• [SUP-8640] Data tables now relinquish the data file cache lock when queries release
the database lock.
• [SUP-8650] Fixed Realflo drivers uploading of K-Factor configuration for water flow
runs.

ClearSCADA 2017 Release Notes – July 2018 Update Page 45 of 49

 • [SUP-8651] Fixed Alarm Summary's validation of TextAlarms so Alarm Summary
TextAlarm records only visible when no Object Id criteria or special
CDBAlarmSummary Id -256 used.
• [SUP-8655] Corrected the behavior of the mimic zoom box in ViewX.
• [SUP-8656] Resolved an exception within the CFX Driver that could occur when
exporting historical data.
• [SUP-8658] Fixed scenario where an Inset Window could not be saved as a ‘Current
Window Only’ favourite.
• [SUP-8659] Fixed Advanced Driver exception that could occur when the socket for a
network direct on-demand outstation does not behave correctly whilst aborting the
current I/O operation due to a “no reply”.
• [SUP-8681] Corrected behavior of inactivity logout so a user can log back if they
originally logged in using their Windows user name.
• [SUP-8682] Corrected configuration fields downloaded for points exported to eDNA
historian.
• [SUP-8689] Improved consistency of point alarm clearance event journal messages.
• [SUP-8693] Fixed an unhandled exception in the timer of PLC to OPC Converter.
• [SUP-8702] Corrected SCADAPack E Modbus slave device query for points and
pulse objects.
• [SUP-8734] Corrected scenario where the millisecond part of the timestamp was
being truncated.
• [SUP-8751] Updated SNMP Device so that it correctly checks and applies the
Confirm Enable/Disable option.
• [SUP-8757] Corrected Advanced Modbus string points to enable the CurrentValue
property both for reading and writing. Additionally, corrected setting CurrentValue on
Advanced EWS string points.
• [SUP-8779] Improved application of transfer interval time-out for historic searches
performed during the standby transfer process.
• [SUP-8787] Improved the calculation of available space when dragging/docking
windows within ViewX.
• [SUP-8788] ST program function calls with named arguments now have the
argument count checked as per positional arguments.
• [SUP-8798] Provided Compressed Format option for FloBoss data tables, reducing
record size by >50%.
• [SUP-8804] Fixed exception in ViewX that could occur when removing a mimic
parameter.
• [SUP-8810] Added support for mail server implementations that do not provide a
SSL/TLS encryption when the connection is first made.
• [SUP-8820] Added ability for server to delete e-mails that do not have a Message-Id
when removing other relevant e-mails.
• [SUP-8834] Improved Backup examples in ClearSCADA Help documentation.
• [SUP-8839] Resolved scenario where the Trend Y-Axis would draw outside its
permitted area.
• [SUP-8840] Update Simple and Advanced OPC Drivers to work with legacy OPC
Servers only supporting interface IID_IOPCServerList.

ClearSCADA 2017 Release Notes – July 2018 Update Page 46 of 49

 • [SUP-8850] Fixed scenario where placement of on-screen keyboard could obscure
the active dialog.
• [SUP-8852] Added support for line wrapping of messages within the Method dialog.
• [SUP-8860] Corrected the display order of trend Y-Axes in WebX to be consistent
with order in ViewX.
• [SUP-8862] Disallowed the use of an invalid /root argument with ServerIcon and
DBServer.
• [SUP-8872, SUP-8905, SUP-9047] Resolved scenario where ClearSCADA server
would not start correctly following a server restart.
• [SUP-8891] Corrected TotalFlow driver's updating of point qualities for unsuccessful
communication scenarios. Corrected TotalFlow, FloBoss and RocPlus drivers’
handling of string points' quality updates when no string value present result in empty
string values by default.
• [SUP-8896] Fixed scenario where thousands separator was not being displayed
correctly in a formatted number in languages that use a non-breaking space as the
separator (for example Russian). Corrected 'Use 1000 Separator (,)' label in 'Text
Format' dialog to show the correct separator for each language (rather than always
showing comma).
• [SUP-8916] Corrected starting of scanner threads after initialization is complete
following a changeover and drivers go active on the Main.
• [SUP-8919] Fixed scenario where Copy option was not available on System Queries.
• [SUP-8924] Removed erroneous double space from name of standard High-High
Limit fields (US-English).
• [SUP-8927] Resolved a scenario where poor network connectivity can cause the
main server to become unavailable.
• [SUP-8934] Corrected memory management in ViewXCtrl ActiveX component of
legacy WebX which could have affected mimic scripts and non-shared embedded
mimic configurations.
• [SUP-8936] Fixed Kingfisher set and outstation address validation when set address
between 251 and 255.
• [SUP-8963] Added text wrapping to tooltips within the ViewX Messages Window so
long messages can now be read in their entirety.
• [SUP-8967] Resolved scenario where modifying certain configuration fields on points
could result in blank Last Modified time in the View Status dialog.
• [SUP-8969] Corrected the display of the time of server's Last State Change.
• [SUP-8981, SUP-9005] Made the use of DNS lookup configurable, for getting the
ClientName from Events list.
• [SUP-9033] Fixed periodic Calculation Points so that they continue to update on the
new Main server following an uncontrolled changeover.
• [SUP-9042] Corrected layout of the forms for abstract analog and counter points
which could get out of order whenever a change is made using the Server
Configuration Tool.
• [SUP-9052] Resolved scenario where new Instances containing Advanced OPC
points do not reflect the Template’s configuration for control properties.

ClearSCADA 2017 Release Notes – July 2018 Update Page 47 of 49

 • [SUP-9062] Fixed generation of Event Journal sequence numbers so they are
unique. Note that the sequence number is now a 64-bit number, and the invariant
record ID is now 48-characters long rather than 40.
• [SUP-9063] Closed down remaining WebX to DBServer links that were still open
after logoff.
• [SUP-9105] Fixed exception in ViewX that could occur when using script within non-
shared, embedded mimics to enumerate items on a layer.
• [SUP-9107] The AlarmSummary, PerformanceStats, GISAggr, and WebXConfig
aggregates are no longer exported to versions that don't support them.
• [SUP-9129] Resolved exception in ViewX that could occur when clicking on a Mimic
Pick Action.
• [SUP-9130] Fixed manual input of Template name in Template Browse Dialog.
• [SUP-9147] Improved implementation of schedules that are linked to a calendar.
• [SUP-9150, SUP-9101, SUP-9226] Corrected invalid 'maximum application fragment
size exceeded' alarm that could be displayed if the DNP3 driver receives an empty
application fragment from a remote device.
• [SUP-9156] Resolved invalid Event Journal entries that could be created when using
a newer version ViewX client connected to an older version Server.
• [SUP-9175] Improved SP50 Driver’s handling of Data Messages.
• [SUP-9186] Corrected starting of scanner threads after initialization is complete
following a changeover and drivers go active on the Main.
• [SUP-9187] Fixed exception in ViewX that could occur when closing a mimic
containing shared, embedded mimics.
• [SUP-9189] Applied the correct title across ViewX multiple window containers.
• [SUP-9194] Fixed server exception that could occur when running subqueries
redirected through SELECT *.
• [SUP-9196] Fixed exception in ViewX that could occur if no system is available and
the Guest user has a home mimic configured to be shown at logon.

Vulnerability Disclosure
ClearSCADA 2017 resolves a communications vulnerability present in ClearSCADA versions
released prior to December 2016, whereby malformed requests could be crafted by a
malicious actor and sent to the ClearSCADA server to cause termination of the ClearSCADA
DBServer process.

Further information on this vulnerability is available from the Schneider Electric

Cybersecurity Portal.

ClearSCADA 2017 Release Notes – July 2018 Update Page 48 of 49