Aeon Known Issues
43 results found
-
Session timeout issues on the ArchivalRequest form Once a user's session expires, the Submit button on ArchivalRequest does nothing if clicked on. It should redirect to the Logon form for the user to re-authenticate and then submit after re-authentication.
Also after session expiration, the "Cancel - Return to Main Menu" and "Save Request for Later" buttons redirects to the Logon form but entering credentials does nothing except reload the logon form. There is no way to log back in.
Bug# 31680
1 vote -
Session timeout issue on Saved Requests page Submitting a request from the Saved Requests page using the "Submit Information" button does not work once the session has timed out. The "Cancel Requests" button does work by redirecting to the Logon page and cancelling after re-authentication.
The behavior should be consistent to allow batch submission after session timeout.
Bug# 31679
1 vote -
TransactionStatus for RequestCopy (turning a request into an order) should advance When a user initiates the Request Copy function the request status should move to Awaiting Request Processing if it is in a saved request state. Currently, the status stays at Awaiting User Review.
Bug# 31643
1 vote -
Issue with session timeouts and appointment creation in web interface A user cannot finish creating new appointments once their session has timed out. If they try clicking the "Create Appointment" button, nothing happens. There is no redirect to the login page or other way for the user to complete that action without losing progress.
Bug# 31388
1 vote -
Phototoggle on EADRequest does not handle multiple requests The grouping functionality is not correcting being called on submittal to enable multiple requests.
Bug# 30721
1 vote -
Submitting the ExpiredUsers form does not set custom field values When submitting ExpiredUsers when a custom field is present, the custom field value will not update.
Bug# 30607
1 vote -
Photodup requests can become associated with an activity or appointment A photoduplication request can become associated with an appointment or activity in the situation where there is lack of a matching EditPhotodup form, since it then defaults to the edit page meant for regular requests and adds the photoduplication fields via the <#INCLUDE> tag present on the page. Transaction status and photoduplication status stay the same.
Bug# 30398
1 vote -
Issues with hardcoded Site options in web interface The ViewAppointments.html page does not currently handle hardcoded options in the Site field dropdown correctly, unlike request forms with appointments
Hardcoded Site dropdown fields can fail on edit forms when using appointments.
Bug# 30377
1 vote -
Item detail information in web showing encoding for ampersand HTML encoding is showing for the ampersand on the item detail pages
Bug# 30262
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 -
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
-
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 -
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 -
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 -
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 -
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 -
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 -
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