📖HomeBack Please read the information below prior to installing SCADA Expert ClearSCADA 2013 R1.1a for important information on any known issues.
Mimics created in SCADA Expert ClearSCADA 2013 R1.1a cannot be opened from ViewX clients running version ClearSCADA 2010 R1.1 and older. This could cause ViewX to crash. This is due the addition of the default text border and graph key font in the newer versions.
SCADA Expert ClearSCADA 2013 R1.1a contains the new HTML version of the Online Help. On Windows Server 2003 and Windows XP machines, when starting the Online Help from any of the applications (ViewX, Server Status, Server Configuration etc.) for the first time, there may be a display issue with the topics displayed in the drop down list next to the Search option. This problem should disappear when the application is restarted.
During an upgrade from an older version to SCADA Expert ClearSCADA 2013 R1.1a on a Windows XP machine, the installation of the .Net Runtime component may fail. If this happens, restart the machine and re-run the SCADA Expert ClearSCADA 2013 R1.1a installer and the upgrade should complete successfully.
On a clean installation of SCADA Expert ClearSCADA 2013 R1.1a, the classes for OPCDA, OPCAE and OPCHDA are not registered. The user would need to open the Client Configuration dialog and click OK on the configured connection for the classes to be registered. This was changed to add support for the Systems.xml file.
Support for Internet Explorer 9/10
The following problems were identified:
When clicking on the 'List All Objects' from a class information page in the database schema, the list of objects may not display correctly. This is a problem with the Internet Explorer's XSL transformation related to elements with content and children.
Script functions such as 'Mimic.OpenInset' and 'App.OpenWindow' may not display properly on IE9/10.
Hyperlinks to lists may not display correctly due to the cross site scripting security filter in Internet Explorer. This also includes links to trends generated using the TrendSpec specification in ClearSCADA. The workaround for this is to disable the Cross-Site Scripting (XSS) filter in the web browser.