Open Statspadders opened 1 year ago
For email, we only put restriction on username@example.com, where the @ is compulsory. We do not have a restriction on the portion after the @ since some companies use a specific domain as that part of the email, for example name@companyName.com, and it is not very feasible to make a restriction on company names.
Team chose [response.Rejected
]
Reason for disagreement:
This is a very small feature flaw, wherein the system is able to create a client even if an invalid email address is provided.
Input: xxxx@123123.com
Expected: Not an valid email is used.
From the UG: EMAIL: A valid email of a client whose contact is to be stored in FAid
FAid: