jgagnon
Active Member
In our organization we have set up roles with security for E1 users. For some roles, we ran into an issue where the best solution seemed to be to create a Personal Form UDO that would be assigned to the role(s).
In this scenario, users in these roles need to be able to run a specific application that is currently accessible via a row exit in an application. This in itself is not a problem. The problem is that there are other items in the row exit menu for that application that users in these roles have no need to use. Furthermore, if these other functions were to be used, even accidentally, it could cause transactional changes to production data that could be difficult to correct.
Since Personal Forms UDOs allow for modification of the form appearance and the ability to hide items in the form and row exit menus, this seems to be a good solution. So, I built a Personal Form UDO where the only thing I changed was removing row exit menu items users should not be allowed to access. All well and good.
The problem I'm running into is that I can't seem to prevent a user with the role from selecting the Personal Form dropdown on the application header and selecting the "(No Personalization)" form, which brings back all of the row exit menu items.
Is there a security setting somewhere that allows me to control this?
In this scenario, users in these roles need to be able to run a specific application that is currently accessible via a row exit in an application. This in itself is not a problem. The problem is that there are other items in the row exit menu for that application that users in these roles have no need to use. Furthermore, if these other functions were to be used, even accidentally, it could cause transactional changes to production data that could be difficult to correct.
Since Personal Forms UDOs allow for modification of the form appearance and the ability to hide items in the form and row exit menus, this seems to be a good solution. So, I built a Personal Form UDO where the only thing I changed was removing row exit menu items users should not be allowed to access. All well and good.
The problem I'm running into is that I can't seem to prevent a user with the role from selecting the Personal Form dropdown on the application header and selecting the "(No Personalization)" form, which brings back all of the row exit menu items.
Is there a security setting somewhere that allows me to control this?