FIX: Movicon 11.6 (11.6.1200.10)

Problems fixed with the version: 11.6.1200.10

Build: 11.6.1200.10

Release Date: February 12 2019

ID	TOPIC	PROBLEMA FIXED
22765	Redundancy	The Secondary Project did not issue the Active State at the time the Primary returned available.
22581	Design	Supervision could be blocked if VB Script Resource was invoked simultaneously both from the Father Project and from the Son Project.
22847	Web Client	Continuously refreshing an HTML5 type Web page they could generate a block of the Server application.
22918	WinCE OS	A project achieved through an HTML5 Web Client session and communicating as OPC Client UA to an OPC Server UA could consume Memory and after many hours reach saturation of the RAM value reserved for processes started on Windows CE.

Minor Problem

ID	TOPIC	PROBLEM FIXED
22854	Design	The choice of the contextual function "Check Missing Strings" was also active in contexts of Project Resource where it could not be used.
23039	Design	Setting the Chinese language, the Tools menu displayed a partial list of items present in other languages.
22852	OPC Communication	The OPC DA Client Browser did not display correctly Items of an OPC DA Server which contained names with Unicode characters.
22903	OPC Communication	It was not possible to exchange an OPC UA Client variable of bit array type in Writing but only in reading.
22634	Screen Objects	If for a Display, set to use the Numeric Pad, the limits were set at runtime at the same value it was possible to insert any value on the Display.
22872	Screen Objects	The Combo Box object did not show the selection of the elements if the Selection variable "Tag Display" was set externally from the Combo Box object.
22986	Web Client	The HTML5-type Web Client was unable to open Parameterized Screens via the Parameterization Files.
22891	Web Client	Turning off the Mobile Phone or Tablet on which a session was started Web Client of type HTML5 did not disconnect Web Client users on the Server side causing consumption of Web Client Licenses. The problem was due to the fact that the forced closing of the Browser actually does not interrupted the TCP connection established with Movicon. Therefore an Inactivity Timeout has been introduced whose value is determined from the Network Connection TCP Downtime, after which time the connection is closed by the Server informing in the Log of the closing due to inactivity.