1. Security Administration Guide
  2. Example of a UDO Security Implementation

Example of a UDO Security Implementation

Company A wants to implement UDO features in EnterpriseOne with the following criteria:

  • Allow only supervisors in the Purchasing department to create One View reports and queries for the purpose of sharing with other users in the department.

  • Allow all members of the Purchasing department to use shared UDOs created by the supervisors.

  • (Release 9.2.4) Restrict access to the base forms of the Sales Order Entry application so that all members of the Sales department can only access the personalized forms.

Based on these criteria, Company A will need to perform the following tasks:

  1. Activate the One View Reports Manager and Query Manager features in the "Revise Feature Enablement" form in Security Workbench. This displays these features globally in all applicable EnterpriseOne applications and forms.

  2. Set up two UDO action security records: one that enables members of the Purchasing supervisors role to create and share One View reports; one that enables members of the Purchasing supervisors role to create and share queries.

  3. Set up UDO view security to determine which users can use the shared One View reports and queries.

  4. (Release 9.2.4) Configure base form security for the Sales Order Entry application to determine which users are restricted from accessing the base form.