Aeon Known Issues
186 results found
-
"Skip to main content" link remains invisible when focused on in certain browsers
The "Skip to main content" link remains invisible when it is focused on using the keyboard in certain browsers including Chrome and Safari. The link appears as intended in Firefox.
Bug #15254
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Adding Appointment tab without any reading rooms configured crashes Aeon Client
Attempting to add the Appointment tab when customizing the Client layout will cause the Client to freeze/crash if no reading rooms have been configured in the Customization Manager.
Bug# 14767
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Request callslips cannot be printed from an Activity record if any Transaction or Activity context-type custom fields are defined
Using the "Print Callslips for Requests Awaiting Processing" dropdown option from the "Print Callslips" button on an Activity record results in the following error if any custom fields are defined in the CustomFieldDefinitions table:
"An error occurred while attempting to print callslips (Ambiguous column name 'Activity ID'. "
Workaround: Print the callslips for Activity requests from the Awaiting Activity Processing queue or individually from each request record.
Bug# 14570
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
<#OPTION> web tag cannot be used to automatically generate a list of checkbox options for CustomDropDown-type custom fields
Using the <#OPTION> web tag to automatically generate a list of checkbox options for a group defined in the CustomDropDown table does not work if the group is a CustomDropDown-type field defined in the CustomFieldDefinitions table.
Bug# 14532
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Cloning a photoduplication request in the web creates a non-photoduplication request
Cloning a photoduplication request from the web interface will take the user to the default request form for a non-photoduplication request.
Bug# 14459
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
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.
-
OtherHeaders property used on SMTP.config does not function as expected.
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# 14378
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
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.
-
Filtering/sorting requests by appointment start or stop time breaks results
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# 14166
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Cannot select the current date when adding attendance count to an activity
Selecting the current date when adding attendance count to an activity throws an error stating that the date cannot be in the future.
Aeon v5.1
Bug# 13930
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
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.
-
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.) respondedReleased 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.) respondedReleased 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.) respondedReleased 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.) respondedReleased in Aeon Web API v1.4.3.
-
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