Overloading %SubmitScriptName

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.
Continue reading

A Look at %SubmitScriptName

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:
Continue reading