PeopleTools Gottchas

Iouri Chadour — Sun, 25 Sep 2011 19:18:00 +0000

As I was working on the Peoplesoft upgrade project I have noticed that some of the developers were still using App. Designer Compare reports as a sole means to comparing the code and components during customization reapplication process. It seems the new ways of doing compares are not being used as extensively as I hoped.

I figured I would write a quick post to remind my developers and others out there some of the features that have been implemented since version 8.49. For those experts readers who have been using these and other technics for awhile I would appreciate if you share your own technics.

Running Compares

So without further due, below you can see a sample PeopleSoft’s visual merge compare for Project Peoplecode. In order to save you from long and boring explanations – I will leave it to PeopleBooks – Using Merge Interface. However I would like to add just a few comments – sometimes I find myself pasting compare code into good old Notepad++ and running a compare in there. I guess I do like the power of the full fledged editor and syntax highlighting does not hurt as well.

As much fun as App Designer reports are I always like to look at the reports in the HTML view – better , faster and cleaner experience. And all it take is specifying Generate HTML report in the Compare Options in App Designer:

Secondary Pages

If you are creating a complex page that contains some sort of look-up pages – always a good idea to split the interface and not create page that would overwhelm the user. In earlier versions of tools going to secondary pages required user to transfer to a separate page, however since Tools 8.50 – secondary and modal pages can open in a modal JavaScript Popup that still allows you to stay on the same page:

In order to enable this behavior for existing and new pages you just need to enable one little checkbox and voila:

Change Control

When working in a team and making multiple changes to the environment you don’t want to be stepping on each others toes. Although still quite limited and inferior to Tools like Quest Stat – PeopleTools built in change control does provide you the ability to lock objects while you change them and leave comments as to what was done (always a good idea). This also helps with documentation – once you are done with the changes you can run a quick SQL and get a report of all the changes that were done for more please go to here.

I hope you enjoy this and let me know if you have any suggestions.

PeopleSoft Debugging Techniques – Part I (Batch)

Iouri Chadour — Sat, 23 May 2009 21:36:34 +0000

I would like to briefly describe some of the PeopleSoft debugging techniques that I have used and found invaluable during development batch and online programs.

SQR Debugging

Flag

Description

-S

Choose Append Option on Parameter List of Process Definition. All of your SQL statements – simple and clear + execution counts

–debug(flag)

Choose Append Option on Parameter List of Process Definition. Put the following statements in your code

#debug(flag) show
#debug(flag) display

this will allow you to display definitions in your log. What is most useful this allows you to specify different levels of tracing using the flag – which can be letters A-Z. Specifying –debug(A-Z) on process definition it allows you to selectively display your debug statements.

COBOL Debugging

Flag	Description
`%%PRCSNAME%% %%DBTYPE%%/%%DBNAME%%/%%OPRID%%/ %%OPRPSWD%%/%%RUNCNTLID%%/%%INSTANCE%%//%%DBFLAG%%`	Choose Override Option on Parameter List of Process Definition. Copy and paste Flags and run your process normally. You will see the trace file in the Process Monitor

App Engine Debugging

Flag

Description

-TRACE 131

Choose Append Option on Parameter List of Process Definition.

Required to start the app engine trace. Does not display much more than message log

-TRACE 131

-TOOLSTRACEPC 2048

Choose Append Option on Parameter List of Process Definition.

Adding TOOLSTRACEPC with a number causes detailed PeopleCode code trace – be careful those can get very large and significantly impact performance.

-TRACE 131

-TOOLSTRACESQL 31

Choose Append Option on Parameter List of Process Definition.

Adding

TOOLSTRACESQL

with a number causes detailed SQL trace. This option should always be used when tracing – app engine are all about SQL.

App engine can also be debugged on the client. In order to do this you need to configure trace setting in the configuration manager:

Open App Engine program in the Application Designer, press the Run Program icon and enter the Run Control ID and Process Instance Number (You should have an existing process instance and run control id defined online). Click ‘OK’ to run the App Engine process in two-tier mode.

If you would like to read about debugging in more details here is an excellent overview presentation by Kai Markowitz from CSU:

http://www.scribd.com/doc/15756180/Tracing-Debugging-in-People-Tools-84x-CMS411