Get Started with Redwood for Oracle Cloud HCM Begin Now
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.
Phone number length validation autocomplete rule
Summary:
Phone number length validation autocomplete rule
Content (please ensure you mask any confidential information):
We currently have an autocomplete rule to validate length of phone number (Phone number object) being entered for 5 countries. The rule has 5 if conditions with length conditions and error messages. As part of an initiative we are planning to extend this rule to include length validation to another 55 countries, this will require extending the same autocomplete with 55 if conditions.
Will this impact performance by any chance? What are the best practices for implementing rules with such high volume of conditions? Any design recommendations for this please?
Tagged:
0