Aeon Known Issues
92 results found
-
The Aeon installer does not support non-standard database user installations
A default database user and password are hard-coded into the installer defaults. When the DB update scripts try to grant permissions on new or updates tables, it will always try to grant them to 'aeon'. Need a way to configure the database user/password on install if different from hard-coded 'aeon'.
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 -
Password Reset link not converting when emailed from client
The password reset email template should be hidden in client email template options.
0 votes -
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