Understanding UDO View Security

Set up UDO view security to authorize access to shared UDOs. Shared UDOs are secure by default; other users cannot access them unless authorized to do so through UDO view security.

How does a udo become a "shared udo"?: To share a UDO, the creator of the UDO has to click the "Request to Publish" button, which sends it through an approval process. After the UDO is approved by an approver in the User Defined Object Management (P98220U) application, it is considered a "shared UDO."See Also: JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide for information on how to approve UDOs.

You can set up UDO view security for:

• Individual shared UDOs.

• All shared UDOs of a particular UDO type. Instead of specifying the name of a particular shared UDO, you can enter *ALL for the "User Defined Object Name" to gives users access to all shared UDOs of a particular UDO type. For example, for grid formats, if you enter *ALL instead of the name of a particular shared grid format, users will be able to access all grid formats that are shared.

  Important: You cannot use *ALL for Classic EnterpriseOne Pages and Composed Pages. This restriction prevents users from being able to access all Classic and Composed Pages from the EnterpriseOne Welcome screen. (Release 9.2.0.2)
  Note: You must first request to share the Classic EnterpriseOne Page and receive View permissions from your system administrator before your page is available in run time.

• (Release 9.2.4) *BASE value for the personal forms UDO type.

  System administrators can use the *BASE value to restrict access to an EnterpriseOne form so that users can access only the personalized forms available to them and not the base form.

  Important: When setting up base form security using the *BASE value, system administrators cannot use a combination of *ALL in the Application Name column and *BASE in the User Defined Object Name column. This restriction prevents system administrators from restricting access to all applications.

You set up UDO view security records for a user, role, or *PUBLIC (all users). In addition, you can define a particular application, form, application version, product code, or reporting code to which to apply the security. Or you can use *ALL (all objects) to apply view security to all applications, forms, application version to which the user has access.

EnterpriseOne provides two versions of the "Work With User Defined Object View Security" form:

• W00950UOG. Access this form through Security Workbench. Use this form to set up view security for individual UDOs or all shared UDOs of a particular UDO type. Setting up view security for all shared UDOs of a particular UDO type can only be performed using this form. Starting with EnterpriseOne Tools Release 9.2.3, you can access W00950UOG from the User Defined Object Management (P98220U) application.

• W00950UOK. Access this form outside of Security Workbench through the User Defined Object Management (P98220U)application, the application for reviewing, approving, or rejecting UDOs submitted for sharing. This enables you to allow the same user approving UDOs to set up view security for the objects. Oracle recommends using this application to set up UDO view security for individual shared UDOs.

Updates to UDO view security in either form are reflected in both forms.