Find out who last updated a PeopleCode

The following SQL is an example of finding out who last updated a specific Component Record Field PeopleCode but can be modified to check the audit on other types of PeopleCode events as well.

select * FROM PSPCMPROG
WHERE OBJECTID1 = 10
AND OBJECTID2 = 39
AND OBJECTID3 = 1
AND OBJECTID4 = 2
AND OBJECTVALUE1 = ' '
AND OBJECTVALUE3 = ' '
AND OBJECTVALUE4 = ' '
AND OBJECTVALUE5 = 'FieldChange'

PSPROJECTITEM OBJECTTYPE values

The translate values are stored in PS_WHEREUSEDOBJTBL table from Tools ver 8.49.

For older tools version, the list is:

0 Record
1 Index
2 Field
3 Format definition
4 Translate
5 Page
6 Menu
7 Components
8 Record PeopleCode
9 Menu PeopleCode
10 Query
11 Tree structure
12 Tree*
13 Access group*
14 Color
15 Style
16 Not used
17 Business process
18 Activity
19 Role*
20 Process definition
21 Process server
22 Process type
23 Process job
24 Process recurrence
25 Message catalog entries*
26 Dimension*
27 Cube definitions*
28 Cube instance definitions*
29 Business interlink
30 SQL definition
31 File layout definition
32 Component interfaces
33 Application Engine program
34 Application Engine section
35 Message node
36 Message channel
37 Message definition
38 Approval rule set
39 Message PeopleCode
40 Subscription PeopleCode
41 Not used
42 Component interface PeopleCode
43 Application engine PeopleCode
44 Page PeopleCode
45 Page field PeopleCode
46 Component PeopleCode
47 Component record PeopleCode
48 Component record field PeopleCode
49 Image
50 Style sheet
51 HTML
52 Not used
53 Permission list
54 Portal registry definitions
55 Portal registry structures
56 URL definitions
57 Application Packages
58 Application Package PeopleCode
59 Portal Registry User homepage
60 Problem type definition
61 Archive templates (deprecated in PeopleTools release 8.44 and
above).
62 XSLT
63 Portal Registry User Favorite
64 Mobile page
65 Relationships
66 Component Interface Property PeopleCode**
67 Optimization Models***
68 File References***
69 File Reference Type Code***
70 Archive object definitions***
71 Archive Templates (Type 2)***
72 Diagnostic Plug-Ins***

Content Reference (CREF) with link to external site

Navigate to PeopleTools >
Portal > Structure and Content. Chose the folder you would like your
link to be in or you can add a new folder just for this new link if
you'd like.

Now scroll all the way to the bottom and click "Add Content Reference".

Name: Add what ever name you would like here. Users will not see this link.
Label: This will end up being the link the users will click on.
Long Description: Long desc for your link - this will show just below your actual link.
Usage Type: Target
No Template Check Box: Make sure you CHECK this one so the portal template wont wrap around your page.

URL Information

URL Type: Non-PeopleSoft URL
Portal URL: The website you are trying to open (example: http://www.CompShack.com) :)

Now in the Content Reference Attributes of the Content Ref Administration page add the following to get your page to open in a new window:

Name: NAVNEWWIN
Label: You can leave this one blank
Attribute value: true
Translate Check Box: Make sure this is UNCHECKED

SQL Server ODBC - 32bit/64bit issue

When using SQL Server 2005 on 64 bit Edition Windows 2005 Server, use 32bit ODBC Administrator (available under C:\WINDOWS\SysWOW64\odbcad32.exe) to configure ODBC Database Sources as the PS client requires 32 bit database connectivity.

REN server 403 Error

When configuring REN server, if you get an error 403... check these
http://psadmin.wordpress.com/2008/08/04/steps-to-check-ren-server-failure/

Portal Search Index: Separate Application & Process Scheduler Server

In case you have separate servers (physical machines) for App and Process Scheduler, you would need to configure your App Servers and Process Schedulers to point to same folder where the Portal Search Index entries would be stored. In other words, your App and Process scheduler need an entry like this:

Process Scheduler
[Search Indexes]
;=========================================================================
; Search index settings
;=========================================================================
; Search indexes can be given alternate locations if there is an entry here.
; Entries look like: IndexName=fs location (ie EMPLOYEE=c:\temp)
EMPLOYEE=E:\psft\VeritySearch\HCMPRD90

Application Scheduler:
[Search Indexes]
;=========================================================================
; Text-Search index settings
;=========================================================================
; Search indexes can be given alternate locations if there is an entry here.
; Entries look like: IndexName=fs location (ie EMPLOYEE=c:\temp)
EMPLOYEE=\\servername\sharename\HCMPRD90
;

Windows XP Text Search

To configure Windows XP to search all files no matter what the file type, obtain the latest service pack for Windows XP (currently SP2) and then turn on the Index file types with unknown extensions option.

If you use this method, Windows XP searches all file types for the text that you specify.

This can affect the performance of the search functionality. To do this:

Click Start, and then click Search (or point to Search, and then click For Files or Folders).

Click Change preferences, and then click With Indexing Service (for faster local searches).

Click Change Indexing Service Settings (Advanced). Note that you do not have to turn on the Index service.

On the toolbar, click Show/Hide Console Tree.

In the left pane, right-click Indexing Service on Local Machine, and then click Properties.

On the Generation tab, click to select the Index files with unknown extensions check box, and then click OK.

Close the Indexing Service console.