Aeon Known Issues
7 results found
-
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 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
400 Bad Request error handling is insufficient when using the request creation endpoint.
When the request creation endpoint encounters a 400 Bad Request error, a generic error message is returned that does not contain sufficient detail describing the problem.
Bug# 13747
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
The Web API caches some database values beyond the scope of a web request.
When making changes to an Aeon configuration via the Customization Manager, the Web API will continue to use cached values in some instances beyond what is needed to process the current request until the app is restarted in IIS.
Bug# 13746
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Request creation validation error message is inaccurate when the specified researcher user doesn't exist.
Creating a new request via the request creation endpoint that specifies a non-existent researcher will correctly return a validation error stating that the researcher's username does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid.
Bug# 13743
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Custom fields of the 'Transaction' context type break API routing
Using a custom field with the context type set to 'Transaction' in the CustomFieldDefinitions table breaks routing through the Aeon API and returns a 500 error.
Aeon v5.1
Bug# 13642
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon Web API v1.4.3.
-
Missing validation for activities in transactions
In TransactionValidator, there is no validation for ensuring that ActivityId and ResearcherUsername are mutually exclusive or that the user is associated with the activity.
Bug# 11562
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
TransactionValidator creates some redundant and/or incorrect error messages
For example, validating a transaction without username results in the following:
2x "username can't be empty"
1x " is not a valid username"
1x "user cannot be anonymous"Bug# 8889
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2