Required Attribute Behavior in Custom Fields

(Doc ID 1594872.1)

Last updated on MAY 12, 2016

Applies to:

Oracle Fusion CRM Application Composer - Version 11.1.6.0.0 and later
Oracle Fusion CRM Application Composer Cloud Service - Version 11.1.5.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.6.0.0 version, Application Common

ACTUAL BEHAVIOR
---------------
Required fields do not display asterisk and when saving without filling that field the application throws an error message but it does not make the field red as it does in standard fields like Last Name and First Name.

EXPECTED BEHAVIOR
-----------------------
Expected to see same behavior for the standard fields.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log into application
2. Set any standard field as required
E.g Common Application
Trading Community Person Profile object
Gender field set as Required
3. Save and Close
4. Go to Customers
5. Create a new consumer
6. Leave Gender blank and save, it throws the error
Attribute Gender in PersonDEO is required
7. If Last Name is left blank, there will be a popup message and a red mark in its field.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Customer wants to harmonize the behavior

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