Aeon Known Issues
92 results found
-
Duplicate Requests in Aeon by double clicking submit button
Users can submit duplicate requests through external requesting by rapidly clicking the submit button.
Bug# 4702
0 votes -
1 vote
-
Ampersands in Aeon usernames cause errors when using the Aeon web interface
When an Aeon user has an ampersand (&) in their username, this causes the following error to display in the Aeon web interface when that user attempts to view or edit a request: "You may only manage transactions that were created by you or for you by your proxy."
Bug# 24184
0 votes -
Appointment merge fields can cause errors when printing callslips for activities
If merge fields containing appointment-related data are added to the PrintCallslip.docx print template, the Aeon Client will throw an "Invalid Merge Field" error when attempting to print callslips for activities.
Bug# 23929
0 votes -
Requests may go to the wrong status when resubmitted from the Aeon web interface
When a request is resubmitted from the Aeon web interface either through cloning or by using the option to convert the request into a photoduplication request, the new request may not be put into the same status as that of the original request since Aeon will always set it to the first status it finds in the Queues table that uses the same StateCode as the original request's status.
Bug# 23628
0 votes -
Editing an appointment on the web forces manual confirmation
An appointment must be manually confirmed/re-confirmed after it is edited on the web, even when the option to auto-confirm appointments has been enabled for the reading room in the Aeon Customization Manager.
Bug# 24074
0 votes -
Byte arrays passed to .NET methods are converted to null due to an NLua bug
Byte arrays (often referred to as Byte[] in Microsoft's .NET documentation) passed from Lua to .NET methods are converted to null, causing those .NET methods to fail when included in addon code.
This is a known NLua bug present in the version of the NLua component used by the Aeon application, detailed here: https://github.com/NLua/NLua/issues/438.
Bug# 24019
0 votes -
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 votes -
Creating requests from file fails when custom fields are included
Creating requests from a spreadsheet file in the Aeon Client will fail when user-defined custom fields are included in the spreadsheet.
Bug# 23597
0 votes -
Applying service packages to photoduplication requests causes errors
Global service packages cannot be applied to photoduplication requests in the Aeon Client and will result in an error. Non-global service packages may also result in an error when applied.
Workaround: Apply a global service package to trigger the error, then apply a non-global service package to the request. This will allow the non-global service package to be applied. There is currently no workaround for applying global service packages to requests.
Aeon 5.2.
Bug# 23473
0 votes -
HTML5 client-side validation is not supported on the Saved Requests web page
Client-side HTML5 validation (e.g., the 'required' attribute) cannot be used for fields on the Saved Requests web page (ViewUserReviewRequests.html).
Bug# 22300
0 votes -
Color contrast issues on the Aeon Options form when using certain skins
The panel on the left of the Options form in the Aeon Client does not change color based on the Client skin selected and the links on the Resources tab have poor color contrast when using the Office 2016 Dark skin.
Bug# 22246
0 votes -
Email routing allows requests to be routed to incorrect state codes
Email routing allows activity requests to be routed into non-activity queues and internal routing controls will not be applied to move the request into the proper activity queue.
Bug# 21755
0 votes -
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 votes -
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 votes -
Cannot properly focus appointment calendar under certain conditions with keyboard controls
After typing a date manually into the Appointment Date text field on the Aeon web pages, pressing the TAB key will not properly bring focus on the calendar date picker and it will not be possible to operate the date picker with keyboard controls until pressing TAB key one more time and then SHIFT+TABing back into the calendar.
Bug# 19925
0 votes -
The Save for Later button on the EAD Request form may submit requests for processing
When the SubmitEadRequestsUpToRequestLimit customization key is set to Yes, using the Save for Later button on the EAD request form submits the request for processing instead of saving it for user review. As a result, requests can bypass the appointment requirement.
Bug# 21000
0 votes -
Aeon Client crashes on first load of addon from a network location
The Aeon Client will crash upon first startup if addons are loaded from a network location (i.e., when the My Documents folder on the workstation is hosted in a network location such as OneDrive).
Workaround: Open the My Documents folder in File Explorer before starting Aeon.
Bug# 20962
0 votes -
Aeon Options form displays incorrect version numbers for Staff and Customization Managers
The version numbers for the Staff and Customization Managers displayed on the Resources tab of the Aeon Options form in the Aeon Client are incorrect.
Bug# 19887
0 votes -
Duration of a booked appointment can't be shortened for reading rooms configured with a single seat
Attempting to shorten the duration of an existing appointment booked in a reading room configured with only a single seat on the web will return a "No appointment availability for this start and stop time" error.
Bug# 19849
0 votes