Aeon Known Issues
94 results found
-
Null username error occurs when using the Clone to Current User option from a request list
In Aeon Client v5.2.4, using the Clone to Current User button from a queue's request list will result in a pop-up error stating "An exception occurred while attempting to clone the selected requests: Value cannot be null. Parameter name: Username"
Workaround: Open an individual request and use the Clone to Current User option from the Request form or select the Clone to New User option from the request list and then select the current user's username from the search.
Bug# 26834
0 votes -
Request callslips cannot be printed from an Activity record if custom fields are defined
Using the Print Callslips button on an Activity record results in an "invalid merge field" error if any custom fields are defined in the CustomFieldDefinitions table.
Bug# 26639
0 votes -
Aeon.dll can get caught in a logon loop when submitting external requests
When external requests are submitted to Aeon with the action specified by query parameters (Action=11&Type=200), this will lead to a logon loop on logon2.html when the user does not have an active web session.
As a workaround to this issue, there is a new recommended approach for submitting external requests that uses the AeonForm field to specify the ExternalRequest and does not use the action query parameters causing the logon loop issue. For details on implementing the new approach, see the "Aeon Form Fields" section of the External Request Endpoint documentation.
Bug# 26336
0 votes -
System alerts in Aeon Client do not check for emails with the Appointment EmailType
Emails with the EmailType “Appointment” do not display in the System section of the Aeon Client dashboard.
Bug# 26272
0 votes -
Aeon API can experience connection exhaustion with the database
The Aeon API can sometimes experience connection exhaustion with the database, which can lead to 500 errors in the API.
Bug# 26032
0 votes -
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 votes -
The Atlas Authentication Portal is missing the log configuration file
The Atlas Authentication Portal has support for logging, but is not currently distributed with the necessary App_Data folder and log.config file to enable logging.
Bug# 26220
0 votes -
Z39.50 may duplicate item records for holdings
Z39.50 will pull in any hardcoded holding elements in the XML for a holding record, which can cause the first item listed in the record to be duplicated in Aeon.
Bug# 25965
0 votes -
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 -
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 -
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