Aeon Known Issues
35 results found
-
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 -
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 -
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 -
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 -
Appointment scheduling web calendar is not properly formatted for screen reader navigation
The HTML tables used to format the appointment scheduling calendar on the web are improperly formatted and cause navigation issues for screen reader users.
Backlog# 18519
0 votes -
Using the <#OPTION> tag with a CustomDropDown group requires the group name to match the target field name
CustomDropDown group selections displayed on web forms using the <#OPTION> tag can only be saved to a field with a name matching that of the CustomDropDown group name.
Bug# 17407
0 votes -
Checkboxes generated with the Aeon <#OPTION> tag will save data in an incorrect format
Using the <#OPTION> tag to generate a group of checkbox selections for a CustomDropDown group on the web will cause the data selected to be saved with a comma prepended to each value.
Bug# 17406
0 votes -
Submission of XML/HTML tags in EAD requests will cause errors
If POSTed data from an EAD request contains an XML/HTML tag, the Aeon server will respond with a 500 error message.
Bug# 17275
0 votes -
ReturnLink fields are not sent during HTTP redirects
ReturnLink parameters are not sent by the Aeon Web DLL during the HTTP redirect process.
Bug# 16722
0 votes -
Issues may be caused when DLL attempts to match form values to regular expressions used for web validation
Issues can sometimes occur in the Web DLL when matching submitted form data to certain regular expressions defined in the WebValidation table.
Bug# 16111
0 votes -
DLL incorrectly displays detailed error information to users
When an error is encountered, the Aeon Web DLL is surfacing detailed error information that should not be visible to end-users.
Bug# 12289
0 votes -
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 -
Blocked dates can be bypassed by manually entering date
When submitting a new request through the web and manually typing in the date, the date will be accepted regardless of if it is a blackout date. The blackout date will be unavailable if you attempt to select it from the calendar.
Workaround: Disable the manual entry to the date field by adding the below code to the scheduled_date.js:
// Disable manual entry for date
scheduledDate.attr("readonly", true);Bug# 8364
0 votes