Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Issue with ORC merge when Duplicate phone type not allowed implemented using autocomplete rule
Summary:
The original requirement was to add a validation rule that would prevent a person from having more than one of a particular phone type. This is Use Case 16 for Guidewell Mutual project. This requirement was implemented using the below code. But, now the issue is, when an external candidate in Recruiting applies for a opening and on running the duplicate check, he is found to be an existing person; the user selects the existing person to merge the records; but gets an error due to this autocomplete rule with the same error message used here.
To avoid the issue, I tried adding an additional criteria in the IF clause to say - "and Person_Phone.Number Not equal to rowVar_Phone.Number" but still the same issue.
Tagged:
0