Extra Hot

As discussed in the previous post, all actions in a component that eventually require a server trip would invoke %SubmitScriptName for submitting the page. As such, it sometimes provide a convenient point for performing javascript modifications on the page.

This is achieved by storing a reference to the original function, and redefining %SubmitScriptName to perform your custom logic — invoking the original function as needed.

The following sample scenarios may help to illustrate this technique.
read more…

In PeopleTools 8.4, %SubmitScriptName is the meta-HTML javascript function used by all PeopleSoft component pages for triggering server-side actions. %SubmitScriptName is translated at run time (i.e., when the page is rendered) to submitAction_win0. It may be related to %FormName as submitAction_%FormName, since %FormName is also translated to win0. I don’t know how PeopleTools internally translates %FormName, but as far as I can tell it is always translated to win0 inside any component.

The %SubmitScriptName function is passed 2 parameters:

1. form – the 1st parameter is the form object with the data to be submitted. On a component, this will be the win0 form in the content frame.
2. action ID * – the 2nd parameter is a distinct text string which informs the component processor what action is requested or what type of action took place.

* – I just made up this label for the purpose of discussion.

The action ID that can be passed to %SubmitScriptName can be categorized into the following type of actions:
read more…

Just a simple tip. When embedding static javascript code on a page, the obvious approach is to place the code as a constant value in the HTML Area control. For example, suppose the following code:

var something = "something";
function SomeThing() {
   /* Something */
   /* something... */
}

read more…

One very handy, yet very mysterious property in the PeopleTools page fields is the so-called Modifiable by JavaScript property. This property is available under the Use tab of user-input page fields. It is used to be labeled Modifiable from HTML on the earlier versions of PeopleTools (8.2x and earlier). This property is mysterious because its use is not documented thoroughly in PeopleBooks. Only a passing remark on the property is made to describe it under the Application Designer PeopleBook:

Modifiable by JavaScript - This is a security-related feature and should always be cleared unless you are familiar with modifying an invisible field using JavaScript in an HTML area. If the Invisible check box is cleared, Modifiable by JavaScript is cleared and unavailable for entry. If the Invisible check box is selected, this check box is cleared, by default.

read more…

In PeopleCode, when inserting or deleting a row on a scroll, it is required that you perform the action on a parent row of the rowset being inserted/deleted to. PeopleTools doesn’t allow PeopleCode (using the built-in functions/methods InsertRow and DeleteRow) to insert or delete a row on the same scroll within which it is currently running. If you attempt to do this, PeopleTools will give an error complaining about changing the current program context.

However, there are some cases where inserting within the same scroll might be desirable. For example, based on the data entered on a row of a scroll, a new matching row must be inserted within the same scroll.

Yes, you can always make concessions, like forcing the user to click a button on a higher scroll level. Yet if you are looking for a way to insert within the same scroll level, read on. This tutorial illustrates a technique for doing a row insert from PeopleCode to the same scroll where the PeopleCode program is running.
read more…

I’ve often receive requests for a solution regarding printing a PeopleSoft page by clicking a button. This tutorial presents a step-by-step instruction for the simple requirement of printing the current page.

read more…

If you’ve ever wondered what that ubiquitous Enable as Page Anchor checkbox is for, here is a quick tutorial (new window).

Here’s the resulting page behavior (new window).