Peter Slager posted a new article about “What’s new in PeopleTools 8.50”.  From the screenshots he posted, it looks very exciting.  I am anxious to get in and try it out!

I read several posts about it coming out in late 2009.  That is a long time to wait!

Resources

• “What’s New in PeopleTools 8.50“
• PeopleSoft Technology Blog
• “New PeopleTools Blog”
• PeopleSoft Enterprise Reporting Road Map
• My Oracle OpenWorld 2008
• PeopleTools Product Roadmap PPT

I just came across this new certification (at least to my knowledge new).  Somewhere I found a date of August 31st, but don’t quote me on that.

Any way, Oracle has a certification program for PeopleTools Developers.  I hope to work toward that path, and you may see some basic posts as I review the topics for the exam.  What better way to make sure you understand something than to explain it to someone else?

One question we have had is whether a “hands-on” course is required.  If you are self-taught or experience-taught in PeopleTools, do you have to take one of Oracle’s classes anyway as a requirement.  That has yet to be answered for me.

Check it out on Oracle’s website:

• PeopleTools Certified Expert path
• PeopleTools Application Developer I Test
• PeopleTools Application Developer II Test

Step 1: WEBLIB_ record

You must put your PeopleCode on a record that begins with “WEBLIB_”. You can either create one or add onto an existing record that meets that naming convention.

Step 2: Create the PeopleCode Function

The function name should start with “IScript_”.

%Response

You can use the %Response to create the output HTML, XML, or other format. The Write function is the main function that you will use:

%Response.Write("<b>Hello, World</b>");

%Request

You can use the %Request object to read parameters that were sent to the script. For example, if the URL had “?EMPLID=00001” at the end of it, you could use the following PeopleCode to read it:

&emplid = %Request.GetParameter("EMPLID");

Step 3: Security

You must grant security to your IScript before you can view it. This is done on the Permission List just like the security for a regular page.

Nagivation to the Permission Online:

PeopleTools > Security > Permissions & Roles > Permission Lists

Go to the WebLibraries page/tab.

On that page, you will need to enter the record name of the script. Then, click on the Edit link to choose the specific IScript that you wish to grant access.

Step 4: Determine the URL

The URL for a component looks something like this:

… /c/MenuName.ComponentName.Market

The URL for an IScript looks something like this:

… /s/RecordName.FieldName.Event.FunctionName

See PeopleBooks for more information.

Step 5: Register Your IScript

If an end-user should access the IScript, you need to put a content reference in the menu for easy access. You can do so, by registering your script through the registration wizard. If you just intend to access the script via code, you don’t need to do this step.

When you open a record that begins with “WEBLIB_”, you will notice a new button on the toolbar for the registration wizard. Just click that button and follow the steps.

See PeopleBooks for more information.

Resources

• PeopleBooks: Internet Script Classes
• PeopleBooks: Creating the Location
• PeopleBooks: Registering
• PeopleBooks: When to Use
• PeopleBooks: Details on URL
• PeopleBooks: Security

These resources may not be as relevant:

• PeopleBooks: Writing the Function for Business Interlinks
• PeopleBooks: GetContentBody Method