Last week's post mentioned setting up Personalizations to make fields required. We had someone reach out to "Ask Denovo" about Personalization defaults for users. The concern is that a user may see the "Personal Form" field at the top of the application and change the default form to "No Personalization", thereby changing the screen from the intended default form the employee needs to be using. Oracle has the answer!

In Tools Release 9.2.4, Oracle provided the ability to setup *Base Form Security for Personalizations. This secures users from being able to select "No Personalization", ensuring the users are seeing only the Personalizations shared with them for their use. 

This is a link to the Oracle document on how to set this up.

Want to see your question answered in the series, or just want to subscribe for alerts on future issues? Simply fill out the form below!