When switching the language, already existing CEL entries that have been produced by Command Processing are not translated.

• Related Articles

• The information element Response Variable (identification) from Command processing cannot be translated

  Summary Some elements of the response variable from the Command Processing are not translated. This has been fixed. Description Some elements such as the variable identification in the Command Processing screen are not translated correctly in the ...

• WVS supports basic Command Processing

  Summary WVS supports Command Processing. Description The screen of type Command Processing can be called up in the Web Visualization Service. The following are supported: Write set value via the following screen elements: Dynamic text Numeric value ...

• CEL: At acknowledgement, the alarm text not translated in CEL

  Description When acknowledging an alarm, the translation is not correct when using language switching. "Acknowledged" is translated correctly. However, the "Limit value text" will not be translated. This error occurred in versions 7.11 to 8.20. The ...

• Command Processing is using randomized text as 'switching direction' greater than 5

  Summary Command Processing for action 'set value, DIR: xx': when no reaction matrix is linked to the response variable, then the module has predefined texts about 'switching direction' for values until 5. If after the command was executed, the ...

• Keywords are not translated via the language table.

  Summary The string Creating list... or Liste wird erzeugt... will be shown when the CEL/AML is being populated isn't translated via the language table. Description The string Creating list... or Liste wird erzeugt... will be shown when the ...