Aeon Known Issues
102 results found
-
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 -
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 -
Using an nonexistent researcher username in the create request endpoint returns inaccurate validation messages
When using the create request endpoint, attempting to use a nonexistent researcher username as the reference when the RequestFor type is "researcher" returns inaccurate validation messages that do not make it clear that the user doesn't exist:
"{ResearcherUsername} is not a valid researcher username.",
"{ResearcherUsername} has been marked as an Anonymous user and cannot be a researcher username.",
"{ResearcherUsername} does not have a researcher association with {username}."Bug# 27504
0 votes -
Researchers cannot be associated with requests using the create request endpoint
When using the create request endpoint to create a request via the Aeon API, attempting to associate a researcher with the request via the RequestFor field will allow the request to be created, but Aeon will set the RequestFor field to the username associated with the request instead of to the researcher's username.
Bug# 27503
0 votes -
The Users/{username}/requests endpoint returns a 500 when setting activeOnly to 'true'
Setting activeOnly to 'true' when using the GET Users/{username}/requests endpoint to limit the requests returned for the user to only return those that are active results in a 500 error. Since the activeOnly parameter defaults to 'true', not setting a value for this parameter also returns a 500 error.
Bug# 27501
0 votes -
Activities cannot be associated with requests using the create request endpoint
When using the create request endpoint to create a request via the Aeon API, attempting to associate an activity with the request via the ActivityId field will always fail with the following validation message:
"User [username] is not associated with Activity [id]"
Bug# 27495
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 -
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