Aeon Known Issues
91 results found
-
Small notes in Aeon can be easily missed by screen readers
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# 14420
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
"Approve Billing" button does not work on request pages
Clicking the "Approve Billing" button from the "Actions" dropdown menu for a request or on the request's detailed information page will result in an error.
Workaround: Use the "Approve Order" button on the Order Billing web page to approve the billing charges for the request.
Bug# 14404
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Web DLL v5.1.3.
-
Several incorrect links in Aeon action menus
Two Aeon web action menus, includeTransactionMenu.html and DataRowDefaultRequest.html, have incorrect links for the following menu items:
-Delete Item
-Approve Estimate
-Approve BillingThe links for these items contain Form parameters where they should instead have Type parameters.
Bug# 14398
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.1.18 default web pages.
-
Credit card webpages do not specify type attribute on button elements.
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.1.18 default web pages.
-
The role="heading" attribute on top level <div> containers may cause issues for screen readers
The role="heading" attribute on the <div> containers surrounding most web pages can cause strange behavior with screen readers depending on the content of the file.
Bug# 13847
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.1.19 default and feature-specific web pages.
-
Certain activity requests trigger the appointment requirement on web pages
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Web DLL v5.1.2.
-
Unnecessary div element with id="username" on include_appointment_info.html
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 default and feature-specific web pages
-
"Submit Request" button does not enforce the appointment requirement for saved requests
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Appointment Exception Dates sometimes may not be reflected in the web scheduling interface
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Web DLL v5.1.1/Aeon v5.1.14 Appointment Scheduling web pages.
-
Appointment scheduling calendars on the web may load slowly if the reading room is fully booked
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Web DLL v5.1.1/Aeon v5.1.14 Appointment Scheduling web pages.
-
Setting a custom field to a blank value can cause an internal error in the Aeon web DLL
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Web DLL v5.1.1.
-
Some button elements in the default web pages do not include a type attribute
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 default web pages
-
Some default EditGenericRequest forms are missing the required Transaction Number field
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.htmlAeon 5.0/5.1 Default Web Pages
Bug# 12899
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.1.14 default web pages.
-
Buttons not working on DataRow_ElectronicDelivery
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.1.14 default web pages.
-
EAD requests that skip order estimate can become uneditable
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v6.0.
-
The "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't return users to the logon menu
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
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.1.14 default web pages.
-
The Web DLL does not properly validate researcher request links when submitting requests
When submitting a request for a researcher, the DLL does not properly validate the proxy relationship between the user submitting the request and the selected researcher.
Bug# 11699
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
BillingAccountsVisible param tag does not work on PhotoduplicationRequest.html
In the default Aeon web pages, the BillingAccountsVisible param tag on PhotoduplicationRequest.html does not properly hide the BillIng Account dropdown if Billing Accounts are disabled.
Bug# 11533
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
DataRow headers don't meet accessibility
Once the h5 header is updated to h4, there is an empty header that breaks accessibility.
Bug# 10178
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.1 and v5.0.73 default web pages
-
0 votes
Released in v5.0.24 Default Web Pages on 22 Jan 2021