Custom Predicate Not Taking Effect on Records Immediately
(Doc ID 2316419.1)
Last updated on NOVEMBER 14, 2017
Applies to:Oracle Fusion Sales Cloud Service - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 1.0]
Information in this document applies to any platform.
Have created a custom predicate for opportunity records based on a custom field 'PartnerRegistrationStatus_c' in pportunity.
Column name of the custom field is EXTN_ATTRIBUTE_CHAR053, and when the status is not in certain values,
then need the ability for users to be able to edit the opportunity records.
(&TABLE_ALIAS.opty_id IN (SELECT DISTINCT myopres.opty_id FROM Moo_opty_resources myopres WHERE myopres.resource_id = (SELECT HZ_SESSION_UTIL.GET_USER_PARTYID FROM dual ) AND myopres.access_level_code IN ('200', '300') )) AND &TABLE_ALIAS.EXTN_ATTRIBUTE_CHAR053 NOT IN('TEST_C_CLOSED','TEST_C_EXPIRED','TEST_C_REBATEREQUESTED','TEST_C_LOST')
Now when the user change the value in the PartnerRegistrationStatus_c field the
record is not becoming readonly, but when the user logout and login the record is readonly as expected.
The custom predicate not taking effect on records immediately,
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