Phone-Number Is Populated To PrimaryFormattedPhoneNumber Despite Of Validation Exception
(Doc ID 2364429.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Fusion Sales Cloud Service - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Accounts, Contacts, Households
Phone-Number is populated to PrimaryFormattedPhoneNumber despite of Validation Exception
We have an object validation, that validates every single phone field (CountryCode, AreaCode, ...) and throws an error,
if the AreaCode has a leading 0
if any Phone field contains letters or special characters.
On the account object, when you type in a number which makes the validation throw the error as you save > click ok in the error > click save again (please see the attached video for the workflow) , the invalid number is displayed in the PrimaryFormattedPhoneNumber field on the overview page. The invalid number should not be transferred in this field, because this is exactly what we want to prevent with the validation.
Validation message suppose to show second time and it is not suppose to save
The issue can be reproduced at will with the following steps:
1. In Account there is phone no validation script
2. Navigate to account object and create account with valid phone no click save and close or save
3. In edit details page edit the no with alphabets click save warning message will show then again click save or save and close then it is saving with out warning message but in details page showing correct no but in Overview page showing with wrong no.
The issue has the following business impact:
Due to this issue, users getting confused.
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