Request creation validation error message is inaccurate when the specified username doesn't exist.
Creating a new request via the request creation endpoint that specifies a non-existent username will correctly return a validation error stating that the user does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid, even if valid values had been entered.
Bug# 17649
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 v5.2