I would like to request an enhancement for rule Edit validate AppValidateMultipleEmailAddresses (PegaAppCA ruleset).
The implementation of this rule is very basic and not good enough for production environment to validate email addresses.
for example it accepts the input below as valid email addresses which are obviously not.
We have specialized this rule and implemented the validation with regex expression which validates also the examples above. The edit validate we created works fine when it is triggered from a input field but when the task is submitted this regex makes the java thread hang in SOME CASES WITH JUST ONE EMAIL ADDRESS. This is a strange behaviour because the same edit validate was also called before submitting the task. So when the email address was entered and edit validate was fired. In that case we don't see any problems.
I have created a Service Request (SR-C98057) for this issue but is its closed and the engineer asked us to create an enhancement to improve the OOTB rule.
Please improve the OOTB edit validate so it validates multiple email addresses in a correct way.
***Moderator Edit-Vidyaranjan: Updated SR details & FDBK ID***
A feedback request has been created on your behalf in our internal portal. The feedback ID is tagged to the issue description above (under Related Support Case Number). Use this FDBK ID as reference to connect with your Pega Account Executive to track the progress of this request.
Posted: 2 years ago
Posted: 29 Mar 2019 8:55 EDT
Michael Michalski (MMIchalski)
Consulting Manager - Public Sector
Be careful with implementing this please. Some of the examples noted in the original post are, indeed, valid email address formats. For example someone@somewhere is valid. Most validators available are too strict.
Please read the following article. It is 12 years old but I have no reason to believe i is not still applicable. It's content can be easily verified against the RFC. Out of the box, we should be careful to not be strict beyond what is defined in the RFC.