Extra Hot

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…

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).

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…

Some notes when working with secondary pages.

It is possible to bring up a secondary page using the DoModal() PeopleCode function. To make the data contained in that secondary page to be part of the component buffer, you’ll have to place a secondary page control in one of the standard pages of your component. Elementary. However, there’s something I didn’t discover until recently.

read more…

PeopleSoft pages use CSS-based stylesheets for defining the look (style) of each page element. CSS is a web standard for defining the presentation of a webpage. If you’re new to this concept and want to know more, there’s tons of tutorials and articles. PeopleSoft StyleSheets are created in Application Designer using a GUI editor which looks somewhat similar to Nvu’s CSS Editor:

read more…

One way to customize a PeopleSoft page is to execute javascript to manipulate the DOM. Some possible scenarios that may make this necessary:

• add dynamic elements to your page (set some elements as draggable maybe? or perhaps adding mouseover behavior to PeopleSoft page elements)
• removal/manipulation of elements not accessible via Application Designer (automatically added elements outside of a page definition: navigation elements, Close/Ok/Apply buttons in modal pages, etc.)

read more…