Change control is used in Application Designer to lock definitions and track history changes for each object. Change control can be activated through Application Designer using Tools > Change Control > Administrator.
After few good size projects, you can easily have hundreds if not thousands of locked objects. Attempting to unlock the objects one by one is very time consuming, so here is a way to speed up the process.
Locked objects are stored on PSCHGCTLLOCK table. Here is how PeopleSoft describes the table:
PeopleSoft stores object definitions types such as Record, Field and SQL definitions as numbers in PeopleTools meta-tables. Here is a list of what each number means with respect to its definition.
The following are stored on the PSRECDEFN table on RECTYPE field.
RECTYPE = 0
Corresponds to: SQL Table
Comments: The record will be built as an actuall database table.
Below given are the important records used in the tree manager.
PSTREEDEFN -- Tree Definition and Properties
PSTREEDEFNLEVELS -- Tree Levels
PSTREEBRANCH -- branches of the tree
PSTREENODE -- Contains the nodes of the tree
PSTREELEAF
PSTREELEVEL
Click here -> Compare Report in HTML format to see how you can generate compare reports in HTML or CSV format.
This is an attempt to list PeopleSoft meta-tables along with some kind of description for every table. The list will be broken into categories (pages, records, components, and so forth). Please feel free to add to or correct the list, this is a wiki page, so jump in!
PSPROJECTDEFN table stores information about projects created in Application Designer.
Try it out:
PSOPRDEFN - UserIds created.
PSCLASSDEFN - Permission List definition.
PSROLEDEFN - Role Definition table
PSAUTHITEM - Menus, Components and Pages attached to a permission list.
PSROLEUSER - Contains user and role mapping.
PSROLECLASS - Role Permission List mapping.
PSAUTHBUSCOMP -- Component Interfaces Permissions
PSAUTHCHNLMON - Message Channels tagged to any particular PLs
PSAUTHMP - Mobile Pages tagged to a particular Permission List
PSUSERATTR
PSUSEREMAIL
PSOPRALIAS
PSOPRALIASTYPE
PSOPRALIASFIELD
PSROLECANGRANT
PSAUTHCUBE
PSAUTHOPTN
PSAUTHPRCS
PSAUTHSIGNON
We can bypass the component search page in different ways.
1. One way is to set the key values using peoplecode and use the peoplecode function SetSearchDialogBehavior. You can write the code in the SearchInit PeopleCode. Suppose Employee Id is the only key, then the code will look like,
EMPLID = %EmployeeId;
SetSearchDialogBehavior(0);
2. There is another method of using a record with no keys as the component search record. This will also bypass the search.
Based on the requirement you can use any of the above methods.
This was kind of interesting to figure out. What I was going after is the following. I had a drop down box on a page that shows some Business Units. The values however need to be dynamic and change depending on the user viewing/accessing the page.
For example, user1 should only see 52024, 12456 but user2 should be allowed to see 52024, 12456, 45648, and 10235.
To accomplish this I've created a table to store values for each user (lets call it TABLE_1). TABLE_1 has 2 fields (oprid, and business_unit). So now, we have 2 users on the table along with their associated business units.
The 2nd step is to create the dynamic view to pull business units specific to each user. The view will only have one field and that is the business_unit field.

If you ever queried PSPROJECTITEM table (stores PeopleTools project objects) then you have definitely noticed that object types are stored as a number and not with their names. For example, if you have a project with a component then your component on this table will be stored as object type number 7.
So, what are other object types stored as (Pages, Record PeopleCode, Menus....)? Well, the list below is your answer. Please don't hesitate to post a comment and "correct" me if I messed up somewhere while mapping numbers to names!
| Title | Under | Posted on |
|---|---|---|
| Inserting records | PeopleSoft Technical | 07/28/2010 - 11:03am |
| WEBLIB_PT_NAV.ISCRIPT1.FieldFormula.IScript_PT_NAV_PAGELET error... | PeopleSoft Technical | 07/27/2010 - 2:02pm |
| Basic language | PeopleSoft Technical | 07/27/2010 - 7:12am |
| Rowlevel security from app designer | PeopleSoft Technical | 07/27/2010 - 5:15am |
Recent comments
55 min 7 sec ago
58 min 19 sec ago
13 hours 15 min ago
13 hours 18 min ago
22 hours 39 min ago
1 day 1 hour ago
1 day 1 hour ago
1 day 1 hour ago
1 day 9 hours ago
1 day 10 hours ago