Aeon Known Issues
-
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 -
The Web DLL does not properly validate researcher request links when submitting requests
When submitting a request for a researcher, the DLL does not properly validate the proxy relationship between the user submitting the request and the selected researcher.
Bug# 11699
0 votes -
Missing validation for activities in transactions
In TransactionValidator, there is no validation for ensuring that ActivityId and ResearcherUsername are mutually exclusive or that the user is associated with the activity.
Bug# 11562
0 votes -
BillingAccountsVisible param tag does not work on PhotoduplicationRequest.html
In the default Aeon web pages, the BillingAccountsVisible param tag on PhotoduplicationRequest.html does not properly hide the BillIng Account dropdown if Billing Accounts are disabled.
Bug# 11533
0 votes -
Changing a user's username in the User Information Form causes an error if a Request Form is also open
If the Request Form and User Information Form are open at the same time in the Client, and the relevant user's username is changed in the User Information Form, an error will occur when switching back to the Request Form even if the User Information Form is still open.
Bug# 11403
0 votes -
Client still tries to connect to the database when it can't find a DBC file
If the Aeon Client cannot find a DBC file on startup, it will correctly display an "Error Loading Database Settings" message, but will incorrectly continue trying to connect to the database after the error message is dismissed until this process eventually times out.
Bug# 11107
0 votes -
Certain Transaction Emails do not use LocalInfo Table to populate the email's from address
Generating a new email that is not based on a template from a request form in the client incorrectly populates the email's from address with the value in the EmailFromAddress customization key instead of the site's information entered in the LocalInfo table.
Bug# 11000
0 votes -
Clicking "No" when prompted to edit activity notification e-mail still presents the e-mail for editing
When a user is added to an activity on the Activity form, a prompt asks if you would like to edit the notification being sent to the user. Clicking "No" presents the e-mail for editing the same as if "Yes" were clicked.
Bug# 10938
0 votes -
Customization window on Form Dashboard prevents closing the Client
In Template Edit Mode, open the Customization popup window on the Form Dashboard and save changes. Attempts to close the Aeon Client from will fail as the Customization window is unable to fully close.
Bug# 10792
0 votes -
Transaction numbers do not pass to Touchnet
Transaction numbers do not get to Touchnet due to an issue with ancillaryData handling.
Bug# 10472
0 votes -
Cybersource payment confirmations may not be processed correctly
The "Unable to process payment at this time. Please contact library staff if this problem persists. Response signature provided from CyberSource payment provider could not be confirmed." error occurs when a user makes a payment in CyberSource but closes out before successfully navigating back to Aeon.
Bug# 9361
0 votes -
Resizing prevents access to Notes in Aeon Item record
When scaling an item record's window down, the notes field becomes inaccessible, even when a note is present.
Bug# 10317
0 votes