My Oracle Support Banner

E-PC: PeopleCode API DoModalComponentPopup Opens Target Component with Non-Existing Keys (Doc ID 2754949.1)

Last updated on JULY 20, 2021

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.57 and later
Information in this document applies to any platform.

Symptoms

Target Component, called from another component through PeopleCode API DoModalComponentPopup, opens in Modal, but, displaying invalid values, as provided in the fieldlist parameter.

Per PeopleBooks, if invalid values are provided in the fieldlist parameter, it was expected that the target Component to open at the search dialog box.

The issue can be reproduced at will with the following steps:
1. Write code to open a Fluid Component (Secondary Component), using PeopleCode API DoModalComponentPopup, on a FieldChange event of a Push Button field.
2. Execute the code, passing invalid values in the fieldlist parameter.
3. Rather than opening the Search Dialog Box for the secondary Component, it accepts the fieldlist parameter, with the invalid values.

Note:
If the data exists in both calling and target components, the modal component opens fine and on the corresponding record.
If the data exists in the calling component, but not in the target modal, it was expected that it wouldn't find the data. However, it opens the component fine, with the values from the calling component.
Upon save, the data is being added to target tables.



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.