Aeon Known Issues
202 results found
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Alma Primo Catalog Addon v1.5.4 and Aeon Alma Primo VE Catalog Addon v1.0.3.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Default button colors do not meet contrast requirements in certain cases
The default button colors in certain states such as "active" and "hover" don't meet WCAG contrast requirements with commonly used default background colors like grey or white.
Bug# 17604
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
The "Details" button in the request DataRow template files can't be activated using the spacebar key
The "Details" button contained in the request DataRow files cannot be activated via the spacebar key like other HTML buttons.
Bug# 17580
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Default hyperlink color does not have sufficient contrast with other body text used in Aeon default web pages
In situations where the hyperlink is around other body text, the default color (#08415c) does not meet WCAG contrast requirements when compared to surrounding body text colors used in the default web pages.
Bug# 17578
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Errors related to appointment fields are sometimes not announced by screen readers
Errors involving the appointment fields may not be announced by screen readers in some cases.
Bug# 17577
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Switch buttons on request forms can overflow on certain display/screen sizes
In some display/screen sizes, the Switch button on the request forms overflows outside of the item information box and requires horizontal scrolling to access.
Bug# 17576
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
The request status tooltip within the request DataRow template files does not meet accessibility requirements
The request status tooltip found within the request DataRow template files does not meet accessibility requirements for the following reasons:
-It is not possible to make the tooltip appear via keyboard controls
-The item status popup does not stay visible when the mouse pointer moves over the popup content
-The tooltip may visibly flicker in some casesBug# 17575
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Default page title for FirstTime.html is not sufficiently unique and descriptive
The default page title within the <title> element of FirstTime.html is "Aeon Logon", which is too similar to the page title for Logon.html and Logon2.html and does not accurately describe the page's purpose.
Bug# 17574
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Default form field border colors do not meet contrast requirements
The default border color for form fields in the Aeon web pages does not meet WCAG contrast requirements against a white background nor against the default form section background color.
Bug# 17573
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Focus indicators for interactive controls do not meet contrast requirements
The focus indicator for several interactive controls in the default web pages (e.g., input fields, buttons, etc) does not meet the minimum contrast required by WCAG.
Bug# 17572
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Focus indicators for hyperlinks do not meet contrast requirements in some cases
Hyperlinks on keyboard focus use the browser defaults for focus indicators which may not meet WCAG contrast requirements on the default web pages, particularly in the header and navigation bar areas.
Bug# 17571
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v6.0.
-
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 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v6.0.
-
Aeon Client dashboard does not properly handle database connection errors
The Aeon Client dashboard will correctly catch database connection errors, but will then attempt to use the connection, which causes an additional error.
Bug# 17093
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Keyboard controls cannot be used to dismiss cookie notification popup
Keyboard controls cannot be used to dismiss the cookie notification popup in certain web browsers.
Bug# 16945
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Reading rooms may allow overbooking when a full-day appointment is modified by staff
If a reading room is configured to only allow full-day appointments (i.e., if the minimum and maximum appointment length are equivalent to the open hours duration), and one of the booked appointments for a particular day is manually adjusted by staff in the Aeon Client to a shorter duration, the reading room will allow an additional appointment to be booked that day, leading to potential overbooking.
Bug# 16912
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Billing Account field label has incorrect 'for' attribute value
The Billing Account field found in the PhotoduplicationRequest.html file, Generic Photoduplication request pages, and all corresponding edit pages for these files contains an incorrect value in the label element's 'for' attribute. This value should match the 'id' attribute value in the field's input element to avoid accessibility issues.
Bug# 16833
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.1.29 Default and Feature-Specific Web Pages
-
Multithreading error during Aeon Client dashboard refresh
The following error can sometimes occur in the Aeon Client logs upon a dashboard refresh and may lead to Client slowness:
ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
System.InvalidOperationException: A multithreading issue is detected. The DevExpress.Data.CurrencyDataController.DisableThreadingProblemsDetection option allows you to disable the exception, but it does not resolve the underlying issue.
ManagedThreadId: 20; ThreadName: ''Bug# 16762
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2