"set value" function in HTML Web Engine

"set value" function in HTML Web Engine

Description

When compiling a project for the HTML Web Engine, an error message is displayed for a set value function: "Variable not found." In the HTML Web Engine, the set value cannot be set via a button with this function. The button is not operable. However, setting the setpoint works in the Service Engine.

This error has been fixed. The variable is now linked correctly and the set value can be set in the HTML Web Engine.

To benefit from this fix:

  • Update your zenon Software Platform to the latest build of zenon 8.00 or higher.


Item ID: 173352
Version: 8.00 Build: 55271

    • Related Articles

    • set value" function in HTML Web Engine"

      Summary Set value functions are properly handled by the WebEngine compiler again. Description Set value functions are properly handled by the WebEngine compiler again. Information not available Issue Number: 173352 Fixed on Date: 28.1.2019 Versions: ...

    • Checklist: HTML Web Engine

      Time estimate: 20 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Screenshot and followed ...

    • FAQ: Which IE version is used by the HTML screen? Which Plugins can be executed?

      The HTML-screen created in zenon does not use the default-browser installed on the operating system. It uses the pre-installed rendering-engine of Microsoft, called "Microsoft Web Browser Control". This program emulates the Internet Explorer. ...

    • The Message „HTML 5 Web Engine Connecting to server“ appears with connection problem

      Description The Web Engine shows problems and the message "HTML 5 Web Engine Connecting to server" during the connection to the server with the zenon Service Engine Connector. This connection error occurs only sometimes. Cause: A deadlock occurs in ...

    • FAQ: Open Report Launcher on the web engine HTML screen

      This issue occurs due to cross-site scripting, causing the second HTML screen to be blocked and display a blank screen. It needs to check in IIS if report launcher SSL settings is on "Ignore". And also web engine SSL setting should have the same ...