Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.
The following are some questions related to securing the Processing Options on versions from being changed by users:
- When the "Prompt for Values" security is set for an application in P00950-Security Workbench application, the "Change" checkbox is automatically checked as well. Users cannot view and modify processing option values. The problem is the user is not even allowed to change the processing option values for their own versions in Batch Version application.
How can I secure Prompt for Values from the task menu, but still allow the versions' owners to be able to modify processing options in the Batch Version application?
- We have set the version security level to '1' (Medium Security) so that only the "Last Modified By" user can change processing option values or delete the version. The problem is when users access processing options from the menu using the Prompt for Values option, the users can still modify processing option values. The "Last Modified By" user is then updated. How can I prevent that?
- On the web client, after applying the StrictVersionSecurity=1 setting in jas.ini [SECURITY] stanza, the versions' processing option are secured as desired. However, on a fat Windows client the menu task disappears if the version security is '1' and StrictVersionSecurity=1 in the jde.ini when the task is set to blind execution. Why is this different on the fat Windows client?
Is there a way to mass update EnterpriseOne batch versions, or to setup security such that users are are not allowed to make changes or delete some batch versions while at the same time they are allowed to run and to create their own versions of the same UBE?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms