Aeon Known Issues
35 results found
-
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 -
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 -
Typo of the spelling "Request" in the templates folder
Typo of the spelling "Request" in the templates folder:
DataRowOrderEstimate
DataRowOrderBilling
DataRowElec
DataRowDefaultRequest
DataRowCreditCardOrder
DataRowDefaultActivityBug# 6901
0 votes -
include_header_request.html page is being installed even though it is no longer used as a default
The includeheaderrequest.html page is a web file that pre-dates Aeon 5.0. It is no longer used in any default Aeon 5.0 pages. The file should be removed.
Bug# 6026
0 votes -
Determining transaction ownership in DataRepeaters in not efficient
The check for UserControlsTransaction is loading the transaction query each time to determine ownership.
Bug# 4493
0 votes -
Researcher Re-Submitted Request After Processing
Some web users have been able to re-submit requests after they are placed in statuses that should not allow re-submission.
0 votes -
Database saves entered blank lines before ItemTitle on web form
Using the web request form, users can enter a new/blank line(s) before the item's title. That character is saved in the database causing the ItemTitle Field to appear blank in the client's grid view, and missing in the email templates when the ItemTitle tag is used.
0 votes -
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 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 -
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