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 -
Duplicate classes in DataRow templates
A second class attribute was added for action items in the data row template. The contextual classes (e.g, menuClone) should be included in the earlier class definitions.
<a class="dropdown-item btn btn-light <#DATAROW field="RequestActionAllowed" name="Clone" disabledValue="d-none">" href="aeon.dll?Action=11&Form=32&Value=<#DATAROW field="TransactionNumber">" class="menuClone"><span aria-hidden="true" class="fas fa-copy text-primary"></span> Clone Request</a>
Bug# 7869
0 votes -
Date/Times moment.js inconsistency for convert times to browser time
Not all Date/Time fields are coded with the ISO8601 date.
Bug# 7710
0 votes -
Old jQuery code no longer required
Security scans may ping the following old commented out jQuery in the web pages that needs to be removed:
<!-- Optional JavaScript -->
<!-- jQuery first, then Popper.js, then Bootstrap JS -->
<!--<script src="https://code.jquery.com/jquery-3.4.1.slim.min.js" integrity="sha384-J6qa4849blE2+poT4WnyKhv5vZF5SrPo0iEjwBvKU7imGFAV0wwj1yYfoRSJoZ+n"crossorigin="anonymous"></script>-->Bug# 7573
0 votes -
The ViewAllRequests table and the View Requests By Tag table will always use the same export query
The DLL is using the same code for both the MainMenu.html and ViewRequestHistory.html tables and just uses an attribute to determine which table is show.
Bug# 1231
0 votes -
DLL request copy doesn't redirect user
Requesting a copy from the Item Checked Out or Available for Use status produces the correct status line, but doesn't redirect user to the edit photo duplication form, and also gives a status line about editing a request that has already been processed.
Bug# 7393
0 votes -
Duplication Orders do not appear on detailed information
When the ViewDetailedDefaultInformation page contains a blank field value is blank. As a result, the javascript designed to hide blank/empty fields doesn't show the entire div block.
Bug# 7337
0 votes -
Extra comments on ViewUserReviewRequests.html no longer relevant
ViewUserReviewRequests.html contains commented billing javascript that is unnecessary on the review page since it does not contain any billing information.
Bug# 7336
0 votes -
0 votes
-
Adding new lines to the web alerts breaks the alert
When adding carriage returns, it breaks the JSON parse.
Workaround: Use a <br> tag before starting a new line to ensure the alert will display properly.
v5.0
Bug# 72460 votes -
0 votes
-
Nonvalidate attribute not added to the cancel button
For pages with the required attribute and a cancel button, the nonvalidate attribute needs to be added to the cancel button in order to allow users to stop the request form and return to the main menu. The attribute also needs to be added to the Save Request button in the includerequestbuttons.html.
Bug# 6909
0 votes