The "time of last change" field of a Recipegroup Manager recipe is not correctly updated in the runtime under specific circumstances
Summary
When using the Recipegroup Manager screen in the runtime with the new recipe value table, saving the recipe after making changes, does not correctly update the "time of last change" field.
In the following situations, the "time of last change" may not be correctly updated:
- - change via keyboards
- - change on a runtime client
- - change of action, string value, numeric value, source variable
- - changes via screen specific functions: increment values, decrement values, math formula
When using the legacy recipe value table, the "time of last change" is correctly updated, with the exception of the screen specific functions, with which the field is also not correctly updated.
Description
When using the Recipegroup Manager screen in the runtime with the new recipe value table, saving the recipe after making changes, does not correctly update the "time of last change" field.
In the following situations, the "time of last change" may not be correctly updated:
- - change via keyboards
- - change on a runtime client
- - change of action, string value, numeric value, source variable
- - changes via screen specific functions: increment values, decrement values, math formula
When using the legacy recipe value table, the "time of last change" is correctly updated, with the exception of the screen specific functions, with which the field is also not correctly updated.
Solution
Issues have been addressed in the Runtime where the "time of last change" field was not correctly updated after making changes and saving the recipe.
Issue Number: 36457
Fixed on Date: 23.5.2016
Versions: 7.20 0 BUILD 28665
Related Articles
FAQ: When I change something in the Recipegroup Manager via the programming interface in Service Engine, these changes are not updated in the screen. Why is that?
To understand this, you have to know that each time you access the RGM (Recipegroup Manager), you are working with a copy of the RGM data. So every screen that is opened in the Service Engine, has it's own copy of the RGM data. Also each instance ...
FAQ: When I activate the option "write synchronously" for the Recipegroup manager recipe, and I write the recipe, the recipe does not seem to be written properly and also the Service Engine does not close properly. Why is that?
When the option "write synchronously" is active at a recipe, when writing a recipe (sending values to the PLC) for each recipe variable a writing confirmation is requested to the driver. On a successfull write, the driver sends a writing confirmation ...
The sorting of the recipe value table in the Recipegroup Manager screen in the runtime changes unexpectedly under specific circumstances
Summary When selecting a recipe variable in the recipe value table in the Recipegroup Manager screen in the runtime and executing e.g. the screen specific function "read selected value", then change the sorting on a different column and executing the ...
The defined keyboard screen for editing Recipegroup Manager recipe variable values, may not open in the runtime under specific circumstances.
Summary When a keyboard screen is linked to a recipe variable at the Recipegroup Manager in the editor, this keyboard screen may not open in the runtime when the new recipe value list is used and a multi-hierarchical project structure is used. With ...
After deleting all Recipegroups in the Recipegroup Manager screen in the runtime, the last selected recipe is still partially displayed in the recipe value table and the recipe selection combobox
Summary When all Recipegroups are deleted in the runtime in the Recipegroup Manager screen, the recipename may still be displayed in the combobox for selecting the recipes and parts of the last selected selected recipe are still displayed in the ...