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