1. Security Administration Guide
  2. Setting Up Base Form Security (Release 9.2.4)

Setting Up Base Form Security (Release 9.2.4)

You can use UDO view security settings to restrict access to the base forms. A base form is an EnterpriseOne form that is designed by using the Form Design Aid (FDA) and that has not been personalized. Personalized forms are the forms that have been personalized by using the Personal Form UDO. Configuring base form security ensures that users will only be able to access the personalized forms and not the base form.

JD Edwards EnterpriseOne provides a special UDO value, *BASE, that system administrators can use to configure base form security. When setting up base form security for an EnterpriseOne application, the system administrator must enter the *BASE value manually in the User Defined Object Name field on the User Defined Object View Security form.

If base form security is configured, the system determines the form that will be displayed when a user accesses the application based on the following order of precedence:

  1. If a default personal form exists for the user, the system displays the default personal form.

  2. If a default personal form does not exist for the user, the system displays the shared default form.

  3. If a shared default form does not exist for the user, the system displays the last active form.

  4. If the last active form does not exist for the user, the system displays the first personal form in the Personalization drop-down menu.

If base form security is configured and a personal form does not exist for the user, the system displays the base form but hides the Personal Form icon. This means that the user cannot personalize the form by using the Personal Form UDO.

To configure base form security:

  1. On Work With User/Role Security in the Security Workbench (P00950), from the Form menu, select User Defined Object and then select View.

    Alternatively, on Work with User Defined Objects (P98220U), select the Form menu, and then select View Security.

  2. On Work With User Defined Object View Security (W00950UOG), click Add.

  3. On User Defined Object View Security, click the search button in the Object Type field and select PERSFORM (personal forms) as the UDO type. For a complete list of user defined objects, see the JD Edwards EnterpriseOne Tools Using and Approving User Defined Objects Guide.

  4. In the first row in the grid, ensure that the View column displays a red square and then complete the following columns:

    • User/Role. Enter a user, role, or enter *PUBLIC for all users.

    • Application Name. Enter the application ID of the application which you want to secure.

      Note: If you enter *ALL in this field and *BASE in the User Defined Object Name field, the system displays an error message.

    • Form Name. Enter the form ID of the form for which you want to configure base form security. Enter *ALL for all forms.

    • Version. Enter the version ID of the If you want to limit the base form security to a particular application version, enter the version ID. Or you can enter *ALL for all versions.

    • User Defined Object Name. Enter *BASE.

      Note: *BASE is a special value and is not available as a UDC value. Therefore, you must manually enter this value in the User Defined Object Name field.

    • Product Code and Reporting Code. If you entered a specific application, form, or version, these fields automatically change to *ALL (all product codes or all reporting codes) and you cannot modify them.

    • Web Object Category. Enter PERSFORM.

  5. Click OK.