Aeon Known Issues
92 results found
-
Aeon API logs are not sufficiently detailed for troubleshooting certain web client issues
The Aeon API log does not contain sufficiently detailed logging statements for troubleshooting certain issues in the Aeon Web Client, for example, when a user's multifactor authentication configuration fails.
Bug# 28355
1 vote -
Date formats on the Aeon web interface are not displayed according to server locale settings
The Aeon web pages do not automatically use server locale settings to determine the format displayed for dates in the Aeon web interface and require manual code changes to adjust the format.
Bug# 28352
1 vote -
Researchers cannot be associated with requests created via the create request endpoint
Setting the RequestFor type to "Researcher" always returns a 500 error when attempting to create a request via the create request endpoint in the Aeon 6.0 Web API, regardless of whether or not the researcher username given is valid.
Bug# 27516
1 vote -
Appointment Status can be set to an invalid value using the appointment creation endpoint
The Appointment Status field can be set to any value using the appointment creation endpoint in the Aeon 6.0 Web API, which can lead to appointments created with invalid statuses.
Bug# 27514
1 vote -
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