Object Level Security Types
At specific object levels, you can set these levels of security, alone or in any combination, for users and groups of users assigned to a particular role:
- Application security
Secures users from running or installing, or both, a particular application, an application version, or a form within an application or application version. You cannot define Application security at the subform level. Application security also applies to EnterpriseOne mobile applications.
- Action security
Secures users from performing a particular action, such as adding, deleting, revising, inquiring, or copying a record. You define Action security at the application, version, and form level. You cannot define Action security at the subform level.
- Row security
Secures users from accessing a particular range or list of records in any table. For example, if you secure a user from accessing data about business units 1 through 10, the user cannot view the records that pertain to those business units.
- Column security
Secures users from viewing a particular field or changing a value for a particular field in an application or application version. This item can be a database or non-database field that is defined in the data dictionary, such as the work/calculated fields. For example, if you secure a user from viewing the Salary field on the Employee Master application, the Salary field does not appear on the form when the user accesses that application.
- Processing option security
Secures users from viewing or changing the values of processing options, or from prompting for versions and prompting for values for specific applications or application versions. For example, if you secure a user from changing the processing options for Address Book Revisions, the user could still view the processing options (if you did not secure the user from prompting for values), but would not be able to change any of the values.
If you secure a user from prompting for versions, the user would not be able to see the versions for a specific application, so the user would not be able to select a different version of an application from the version that the administrator assigned.
- Tab security
Secures users from viewing or changing fields in a tab or tabs on a given form. You define Tab security at the application, version, and form level. You cannot define Tab security at the subform level.
- Hyper exit security
Secures users from menu bar exits on JD Edwards EnterpriseOne forms. These exits call applications and allow users to manipulate data. Exit security also restricts use of the same menu options.
- Exclusive application security
Overrides row security that is set for an application. When you set exclusive application security for a user, the system overrides row security for every table that is accessed by the application that is specified. All other security still applies.
- External calls security
Secures users from accessing standalone executables that exist external to JD Edwards EnterpriseOne. These external executables, which might include design tools, system monitors, and debugging tools, are specific to JD Edwards EnterpriseOne.
- Solution Explorer security
Secures users from performing and viewing certain features within Solution Explorer, such as Menu Filtering and Fast Path.
- Miscellaneous security
Provides additional security options to prevent users from running reports that update EnterpriseOne database tables. You can also use Miscellaneous security to configure different levels of access to workflows.
- Data Browser security
Controls access to the Data Browser application.
- Push button, image, and link security
Controls whether users can user or view push button, link, and image controls.
- Media object security
Controls whether users can add, change, delete, or view media objects within interactive applications, forms, or application versions.
- Text Block and Chart Control security
Controls whether users can use or only view text block and chart controls.
- Application query security
Prevents users from performing searches if they have not entered search criteria in the form filter fields or QBE fields.
- Published business service security
Controls access to published business services. For published business services, EnterpriseOne uses a "secure by default" security model which means that users cannot access a published business service unless a security record exists that authorizes access. For all other objects in JD Edwards EnterpriseOne, access is granted unless otherwise secured or restricted.
- User defined object security
EnterpriseOne enables you to set up security for objects created by end users, otherwise referred to as user defined objects (UDO). For instructions on how to set up UDO security, see Managing Security for User Defined Objects.