Users can submit duplicate requests through external requesting by rapidly clicking the submit button.

Bug# 4702

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

If a request is created via the request creation endpoint, validation will not apply to enforce that the username on the request is associated with the specified activity ID.

Bug# 13748

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

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

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

The hidden field containing the username on includeappointmentinfo.html is not necessary as this information is obtained from the user's web session:

<div id="username" hidden><#PARAM name="Username"></div>

Bug# 13641

Using the "Submit Request" button for a saved request via the Actions dropdown menu or from the Request Details page allows the user to submit a request without an appointment, even if appointments are required.

Workaround: Comment out the Submit Request option on the DataRowDefaultRequest, RequestsInReviewDataRow/DataRowReviewRequest, and include_TransactionMenu pages.

Bug# 13543

When sending templated emails from the Aeon Client, the From Address and From Name are set to the default values in the LocalInfo Table or EmailFromAddress/EmailFromName customization keys instead of the values specified in the email template.

Bug# 13531

When a button does not explicitly declare a type in its code, it defaults to type="submit", which can sometimes lead to problems when processing transactions through a payment provider gateway.

Workaround: The code for the buttons in includepaymentbuttons.html should include the attribute 'type="button"'

Aeon v5.0.73/5.1 Default Web Pages

Bug# 13028

If a username contains a backslash, it will not be handled/returned by the Aeon API.

Bug# 12999

When editing template layouts on the main form of the Aeon Client, a layout control named "item0" may appear in the Customize Layout menu, and then will appear as "Root" if placed on the form. Dragging "item0" onto the form freezes the Client, and just opening the Customize Layout menu and seeing it prevents the Client from closing normally.

These issues may occur in both Aeon 5.0 and 5.1.

Bug# 12791

An EAD request can become uneditable if the SkipOrderEstimates parameter is set to "Yes" and the request fails web validation. This is because SkipOrderEstimates will set the Photoduplication status of the request to "Awaiting Order Processing," which makes the request uneditable, even though the web validation failure sent the request to Awaiting User Review.

Bug# 12663

Routing a request to a site outside of the current database view from the Request form does not refresh the Request list in the Client, and leads to an error in the logs stating "A thread exception has occurred" when trying to open that request from the unrefreshed list.

Bug# 12625

If a request is at the "Request in Processing" status and is not associated with an activity, associating it with one via the Request form and then saving gives an error in the logs stating "A thread exception has occurred."

Bug# 12624

The grid displaying associated requests on the Appointment form does not apply field customizations.

Aeon 5.1

Bug# 12618

When using Windows Server 2012, an error occurs when saving a DBC file with the Save button in SQL Alias Manager.

Bug# 12126

When clearing users, changing the username of a user on the list of similar users does not refresh the list. Clicking on a user who has had their username changed in the unrefreshed list causes an error and opens a blank user info form.

Bug# 12249

DBC passwords containing some special characters (such as semicolons) lead to errors when the DLL attempts to connect to the database.

Bug# 12295