Monday, December 27, 2010

Events that are not triggered by Component Interface

Here is the excerpt from Peoplebooks:

People Code events and functions that relate exclusively to GUI and online processing cannot be used by component interfaces. These include:
? 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.
? 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 aren?t available.
? Transfers between components, including modal transfers.
The TransferPage, DoModalPageGroup, and IsModalPageGroup functions cannot be used.
? Dynamic tree controls.
Functions related to this control, such as GetSelectedTreeNode, GetTreeNodeParent, GetTreeRecordName, RefreshTree, and TreeDetailInNode cannot be used.
? ActiveX controls.
The PSControlInit and PSLostFocus events are not supported, and the GetControl function cannot be used.
? 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 don?t execute when called from a component interface.
? 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

No comments:

Post a Comment