Today's post continues our 4-part series on JDE Notifications with a focus on Security. There are two elements of security for Notifications - the system security to the UDOs via the Security Workbench (P00950), and the individual UDO objects themselves in the UDO Workbench (P98220U).
The Notification bell icon will show next to users if they have UDO security to Notifications as a whole. If users do not see this bell icon, the UDO security for Notifications needs to be updated. There is special security for UDOs in the Security Workbench found under the Form exit in P00950.
This document from Oracle helps to further explain things. It discusses:
1. Which UDO features are available (Feature security)
2. Who can create UDO (Action security)
3. Request to publish UDO for sharing with others (Action security)
4. Modify UDO created by other users (Action security)
5. View or work with UDO (View security)
The UDO Workbench has object-level security for viewing the Notification itself. For the pre-configured Notifications, I have found that they come with *PUBLIC when they're imported via Oracle's Update Center. Due to the sheer volume and your company's modular usage, you should go through the Notifications in the UDO Workbench and update the security to be specific to the roles/users where the Notification is most meaningful.
Stay tuned for Part 3 in this series - how to subscribe and maintain Notifications.
We at Denovo want you to get the most out of your Oracle investment, and we hope this series will help with that.
Want to see your question answered in the series, or want to subscribe for alerts on future issues? Simply fill out the form below!