Open hjuntan opened 2 months ago
As only Name, Phone, Address, Email, and Role is required for a person to be created so the guide must be explicitly specifying which one can be blank or not. However, for the other field including Tag is optional; therefore, if the user key in the prefix, it means that they are intentionally want to add some more information to a person in NetConnect. Therefore, it does not make sense for a user to specify that they want to add an optional field with an empty value. Also business use case wise, tag should not be empty anyway.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
Similar to issue of tag inconsistency: the tag can be blank while the app does not allow it
However the app's error message also did not specify that the tag cannot be blank as well