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…

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…

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…

The PeopleCode SendMail() function is a quick and easy way to send emails from your PeopleSoft application. Unlike workflow routing and Notification classes, SendMail() provides the most functionality when it comes to sending emails. Over the newer releases, PeopleSoft has further added new capabilities to this function like overriding the content-type and sender details. However, the feature that I find the least used is the inclusion of file attachments. This is because in PIA, PeopleCode runs either on the Application server or the Batch server. The files that can be attached should be either 1) located on the server, or 2) accessed by the server through a network share. For this reason, most applications that use file attachments are Application Engine programs (running on the Batch server) that attach log files from within the server.

If you’ve used web-based email services like Yahoo, then you’ll find it a common feature to allow attachments to be uploaded by a user from his workstation and send those attachments with the email message. Is this possible in PeopleSoft’s internet architecture? The answer is yes, this article will show you how.

read more…

If you’re a PeopleSoft programmer, the Error() function is probably one of the first function you learned in PeopleCode. Raising an error — via the Error or MessageBox functions — is an indispensable operation, and serves multiple purposes throughout the component processor flow. Aside from displaying a message to the user, issuing an error has an accompanying effect which depends on which PeopleCode event it occurs. In FieldEdit, it highlights the affected field and stops further processing; in SaveEdit, it is used to abort save processing (SavePreChange–Workflow–SavePostChange); in RowDelete, it is used to cancel the user delete action.

read more…

When working with HTML areas or an IScript page, it is still often very convenient to store data into arrays. When converting the data into the necessary HTML, the Join() method of the Array class still provides a convenient way to formulate your HTML without doing a loop. The following examples should illustrate.

To generate a series of paragraphs from an array &arPara:

   &html = &arPara.Join("</p><p>", "<p>", "</p>");

To create an unordered (bullet) list from &arList:

   &html = &arList.Join("</li><li>", "<ul><li>", "</li></ul>");

Related Posts

• Smarter coding techniques with arrays