My Oracle Support Banner

E-PORTAL/E-PC: Event Mapping Is Not Triggered when the Peoplecode Is Mapped to a Prompt Edit Field, in a Component that Is Called in Modal, if The Value of the Field Is Modified Through the Prompt Lookup (Doc ID 2757142.1)

Last updated on MARCH 03, 2021

Applies to:

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

Symptoms

Event Mapping is not getting triggered when the PeopleCode is mapped to a Prompt Edit Field, in a Component that is called in Modal, if the value of the field is modified through the Prompt Lookup.

The issue can be reproduced at will with the following steps:

[Using Workforce Administration > Job Information > Add Empl Instance(hidden), in HCM 9.2, as example]

1. Using Application Designer, create the PeopleCode to be used in the Event Mapping.
2. Create the Related Content Service for that PeopleCode, in PeopleTools > Portal > Related Content Services  > Define Related Content Service.
3. Associate the Service to the Content Reference, in PeopleTools > Portal > Related Content Services  > Manage Related Content Service, Event Mapping. Map it to Component Record Field Level Event Mapping.
    For the example, map it to Record.JOB, Field.POSITION_NBR, Event.FieldChange. The Processing Sequence does not matter.
4. Navigate to Workforce Administration > Job Information > Add Employment Instance.
5. Inform Empl ID and Empl Record.
6. Click on the 'Add Relationship' button. The Add Employment Instance page opens.
7. Manually enter a valid value for field Position and tab out. Event Mapping is triggered, as expected.
8. Use the prompt lookup of field Position to select another value for that field (Position - JOB.POSITION_NBR).
9. Once the value is selected and context return to the field, Event Mapping should have been triggered. It was not..

Note:
To replicate the issue using other components, the component that has the Event Mapping should be called in modal, for example, through PeopleCode API DoModalXComponent.
Example:
- Modify the system to call the User Profile component from Component My System Profile, using DoModalXComponent.
  Suggestion: Add a push button in Component My System Profile and use PeopleCode API DoModalXComponent, in that field's FieldChange PeopleCode, to call the User Profile component in modal.

- Map the Service to the User Profile Content Reference, to any of the fields that have a prompt lookup, Event.FieldChange.
- Test.
  Note that the event mapping will be triggered if the value of the field is manually entered.
  However, it is not triggered when the value is modified through the prompt lookup.

 

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.