Using an nonexistent researcher username in the create request endpoint returns inaccurate validation messages
When using the create request endpoint, attempting to use a nonexistent researcher username as the reference when the RequestFor type is "researcher" returns inaccurate validation messages that do not make it clear that the user doesn't exist:
"{ResearcherUsername} is not a valid researcher username.",
"{ResearcherUsername} has been marked as an Anonymous user and cannot be a researcher username.",
"{ResearcherUsername} does not have a researcher association with {username}."
Bug# 27504
0
votes
released
·
AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
Released in Aeon v6.0.