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
This was discovered in a very particular situation but is still good to account for.1 vote
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
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
The mail merge data files need to be XLSX in order to overcome data length limitations in the XLS format.1 vote
Merging users in a common user database configuration cannot update user requests across site databases1 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
Users can submit duplicate requests through external requesting by rapidly clicking the submit button.
Bug# 47020 votes
When adding a transaction to a bundle, Aeon is creating an entry in the History table. The Entry column is limited to 255 characters, which throws an error if the bundle has a name that exceeds the limit.
Bug# 88060 votes
When a user submits a request, the request is created as expected after logging in. Then, if the user clicks the refresh button in their browser, a duplicate request is submitted.
If the user is already logged in and attempts to refresh after submitting the request, I get the: "This form has already been submitted. Duplicate request not created." error as expected.
Bug# 88260 votes
For example, validating a transaction without username results in the following:
2x "username can't be empty"
1x " is not a valid username"
1x "user cannot be anonymous"
Bug# 88890 votes
The custom search is displaying the correct, converted, time in the client; however, custom searches look for the unconverted UTC time from the database.
v5.0.3 and 126.96.36.199
Bug# 86890 votes
When creating a user with an expired password and resetting their password via an email reset link, the user will immediately be presented with another password change form (because their previous password was expired).
Bug# 86870 votes
The default pages do not currently support special date formats such as ISO8601 for the ActivityStatusDate. When adding the ISO8601 to the code, the pages are preventing the UTC time from being converted to the user's local timezone.
Bug# 86110 votes
When submitting a new request through the web and manually typing in the date, the date will be accepted regardless of if it is a blackout date. The blackout date will be unavailable if you attempt to select it from the calendar.
Workaround: Disable the manual entry to the date field by adding the below code to the scheduled_date.js:
// Disable manual entry for date
Bug# 83640 votes
When submitting a Get Barcode request to the Aeon API with the ActiveOnly parameter set to True will prompt an error.
Bug# 83080 votes