The OPCUA server does not correctly handle limit texts (conditionname) with unicode characters

• Related Articles

• The filter in the detail view does not correctly display Unicode (Cyrillic) characters in the editor.

  Summary The filter in the detail view does not correctly display Cyrillic characters although the filtering itself appears to be working correctly in the editor. Description The filter in the detail view does not correctly display Cyrillic characters ...

• OPCUA32: Driver does not correctly import variables with special characters

  Summary OPCUA32: Driver does not correctly import variables with special characters. Variables are offered for import but do not communicate correctly during runtime due to incorrect characters in the addressing information. Description OPCUA32: ...

• The OPCUA32 client driver does not handle correctly string variable values that contain non-latin or non-ansi characters

  Summary String variables of the OPCUA32 client driver do not correctly display the string value if the string contains non-ansi characters or non-latin characters. DescriptionString variables of the OPCUA32 client driver do not correctly display the ...

• The editor closes unexpectedly when entering unicode (cyrillic) characters in the Equipment model

  Summary The editor closes unexpectedly when entering unicode (cyrillic) characters in the Equipment model DescriptionThe editor closes unexpectedly when entering unicode (cyrillic) characters in the Equipment model Solution An issue has been ...

• History of Changes does not handle correctly the value changes with long texts.

  Summary In Editor - History of Changes of the project - the columns for old value and new value are allowing the maximum of 128 characters. While the History of Changes is active and properties are changed that have a much higher size, or no limit at ...