PeopleCode Events that do not fire in Component Interface

When you create an Component Interface object in Application Designer that wraps an existing PeopleTools Component, there are some subtle issues with some PeopleCode events that you should be aware of. This is documented in PeopleBooks but is often overlooked by developers. Additionally, if you are creating a Component Interface definition for a Component that is delivered or someone else wrote you can run into problems if the Component is using certain PeopleCode events that are critical to the logic of the component.

PeopleCode Issues with Component Interface

Here are the PeopleCode vents that do NOT trigger in Component Interface.

• Page Activate - See Stop Using Page Activate PeopleCode

• TransferPage and Transfer PeopleCode functions

• DoSaveNow

• DoModal

• SetCursorPosition

• SearchInit

• SearchSave

• RowSelect

• Menu PeopleCode

• %page and %panel - Do NOT resolve - See Page and Component Interface: A Warning

So if you are creating a component that you want to expose in a Component Interface, you should be aware of these limitations and make sure you are not using any of these events or functions. The two that I see the most that cause issues is the DoSaveNow and the Page Activate events.