The credit card payment webpages are missing the type="button" attribute on <button> elements, which can lead to issues when submitting the payment forms.

Bug #14371

Submitting a request for an activity through the web pages incorrectly triggers the appointment requirement for reading rooms requiring appointments. This issue does not occur for EAD and external requests.

Bug# 13821

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

Appointment Exception Dates set in the Customization Manager for a reading room may not be reflected in the web scheduling interface in some cases but will display correctly in the Client.

Bug# 13196

In some places in the Aeon Client, an appointment's start and end times display as UTC instead of being converted to the appropriate server time.

Bug# 13160

If a reading room is fully booked with appointments for a long period of time, the appointment scheduling calendar for that room on the web pages will take an excessive amount of time to load.

Bug# 13107

If a custom field (defined in the CustomFieldDefinitions table) is added to a form on the web as an optional field, submitting the form without a value for that field will return an error.

Aeon v5.1

Bug# 13020

The following Edit pages are missing a hidden TransactionNumber input, which is required for edit pages, and instead have a hidden TransactionLink input, which is not used on edit pages:
-EditGenericRequestManuscriptPhotodup.html
-EditGenericRequestMonographPhotodup.html

Aeon 5.0/5.1 Default Web Pages

Bug# 12899

The View and Delete buttons, as well as the Details, View Item, and Cancel Request options from the Actions dropdown menu do not work on the DataRow_ElectronicDelivery template (used on the Electronically Delivered Items web page).

Workaround: Click on the item title and use these options from the top of the item details page.

Aeon 5.1

Bug# 12824

Clicking the "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't allow users to stop the request form and return to the logon menu.

Bug# 12668

Generating a new email that is not based on a template from a request form in the client incorrectly populates the email's from address with the value in the EmailFromAddress customization key instead of the site's information entered in the LocalInfo table.

Bug# 11000

Transaction numbers do not get to Touchnet due to an issue with ancillaryData handling.

Bug# 10472

Once the h5 header is updated to h4, there is an empty header that breaks accessibility.

Bug# 10178

Bug# 9774

An empty string would be produced when the persist value drop-down in the atlasUtility.js due to the handling of the double-quotes.

Bug# 9632

The gray text used on some of the default pages doesn't meet contrast requirements for WCAG.

Bug# 8005

When adding a transaction to a bundle, Aeon is creating an entry in the History table. The Entry column is limited to 255 characters, which throws an error if the bundle has a name that exceeds the limit.

Bug# 8806

When a user submits a request, the request is created as expected after logging in. Then, if the user clicks the refresh button in their browser, a duplicate request is submitted.

If the user is already logged in and attempts to refresh after submitting the request, I get the: "This form has already been submitted. Duplicate request not created." error as expected.

Bug# 8826

The custom search is displaying the correct, converted, time in the client; however, custom searches look for the unconverted UTC time from the database.

v5.0.3 and 4.1.0.2
Bug# 8689

The default pages do not currently support special date formats such as ISO8601 for the ActivityStatusDate. When adding the ISO8601 to the code, the pages are preventing the UTC time from being converted to the user's local timezone.

Bug# 8611