Interwindow Communication Considerations and Limitations

Page and Pagelet Types

This table describes the types of pages and pagelets that interwindow communication supports and the type of refresh that is available to each page and pagelet type:

Page or Pagelet Type Description Refresh Support

Transaction pages

The standard PeopleSoft page that appears in the target content area.

  • Partial refresh.

  • Full refresh.

Component-based pagelets

A pagelet built by using Application Designer.

  • Partial refresh

  • Full refresh.

iScript or Pagelet Wizard pagelets

The PeopleCode-based pagelets built by using Pagelet Wizard or by registering an iScript.

Full refresh.

Considerations and Limitations

Note the following considerations when implementing interwindow communication:

  • The domain for interwindow communication is the entire, visible HTML page.

    This domain includes all pagelets and active transaction pages visibly displayed, but excludes any tabbed pages of the component definition that are currently not displayed (not active). Therefore, the visible HTML page can encompass multiple component and page definitions.

  • A subscribing page or pagelet must be completely loaded or it will fail to consume a published message.

  • A field that will participate in interwindow communication must have a unique HTML field ID within this domain.

    Use developer tools in the browser to determine HTML field IDs. See Identifying HTML Field IDs.

  • Component definitions for objects participating in interwindow communication must remain in deferred processing mode.

    Page definitions and field definitions can be set to either deferred or interactive mode as needed.

  • A publishing field or a subscribing field can include FieldChange PeopleCode.

  • However, a publishing field should not include FieldEdit PeopleCode, which typically includes errors and warnings.

    An interwindow communication event will not fire on a publishing field that includes FieldEdit PeopleCode.

  • If a non-visible field is required to either publish or subscribe to an interwindow communication event, change the style of the page field properties to PTTRANSPARENT (on the Record tab in Application Designer).

    Do not set the field to invisible (on the Use tab); fields set to invisible in this manner do not get generated as part of the HTML.

  • In a modal secondary window, you cannot configure a publication event on the close icon (the "X" with id="ptModClose_0") in the upper right corner of the window.

    Instead, you must configure the publication event on a button such as a Save, OK, or Cancel button within the window.