Aeon Known Issues
108 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 -
Routing a request to another site changes the request status to Request In Processing regardless of previous state When routing a request to another site (that is still visible by the existing view), the request will remain open.
The code for barSubItemRouteToSite_ItemClicked is routing to RequestInProcessing regardless of it the originalStatusRequestProcessing variable is -1 or something else. The route to RequestInProcessing in the else (i.e. when the request is still visible) should only happen if the originalStatusRequestProcessing is not equal to -1.
1 vote -
The Aeon web DLL may crash the app pool if it doesn't have permissions to the log file location. This was discovered in a very particular situation but is still good to account for.
1 vote -
Entering <#STATUS> in Status Line crashes the Aeon Server. Go to Aeon Customization Manager.
Edit the SLMainMenu customization key.
Change the value to <#STATUS>.
Log on to Aeon Web.1 vote -
The request form in the Aeon Client does not prompt to save changes when routing or selecting a next step. In the Aeon Client, open a request and modify a text field so that it is highlighted yellow to indicate pending changes.
Routing the request (both request status routing and photodup routing) or selecting a next step (other than Cancel) will immediately perform that action without prompting to save changes. The route options may prompt you to confirm that you want to route if you haven't checked the "Don't show this again" checkbox, but you won't be prompted to save pending changes.1 vote -
The Aeon DLL does not URL decode POST parameter names n InitializePostData, the DLL loops through the name/value pairs from the request content and decodes their values. However, it does not decode the field names. This isn't often a problem, but the Georgia Tech XSLT submits field names with a + character, which are getting encoded. When the EAD Request function tries to find field names using the identifier, they don't match because the + is still encoded in the field name. (We've since updated GT's XSLT to work around this).
1 vote -
XLS file extension has field constraints The mail merge data files need to be XLSX in order to overcome data length limitations in the XLS format.
1 vote -
1 vote
-
1 vote
-
EAD requests will fail web validation and be left in user review if there is a rule that requires the RequestLink field. Add a web validation rule for the "RequestLink" field with a validation rule of ".+" that will be applied to submitted EADRequests.
Submit an EAD request.
The new request will fail web validation and be left in Awaiting User Review.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