Aeon Known Issues
107 results found
-
Aeon.log.config privileges are lost after update Additional user privileges previously added to the Aeon.log.config file are lost upon update and must be manually re-added. If the permissions are not re-added, this can potentially cause issues enabling debug logging in the Aeon Desktop Client.
Bug# 16914
1 vote -
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
-
Request queue grouping customizations do not load when saved to custom templates Customizations made to the request queue groupings on the Aeon Desktop Client home page using the layout template editor do not load for the custom layout template after the client application is closed.
Bug# 27694
0 votes -
Error occurs when creating appointments from a request using improper username casing If a transaction is created with a casing for the user's username that does not match the value used on the user record in the database, the following error will appear when creating appointments from the Request form for that transaction:
"Database Error
Error refreshing appointments:
Error in the PreferredName mapping
Some appointments could not be loaded. Please contact support."Bug# 27423
0 votes -
Appointments can be created using a casing for the username that does not match the user's record in the database If you search for a user in the Aeon Desktop Client using a casing for the user's username that does not match the value stored on the user's record in the database, new appointments created for that user from the User Information form will use the casing used to perform the search, which can subsequently cause errors in the client.
Bug# 27453
0 votes -
Requests can be created using a different casing for the username that does not match the user's record in the database If you search for a user in the Aeon Desktop Client using a casing for the user's username that does not match the value stored on the user's record in the database, new requests created for that user from the User Information form will use the casing used to perform the search, which subsequently causes errors when an appointment is associated with the request.
Bug# 27452
0 votes -
Duplicate reminder emails may be sent out for appointments If a staff user manually sends the appointment reminder email from the Appointment form, the System Manager will not acknowledge that the email has already been sent and will still send its automated reminder email to the user, leading to duplicate reminder emails.
Bug# 27163
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 -
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 -
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 -
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 -
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 -
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