The user that is stored as the user that created or last modified the Recipegroup Manager is not correct when the recipe is created or changed on a runtime client
Summary
The user that is stored as the user that created or lastmodified a Recipegroup Manager is not the correct user from the runtime client where the recipe was modified but the user that was logged in on the runtime server at the time the recipe was created / modified.
The corresponding entry in the Chronologic Event List for the creation / modification of the recipe shows the correct user that is logged in on the runtime client.
Description
The user that is stored as the user that created or lastmodified a Recipegroup Manager is not the correct user from the runtime client where the recipe was modified but the user that was logged in on the runtime server at the time the recipe was created / modified.
The corresponding entry in the Chronologic Event List for the creation / modification of the recipe shows the correct user that is logged in on the runtime client.
Solution
An issue has been addressed in the Runtime where the information which user created / last modified a recipe was taken from the runtime server rather than the runtime client where the recipe was actually created / modified. Now the recipe also contains the correct user information.
Issue Number: 35342
Fixed on Date: 5.11.2015
Versions: 7.20 0 BUILD 24121
Related Articles
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 ...
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 ...
Changed column settings in the dialog for editing a Recipegroup Manager recipe in the editor are not saved in multi-user projects
Summary When changing the column settings in the dialog for editing a Recipegroup Manager recipe in the zenon editor, the changed column settings are not permanently saved in multi-user projects under specific circumstances DescriptionWhen changing ...
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 ...
Reading a Recipegroup Manager recipe with action type "user status" does not read the upper 32 status bits of a variable
Summary When reading a Recipegroup Manager recipe with the action type "user status" in the Runtime, the upper 32 status bits of a variable are not stored in the recipe. Description When reading a Recipegroup Manager recipe with the action type "user ...