When using Customization Manager the order in which to create a customization is important. What is the correct sequence of steps for creating any customization?
Which Customization Level will allow a screen to open with customizations applied but will never allow you to add new customizations or modify existing customizations at that level?
There is a non-required field on a screen that's value is typically "N/A".
The users would like Solomon to automatically set the field to "N/A" and they don even want to go to the
field except the few times that they need to enter something other than "N/A". Which of the following
properties would be used to meet these requirements?