Aeon Known Issues
130 results found
-
The label color for fields that fail server validation does not pass color contrast requirements
When a field fails server validation, the web pages set the color of the field label to a red color that does not pass contrast requirements with the default form section color.
Bug# 18758
0 votes -
Current Password field on ChangePassword.html has a broken 'aria-describedby' attribute
The 'aria-describedby' attribute for the Current Password field on ChangePassword.html is broken and may be flagged as an issue by accessibility checkers.
Bug# 18687
0 votes -
Modal dialog for web alerts contains broken 'aria-labelledby' attribute
The 'aria-labelledby' attribute used on the modal dialog for web alerts is broken and causes an accessibility issue.
Bug# 18686
0 votes -
Force password reset option may fail in certain cases
If the WebAuthType key is set to RemoteAuth in the Customization Manager and the force password reset option is toggled for a user using Aeon Authentication, the user will not be prompted to change their password upon logging in if the Aeon Authentication checkbox is not checked on the user record.
Bug# 18390
0 votes -
Aeon System Manager does not refresh custom field definitions
The Aeon System Manager caches custom field definitions defined in the Customization Manager and does not automatically refresh these when new entries are made.
Bug# 18405
0 votes -
Aeon Client Options form controls are incorrectly aligned
The controls located within the Aeon Options form in the Aeon Client are not aligned properly within the borders of each section of options on this screen.
Bug# 18418
0 votes -
DataRow_ElectronicDelivery.html does not display File Size and Transaction Number
The DataRow_ElectronicDelivery data row template does not display the associated file size and transaction number for requests.
Bug# 18112
0 votes -
Default FAQ web page contains inaccurate information about cookies
The default FAQ web page contains information about cookies stating that "the technology that we use sends a Session ID to be stored on your machine. You can refuse this cookie and still be able to use Aeon without any problems."
This information is inaccurate as the Session ID cookie is essential for the Aeon web interface.
Bug# 18264
0 votes -
Appointment merge fields are blank when used in Transaction type email templates
Appointment merge fields used in Transaction type email templates will appear blank when emails are generated for the template.
Bug# 17993
0 votes -
ViewSearchResults.html contains an incorrect <u> tag
The default ViewSearchResults.html web page contains an incorrect usage of the <u> tag to emphasize text where a <strong> tag should be used instead.
Bug# 17985
0 votes -
Alma Primo Catalog addons do not display linked records
The Aeon Alma Primo and Alma Primo VE Catalog addons may only import one call number for a record associated with multiple call number entries.
Bug #17908
0 votes -
Request creation validation error message is inaccurate when the specified username doesn't exist.
Creating a new request via the request creation endpoint that specifies a non-existent username will correctly return a validation error stating that the user does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid, even if valid values had been entered.
Bug# 17649
0 votes -
The default selection in the Appointment dropdown is inconsistent
When a request form is loaded for the first time, and a reading room is selected with no appointments scheduled, the Appointment dropdown remains blank instead of showing the "No Appointment" text. However, after swapping to a reading room with an appointment, it will display the "No Appointment" text even though there is an appointment scheduled in the room.
Bug# 17588
0 votes -
Request datarows contain an empty hyperlink when item title is missing
When no item title is provided, the request datarows will contain an empty hyperlink which may cause confusion for screen reader users.
Bug# 17579
0 votes -
Appointment scheduling web calendar is not properly formatted for screen reader navigation
The HTML tables used to format the appointment scheduling calendar on the web are improperly formatted and cause navigation issues for screen reader users.
Backlog# 18519
0 votes -
Using the <#OPTION> tag with a CustomDropDown group requires the group name to match the target field name
CustomDropDown group selections displayed on web forms using the <#OPTION> tag can only be saved to a field with a name matching that of the CustomDropDown group name.
Bug# 17407
0 votes -
Checkboxes generated with the Aeon <#OPTION> tag will save data in an incorrect format
Using the <#OPTION> tag to generate a group of checkbox selections for a CustomDropDown group on the web will cause the data selected to be saved with a comma prepended to each value.
Bug# 17406
0 votes -
Attempting to edit an appointment with invalid data throws errors
Appointments containing invalid data will still appear on the User form and within the Appointment control on the Request form, but the Aeon Client will be unable to open the Appointment form and will throw an unhandled exception error when attempting to edit the appointment:
ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
Bug# 17378
0 votes -
Submission of XML/HTML tags in EAD requests will cause errors
If POSTed data from an EAD request contains an XML/HTML tag, the Aeon server will respond with a 500 error message.
Bug# 17275
0 votes -
Rescheduling an existing appointment in the Aeon Client may result in an error if the same appointment is also being edited elsewhere
Editing the Start Date or End Date of an appointment via the Appointment form in the Aeon Client may result in the following error if the appointment was simultaneously edited elsewhere:
ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
DevExpress.XtraScheduler.Internal.ActualMappingException: Error in the End mappingBug# 17181
0 votes