Chronological Event List: During the acknowledgement process the text will be not translated at the CEL.
Summary
Solution
Now, the limit text will be translated correctly.
Issue Number: 186700
Fixed on Date: 18.6.2019
Versions: 7.50 0 BUILD 58685 | 7.11 0 BUILD 58691 | 7.20 0 BUILD 58726 | 7.60 0 BUILD 59794 | 8.00 0 BUILD 59775 | 8.10 0 BUILD 59911
Related Articles
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 ...
The audit trail entry in the Chronologic Event List for changing a recipe value contains the translated text rather than the keyword.
Summary If the project is configured to use the variable identification for display in the runtime, and a value in a recipe of the Recipe Group Manager is changed, the Chronologic Event List contains the translated text of the identification instead ...
The function for the handling of alarm message list and/or chronological event list printing didn’t work as expected.
Summary The ‘print AML or CEL’ function of the group contains functions for the handling of the alarm message list (AML) and the Chronological Event List (CEL) didn’t work anymore. DescriptionThe ‘print AML or CEL’ function of the group contains ...
Visibility doesn't work for “Chronological Event List Filter” MDI Element
Description In the screen of type "Chronological Event List Filter" the link to a variable for visibility does not work correctly. In the Service Engine, when a time filter is clicked, the visibility setting no longer works as configured. This error ...
If a Batch Control Recipe's job ID contains the character '@', it will be treated as a keyword to be translated.
Summary If the job ID contains the character '@' it will be translated via the language table in the recipe list, chronologic event list and dynamic text elements. If no matching keyword can be found in the language table, the @ will be surpressed by ...