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 -
Status lines are missing from GenericRequestManuscript/MonographPhotodup when using Clone to Copy option
Accessing the GenericRequestManuscriptPhotodup or GenericRequestMonographPhotodup request forms from the Clone to Copy option in the Actions menu or Transactions details page will cause the status line(s) not to appear on the page.
Bug# 15485
0 votes -
Aeon System Manager will not pick up newly created custom queues until restarted
The Aeon System Manager caches the list of queues when started instead of checking and updating the list of queues periodically. This can lead to problems if custom queues are created for an addon as those newly created queues will not be available until the System Manager restarts.
Bug# 15370
0 votes -
Aeon CaiaSoft server addon may experience random connection timeouts
Version 1.1.2 of the Aeon CaiaSoft addon sometimes experiences random connection timeouts and leads to the addon no longer picking up the MonitoredStatus queue. The following error will then display in the System Manager logs:
"ERROR AtlasSystems.Addons.Aeon-CaiasoftRemoteStorage - An error occurred while processing the Caiasoft offsite request:The wait operation timed out"
Bug# 15344
0 votes -
Errors that prevent the appointment scheduling tool from loading also affect other areas of the Client
If an error prevents the appointment scheduling tool in the Client from loading, this will also cause other areas of the Client to become unusable until the underlying error is resolved.
Bug# 15330
0 votes -
Aeon Client becomes unusable if an appointment is created with an invalid username
If an appointment is created with an invalid username, this will prevent both the appointment scheduling tool and other parts of the Client such as the list of queues from loading.
Note: If you experience this bug, please submit a ticket for Atlas Support to resolve the underlying invalid data issues.
Bug# 15329
0 votes -
"Skip to main content" link remains invisible when focused on in certain browsers
The "Skip to main content" link remains invisible when it is focused on using the keyboard in certain browsers including Chrome and Safari. The link appears as intended in Firefox.
Bug #15254
0 votes -
Edit option within the Transaction Menu can still be activated by keyboard when disabled
When the Edit action is not allowed for a request, the button is visually disabled and made un-clickable within the Transaction Menu options but can still be activated using the keyboard, which takes the user back to the main menu page with a status message.
Bug #15246
0 votes -
Non-US regions cannot create entries in the ScheduledClosures table
Entries can not be added to the ScheduledClosures table for servers set to a non-US region.
Bug# 14878
0 votes -
Adding Appointment tab without any reading rooms configured crashes Aeon Client
Attempting to add the Appointment tab when customizing the Client layout will cause the Client to freeze/crash if no reading rooms have been configured in the Customization Manager.
Bug# 14767
0 votes -
Creating or deleting the only reading room configured for appointments while the Aeon Client is open causes errors
If the Aeon Client is opened at a time when no reading rooms are configured for appointments in the Customization Manager, creating a reading room with the Client still open and then attempting to refresh the Client results in the following error:
ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
A similar error occurs if the Client is opened at a time when one reading room is configured for appointments in the Customization Manager, and that reading room is deleted while the Client is still open:
ERROR AtlasSystems.Aeon.FormMain - Failed to process refresh request.
The Client will need to be…
0 votes -
Request callslips cannot be printed from an Activity record if any Transaction or Activity context-type custom fields are defined
Using the "Print Callslips for Requests Awaiting Processing" dropdown option from the "Print Callslips" button on an Activity record results in the following error if any custom fields are defined in the CustomFieldDefinitions table:
"An error occurred while attempting to print callslips (Ambiguous column name 'Activity ID'. "
Workaround: Print the callslips for Activity requests from the Awaiting Activity Processing queue or individually from each request record.
Bug# 14570
0 votes