For more information, please refer to this announcement explaining best practices for getting answers to questions.
Autocomplete not working as expected for duplicate phone number check
Summary:
Autocomplete keeps triggering in all personal information pages when there is a failed transaction.
Content (please ensure you mask any confidential information):
Oracle delivered duplicate phone number check exists. However, there is a limitation for US numbers where a hyphen is added when the phone number is stored in the backend in the format (NNN hyphen NNNN). When a user enters a duplicate phone number of the same type without a hyphen (NNNNNNN) system fails to throw the seeded error message and the transaction gets submitted.
We have written the below autocomplete rule which is making the duplicate check even when the hyphen is not entered by user. However, if an employee has a failed transaction in transaction console for Change personal information and that employee tries to update Emergency contacts, personal details or any personal information page this auto-complete error keeps popping up. Any recommendations please?