Aeon Known Issues
186 results found
-
WebView2 browsers used by addons can occasionally cause errors searching for requests in the Aeon Client
Closing a request form for a request using the WebView2 browser and subsequently searching for a new request in the Aeon Client can sometimes lead to an issue where Aeon will open the previous request instead of the one for which the search was performed.
Bug# 24181
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Client v5.2.4.
-
Invalid End Date can be entered on the Appointment form in Aeon Client
Manually confirming or unconfirming an appointment via the Appointment form in the Aeon Client will save any other changes made to the information on the form without enforcing data validation, which can lead to the following error loading appointments in the Client if an invalid End Date was entered and saved:
“Error refreshing appointments
Error in the End mapping
Some appointments could not be loaded. Please contact support.”Bug# 26376
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Client v5.2.4.
-
Aeon Client throws error loading appointments if the casing for a username is inconsistent between the User record and Appointment record
If a username uses different casings in the database between the User record and an Appointment record for that user, this will cause an error when loading the appointment calendar in the Aeon Client that states: "Error in the PreferredName mapping."
This mismatch can happen if:
1. A request is cloned to a user via the Clone Request to Another User option in the Aeon Client and a different casing for their username is typed into the Username field on the closing interface.
2. An appointment is then created for that user from the cloned request using the different username…0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Server v5.2.6/Aeon Client v5.2.4.
-
System information from the LocalInfo table is not properly imported into the From field on email templates
System tags used to import information from the LocalInfo table (e.g., <#System.GeneralEMailAddress>) will not import the correct value when configured in the From field on email templates.
Bug# 23764
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Client v5.2.4.
-
DLL logs will not be created after Aeon 5.2 update
DLL logs will not be created after updating to Aeon 5.2 due to a lack of appropriate permissions for web users.
Bug# 23261
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Server v5.2.4.
-
Past appointments and future appointments with start dates exceeding the Min Lead Days for the reading room are not viewable on web
Users cannot view appointment details on the web interface for appointments with start dates in the past or with start dates exceeding the Minimum Lead Days setting for the reading room. Clicking on an affected appointment will display the SLAppointmentAssociationError status line to the user (default text: "Error: You cannot view an appointment you are not associated with.").
Aeon 5.2
Bug# 22857
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Server v5.2.4.
-
Aeon 5.1 Scheduled Date date picker calendar does not properly color disabled dates
Disabled dates are not colored correctly in the date picker tool used with the ScheduledDate field in the Aeon 5.1 web pages.
Bug# 22802
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon default web pages v5.1.41.
-
<#Request.CancelNote> does not populate in ItemCancellation emails from template
The <#Request.CancelNote> element does not populate in item cancellation emails and displays as empty space within the email.
Workaround: Use <#Request.ReasonForCancellation> in the email template instead of <#Request.CancelNote>
Aeon 5.2
Bug# 22789
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon Client v5.2.2.
-
JavaScript console error may occur when using the appointment scheduling web interface
After typing a date manually into the Appointment Date text field on a web request form, pressing the TAB key or clicking the mouse to move focus elsewhere will return a JavaScript console error in the web browser.
Bug# 19926
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.2.11 Default Web Pages
-
Some characters are not correctly encoded when logging
Some characters (such as those with diacritics) are not properly encoded in log files.
Workaround: Add <encoding value="utf-8" /> under the <appender> element in the default log.config files.
Bug# 21305
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
Search box on ViewSearchResults.html has poor contrast in some browsers
The border used for the search box on ViewSearchResults.html does not meet color contrast requirements in some browsers, including Safari.
Bug# 19937
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 default web pages
-
Using the Enter key on the Saved Requests page selects all requests without announcing selection to screen readers
Pressing Enter on the ScheduledDate field on the Saved Requests page (ViewUserReviewRequest.html) will checkmark select all requests on the page, without this change being announced to screen readers.
Bug# 19801
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 default web pages
-
Formatting error in Aeon Client log entry when user is set to away
The following formatting error will appear in the Aeon Client log when a user signed into a reading room is set to away:
INFO AtlasSystems.Aeon.FormDashboard - <log4net.Error>Exception during StringFormat: Input string was not in a correct format. <format>Setting user {)} to away.</format><args>{username}</args></log4net.Error>
Bug# 19730
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
MinimumLeadDays behavior functions differently for appointments vs requests
The MinimumLeadDays value for a reading room configured in the Aeon Customization Manager will consider not only the current date, but also the current time when calculating whether a request can still be submitted for an appointment, but will not consider the current time when making the same calculation for whether an appointment can still be scheduled in the room.
This means that it is possible for an appointment to be scheduled for the room that would then not allow any requests to be associated with it.
Bug# 19633
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in v5.2.11 Feature-Specific Web Pages
-
Requests are sometimes created with a NULL transaction status
Requests in Aeon may sometimes be created with a blank/NULL transaction status that can then cause issues in the Aeon Client.
Bug# 19511
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2
-
ItemSubTitle (Series) field on EditEADRequest.html contains an incorrect 'required' attribute
The ItemSubTitle (Series) field on EditEADRequest.html contains a 'required' attribute even though that field is not intended to be required by default.
Bug# 18920
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 default web pages
-
Transaction menu button text is not fully visible on certain display sizes
The text content of the transaction menu buttons does not fully display on small screen sizes or high zoom levels and requires horizontal scrolling to view. In some cases, horizontal scrolling is not enough to read the full button text.
Bug# 18917
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 default web pages
-
Actions dropdown options are not fully visible on certain display sizes
The Actions dropdown options do not fully display on small screen sizes or high zoom levels and require horizontal scrolling to view.
Bug# 18915
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 default web pages
-
ReadingRoomID field label contains incorrect 'for' attribute value on ViewAppointments.html
The ReadingRoomID field label in the ViewAppointments.html file contains an incorrect value in its 'for' attribute and is not read by screen readers.
This value should match the 'id' value for the field ("ReadingRoomID").
Bug# 18913
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 feature-specific web pages
-
Hyperlinks added to the cookie consent banner will fail color contrast requirements
If a hyperlink is added to the cookie consent banner, the default hyperlink color will not provide sufficient contrast against the banner's background color.
Note: Hyperlinks are not present in the banner by default.
Bug# 18486
0 votesreleased · AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) respondedReleased in Aeon v5.2 and v5.1.38 default web pages