Cel print with Switch language in Sub Project from Integration Project doesn’t work.
Summary
Printing the CEL from a subproject after
a language switch does not work correctly. In another language translated Keywords
are not included in the Print. This behavior has been modified.
Description
In a project, the CEL is configured for integration
project and subproject. Both projects have a language file. Switching the
language works correctly for the projects view in the Service Engine. But translating in the subproject for
printing the CEL does not work correctly.
The translation of the keywords for the printout is
only done correctly if all keywords of the subproject are also included in the
integration project. If a keyword is included only in the subproject, it will
not be translated for printing.
This behavior has been modified. When printing the CEL,
all keywords from all projects are translated correctly.
To benefit from this fix:
- Update your zenon Software Platform to the latest build of zenon 10 or
higher.
Item ID: 265030
Version: 11.00 Build: 157700
Version: 10.00 Build: 153228
Related Articles
Checklist: Printer does not print in the format as expected
Time estimate: 15 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. No .frm file is used to specify ...
FAQ: Can I translate or change the system texts in the zenon Service Engine?
Yes, it is possible. All system texts in the Service Engine are keywords for the language change functionality, like user defined texts in projects that start with a "@" character. Using the function "Language switch" and the keywords with ...
Variable identification in the Variable Diagnosis screen cannot be translated in Subproject from Integration project
Summary In the Service Engine, not all variables are translated as configured in the Variable Diagnosis screen. This has been fixed. Description In the Service Engine, with Multi Project Administration, the identification for variables from the ...
Setpoint input for Keyboard screen doesn’t work in Batch Control
Description In Batch Control, the setpoint input in a screen of type keyboard does not work as expected. When entering a value via a button that is linked to the function "Setpoint input for keyboard screen", the input is not executed correctly. The ...
Control Recipe import with unit placeholder doesn’t work
Summary In Batch Control, the import of a control recipe that was previously validated without errors fails. This error has been fixed. Description In Batch Control, a control recipe with a unit placeholder is validated and exported without errors. ...