Using the Change Function Authorization function inside of the Change User Function can lead to unauthorized level changes

• Related Articles

• Under specific circumstances the runtime warns twice the user that it does not own the required authorization level to execute a function.

  Summary If a user that does not own the required authorization level clicks in the runtime a combined element linked to a variable and a function, it is shown twice the warning message box "You are not entitled to execute this function" . ...

• How can I reset the password of a zenon Service Engine/Runtime User?

  Resetting a password in the zenon Engineering Studio can be essential for maintaining security and managing user access to your project. zenon offers two different methods to reset a password: one through the zenon Engineering Studio and the other ...

• The history of changes may not log a screen element position change in the editor.

  Summary Despite the detailing level is set to "object", the history of changes may not log the change of a screen element position when using the "position" properties in the editor. DescriptionDespite the detailing level is set to "object", the ...

• [User Administration] Current authorization group 1-4 variables bits are not correctly set in Service Engine v10 32-bit when a user with authorization levels 31, 63, 95 and/or 127 logs in.

  Problem: [User Administration] Current authorization group 1-4 variables bits are not correctly set in Service Engine v10 32-bit when a user with authorization levels 31, 63, 95 and/or 127 logs in. As a result, the respective variable shows ...

• Under specific circumstances the zenon runtime buttons do not adjust their look according to the current user logged in authorization level.

  Summary It may occur that when a user logs in the zenon runtime its authorization level is not acquired correctly by the screen buttons not looking these accordingly. The buttons appearance is only adjusted if the zenon runtime is reloaded online. ...