What components are not suitable to work as component interfaces

When creating a new Component Interface (CI), it must select the component based-on to build the CI from. Sometimes the selected component may not be suitable to be used as a CI directly without proper customization to the base component, even if it is a Peoplesoft delivered component.

There are limitations, some of which are documented in the Component Interface PeopleTools Peoplebooks. For example, if the component used as the underlying component for CI makes use of the following functions, the new CI will not work properly.

Components with the functionalities below will not work properly as component interfaces

1. Has link/button on page, which bring up secondary page to input additional data
2. Uses the PeopleCode events and functions that relate exclusively to GUI and online processing. These include:
a) Search dialog processing.
When you run a component interface, the SearchInit, SearchSave, and RowSelect events don't fire. This means that any PeopleCode associated with these events will not run. The first event to run is RowInit.

b) Menu PeopleCode and pop-up menus.
The ItemSelected and PrePopup PeopleCode events are not supported. In addition, the CheckMenuItem, DisableMenuItem, EnableMenuItem, HideMenuItem, and UncheckMenuItem functions arent available.

c) Transfers between components, including modal transfers.
The TransferPage, DoModalPageGroup, and IsModalPageGroup functions cannot be used.

d) Dynamic tree controls.
Functions related to this control, such as GetSelectedTreeNode, GetTreeNodeParent, GetTreeRecordName, RefreshTree, and TreeDetailInNode cannot be used.

e) ActiveX controls.
The PSControlInit and PSLostFocus events are not supported, and the GetControl function cannot be used.

f) DoSave() and DoSaveNow().
The DoSave() and DoSaveNow() pcode functions are not supported. You should use the component interface Save() method and wrap the DoSave() and DoSaveNow() functions so they dont execute when called from a component interface.

g) Functions that are ignored in a component interface call.
Some PeopleCode functions are ignored if they are called through a component interface. These functions are:
WinMessage
CheckMenuItem
DisableMenuItem
EnableMenuItem
HideMenuItem
UncheckMenuItem
SetCursorPos
TransferPanel
TransferPage
DoModalComponent
IsModalComponent
DoModalPanelGroup
IsModalPanelGroup
GetSelectedTreeNode
GetTreeNodeParent
RefreshTree
TreeDetailInNode
GetControl
DoSave
DoSaveNow
Gray
Ungray


Workaround/Solution:

A possible workaround is to copy or create a new component based on the existing PS delivered component, customize and tailor the functionality of the component so that it will function as expected as a CI.