Category: PeopleTools

jQuery and PeopleSoft

I came across this link talking about storing Javascript libraries in PeopleTools to use with PeopleSoft applications.  The interesting part is that I have been able to get it working by storing jQuery in an HTML definition.  Application Designer did give me an error about it being too big, but it went ahead and saved it.  Everything seems to work fine so far, and I haven’t had a need to look for another fix.

The solution to save the library in the message catalog sounds  great, but the big problem with Message Catalogs is that they can’t be exported to a file.

Resources

Serve thoseJavaScript Libraries Quickly… and Safely

PSPNLFIELD.FIELDTYPE

Update: These are the list of fields types in the PSPNLFIELD table.

This is a list of the Panel Field types:

  • 0:  Text
  • 1:  Frame
  • 2:  Group Box
  • 3:  Static Image
  • 4:  Edit Box
  • 5:  Drop Down List
  • 6:  Long Edit Box
  • 7:  Check Box
  • 8:  Radio Button
  • 9:  Image
  • 10:  Scroll Bar
  • 11:  Subpage
  • 12:  Push Btn/Link — PeopleCode (Thanks Robert)
  • 13:  Push Btn/Link — Scroll Action
  • 14:  Push Btn/Link — Toolbar Action
  • 15:  Push Btn/Link — External Link
  • 16:  Push Btn/Link — Internal Link
  • 17:  Push Btn/Link — Process
  • 18:  SecPage
  • 19:  Grid
  • 20:  Tree
  • 21:  Push Btn/Link — Secondary Page
  • 22:  ?? not in an HR database
  • 23:  Horizntl Rule
  • 24:  Tab Separator
  • 25:  HTML Area
  • 26:  Push Btn/Link — Prompt Action
  • 27:  Scroll Area
  • 28:  ?? not in an HR database
  • 29:  Push Btn/Link — Page Anchor
  • 30:  Chart
  • 31:  Push Btn/Link — IM Action
  • 32:  Analytic Grid

PeopleTools 8.50 Preview

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

News: New Certification

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:

Updated: PeopleTools Tables

Here is just a quick post to let you know that I have added a few more tables to the PeopleTools Tables page:

  • PSCONTENT
  • PSCONTDEFN

These tables are related to HTML definitions.  I was using them to check to make sure that I have all of the HTML definitions that I have created in my project.

Here is a link to the page:

http://psst0101.wordpress.com/peopletools-tables/

HowTo: Creating IScripts

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

These resources may not be as relevant:

Response: Array Class Generic Sort

Here is my attempt at providing details in response to an article by ChiliJoe called PeopleCode Array Class’ Generic Sort.

Basically, ChiliJoe is referring to a vague example in PeopleBooks that says, “For example, suppose you want to provide a more generic sort, with comparison function at the end of it.” This is in the section: “When Would You Use Application Classes?“.

The key to this example is that you have to write the sort by extending the array class. Here is an attempt at writing an example:

Read More