Comparing Browser Client and Windows Client Definition Security
PeopleTools enables you to implement definition security in the browser client or in the Windows client. Both enable you to implement basic definition security. However, browser client definition security enables you to work with several more definition types and offers additional definition security functionality.
This table lists definition security features available in the browser client and in the Windows client:
Definition Security Feature |
Browser Client Definition Security |
Windows Client Definition Security |
---|---|---|
Create definition groups of one or more metadata definitions. |
X |
X |
Link definition groups to a predefined permission lists. |
X |
X |
Copy and delete definition groups. |
X |
X |
Populate definition groups with SQL-like selection criteria. |
X |
NA |
Create inclusion rules so that new objects added to the database that meet an inclusion rule are added to a definition group. This includes the ability to:
|
X |
NA |
Assign row-level security. |
X |
NA |
Enable or disable Secure by Default for all objects covered by Definition Security. |
X |
NA |
View unsecured definitions/definitions that don’t belong to a group. |
X |
NA |
The following tables lists the definition types with which you can work in browser client definition security and Windows client definition security:
Definition Type |
Browser Client Definition Security |
Windows Client Security |
Associated Designer Tool |
---|---|---|---|
Activities |
X |
X |
PeopleSoft Application Designer |
Analytic Model |
X |
NA |
PeopleSoft Application Designer |
Analytic Types |
X |
X |
PeopleSoft Application Designer |
App Engine Programs) |
X |
X |
PeopleSoft Application Designer |
Application Packages |
X |
X |
PeopleSoft Application Designer |
Approval Rule Sets |
X |
X |
PeopleSoft Application Designer |
Business Interlinks |
X |
X |
PeopleSoft Application Designer |
Business Processes |
X |
X |
PeopleSoft Application Designer |
Component Interfaces |
X |
X |
PeopleSoft Application Designer |
Components |
X |
X |
PeopleSoft Application Designer |
Field Formats |
X |
X |
PeopleSoft Application Designer |
Fields |
X |
X |
PeopleSoft Application Designer |
File Layouts |
X |
X |
PeopleSoft Application Designer |
File Type Codes |
X |
X |
PeopleSoft Application Designer |
HTML |
X |
X |
PeopleSoft Application Designer |
Images |
X |
X |
PeopleSoft Application Designer |
Menus |
X |
X |
PeopleSoft Application Designer |
Message Channel(s) |
X |
X |
PeopleSoft Application Designer |
Messages |
X |
X |
PeopleSoft Application Designer |
Mobile Pages Important! PeopleSoft Mobile Agent is a deprecated product. These features exist for backward compatibility only. |
X |
X |
PeopleSoft Application Designer |
Optimization Models |
X |
NA |
PeopleSoft Application Designer |
Pages |
X |
X |
PeopleSoft Application Designer |
Projects |
X |
X |
PeopleSoft Application Designer |
Queries |
X |
X |
PeopleSoft Query |
Records |
X |
X |
PeopleSoft Application Designer |
SQL |
X |
X |
PeopleSoft Application Designer |
Style Sheets |
X |
X |
PeopleSoft Application Designer |
Styles |
X |
X |
PeopleSoft Application Designer |
Translate Tables |
X |
X |
PeopleSoft Application Designer |
Tree Structures |
X |
X |
PeopleSoft Tree Manager |
Trees |
X |
X |
PeopleSoft Tree Manager |
You can restrict access to an entire definition type, such as records or pages, using the Permission Lists – PeopleTools page (
and click the PeopleTools tab). This works by controlling access to the PeopleSoft Application Designer functionality that works with a particular definition type. For example, if you don't want developers to use application engine programs, don't allow them to access PeopleSoft Application Engine.