Small notes are located outside the label for fields on web forms where they are still accessible by screen readers but are not read out automatically like they would be if located inside the label. This can lead to screen readers skipping these notes unknowingly.
Bug# 144200 votes
The OtherHeaders property used on SMTP.config is set initially but is then overwritten and will not function as expected, which can lead to issues with configuring emails.
Bug# 143780 votes
Screenshots submitted through the Feedback form of the Client will be clipped incorrectly on high-DPI monitors.
Bug# 143330 votes
Trying to filter or sort requests associated with an appointment by either their start or stop time in the grid view breaks the results and changes the grid to a blank page with an orange X over it.
Bug# 141660 votes
Selecting the current date when adding attendance count to an activity throws an error stating that the date cannot be in the future.
Bug# 139300 votes
Creating an instance of the Chromium browser in an addon with privateMode set to true persists the cache between browser instances and also between users.
Bug# 138520 votes
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# 137470 votes
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# 137480 votes
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# 137460 votes
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# 137430 votes
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# 136410 votes
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# 135430 votes
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# 130280 votes
If a username contains a backslash, it will not be handled/returned by the Aeon API.
Bug# 129990 votes
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# 127910 votes
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# 126630 votes
Routing a request to another site from the Request form and then opening it from the Request list causes an error
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# 126250 votes
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# 126240 votes
The grid displaying associated requests on the Appointment form does not apply field customizations.
Bug# 126180 votes
When using Windows Server 2012, an error occurs when saving a DBC file with the Save button in SQL Alias Manager.
Bug# 121260 votes