E-PFC/E-PORTAL: Setting a Field as Required in Page and Field Configuration Does Not Prevent the Transaction to Be Saved if the Field Is Left Blank (Doc ID 2888786.1)

Last updated on AUGUST 10, 2022

Applies to:

Symptoms

Page and Field Configuration is not enforcing mandatory / required field validation, allowing the system to proceed with the remaining component processing.
The Required flag was supposed to implement an edit validation on the field, not allowing the transaction to be saved and preventing other processing to be executed, unless a valid value was informed.


The issue can be reproduced at will with the following steps:
1. Add Page and Field Configuration to a field in a delivered page, configuring it as a required field.
2. Navigate to the impacted component and create a transaction, without informing a value for the modified field.
3. Save the transaction.
4. Note that, even though a message is displayed, the transaction was created.

Changes

Cause

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