Making Custom Interaction Fields Conditionally Required Results In A Server Exception (Doc ID 1938620.1)

Last updated on AUGUST 30, 2016

Applies to:

Oracle Fusion Common CRM Cloud Service - Version 11.1.8.0.0 and later
Oracle Fusion Common CRM - Version 11.1.8.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.8.0.0 version, Common

ACTUAL BEHAVIOR
Custom field with type long text having an expression to manage the fact this field is mandatory is not working after Rel8 upgrade

EXPECTED BEHAVIOR
-----------------------
Shoukd work

STEPS
-----------------------

The issue can be reproduced at will with the following steps:
1. Navigator > Customize > Application Composer > Common application > Standard object interaction
2. Create custom field : NextAction_c > with type = Long Text and a condition/expression on required field :

if (InteractionTypeCode == 'IMEETING') {
return true
}
else {
return false
> Save and add to detail page (is done by default)

3. Edit a customer > Create an interaction > select type = Meeting
> Fied NextAction is not flagged as mandatory (no star) but is already mandatory
so if user save at this step , get error : ADF_FACES-60097:For more information, please see the server's error log for an entry beginning with: ADF_FACES-60096:Server Exception during PPR, #8

4.
Edit a customer > Create an interaction > select type = Meeting
> Fied NextAction is not flagged as mandatory (no star) but is already mandatory
> so if user fill this field with a text value > save > no error

5.
Edit same customer > Edit same interaction with type = Meeting
> Fied NextAction is now flagged as mandatory and is already mandatory
> so you can update the value
> if blanking the filed get standard mlessage
Error: A value is required.
You must enter a value.> in changing interaction type (eg chat)
> blank the field NextAction
> Save: n o error

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot mange the required property by using expressionODM Issue Clarification

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms