OKEKAUWB Form Does Not Allow Personalization of Making Priority Rating Required
(Doc ID 1070214.1)
Last updated on FEBRUARY 13, 2019
Applies to:Oracle Project Contracts - Version 12.0.4 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.
The requirement is to make Priority Rating field mandatory in the Contract Authoring Workbench.
The Navigation is: Help-Custom Code-Personalize
Then set the following values on the form:
ActionsObject Type: ItemTarget Object: K_HEADER.PRIORITY_RATING
Property Name: RequiredValue: True
Although the Priority Rating field will show as yellow, the user is able to save the record without populating a value for Priority Rating.
All other fields will force a FRM-40202 error if left blank on a save.
This issue does not happen in 184.108.40.206.
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