Aeon Known Issues
92 results found
-
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 -
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 -
Screenshots submitted through the Feedback form are clipped incorrectly on high-DPI monitors
Screenshots submitted through the Feedback form of the Client will be clipped incorrectly on high-DPI monitors.
Bug# 14333
0 votes -
Setting private mode in the Chromium browser does not clear cache upon closing the browser.
Creating an instance of the Chromium browser in an addon with privateMode set to true persists the cache between browser instances and also between users.
Aeon v5.1.
Bug# 13852
0 votes -
The Web API request creation endpoint does not properly validate an activity association.
If a request is created via the request creation endpoint, validation will not apply to enforce that the username on the request is associated with the specified activity ID.
Bug# 13748
0 votes -
Backslashes are not handled in the Aeon API for the username field
If a username contains a backslash, it will not be handled/returned by the Aeon API.
Bug# 12999
0 votes -
"Item0" control in the Customize Layout menu can freeze or prevent the Client from closing.
When editing template layouts on the main form of the Aeon Client, a layout control named "item0" may appear in the Customize Layout menu, and then will appear as "Root" if placed on the form. Dragging "item0" onto the form freezes the Client, and just opening the Customize Layout menu and seeing it prevents the Client from closing normally.
These issues may occur in both Aeon 5.0 and 5.1.
Bug# 12791
0 votes -
Routing a request to another site from the Request form and then opening it from the Request list causes an error
Routing a request to a site outside of the current database view from the Request form does not refresh the Request list in the Client, and leads to an error in the logs stating "A thread exception has occurred" when trying to open that request from the unrefreshed list.
Bug# 12625
0 votes -
Associating a request at the "Request in Processing" status with an activity causes an error
If a request is at the "Request in Processing" status and is not associated with an activity, associating it with one via the Request form and then saving gives an error in the logs stating "A thread exception has occurred."
Bug# 12624
0 votes -
The transactions grid on the Appointment form does not display field customizations
The grid displaying associated requests on the Appointment form does not apply field customizations.
Aeon 5.1
Bug# 12618
0 votes -
Errors saving DBC on Windows 8/Server 2012
When using Windows Server 2012, an error occurs when saving a DBC file with the Save button in SQL Alias Manager.
Bug# 12126
0 votes -
When clearing users, changing the username of a user on the similar users list does not refresh the list
When clearing users, changing the username of a user on the list of similar users does not refresh the list. Clicking on a user who has had their username changed in the unrefreshed list causes an error and opens a blank user info form.
Bug# 12249
0 votes -
DBC passwords containing special characters cause database connection errors
DBC passwords containing some special characters (such as semicolons) lead to errors when the DLL attempts to connect to the database.
Bug# 12295
0 votes -
DLL incorrectly displays detailed error information to users
When an error is encountered, the Aeon Web DLL is surfacing detailed error information that should not be visible to end-users.
Bug# 12289
0 votes -
The Merge User form is too small
When the Merge User form is opened, the height of the screen is too small and requires the user to scroll down to access some fields and all buttons. The form is also freely resizeable and does not have a minimum size or fixed size.
Bug# 11880
0 votes -
Changing a user's username in the User Information Form causes an error if a Request Form is also open
If the Request Form and User Information Form are open at the same time in the Client, and the relevant user's username is changed in the User Information Form, an error will occur when switching back to the Request Form even if the User Information Form is still open.
Bug# 11403
0 votes -
Client still tries to connect to the database when it can't find a DBC file
If the Aeon Client cannot find a DBC file on startup, it will correctly display an "Error Loading Database Settings" message, but will incorrectly continue trying to connect to the database after the error message is dismissed until this process eventually times out.
Bug# 11107
0 votes -
Clicking "No" when prompted to edit activity notification e-mail still presents the e-mail for editing
When a user is added to an activity on the Activity form, a prompt asks if you would like to edit the notification being sent to the user. Clicking "No" presents the e-mail for editing the same as if "Yes" were clicked.
Bug# 10938
0 votes -
Customization window on Form Dashboard prevents closing the Client
In Template Edit Mode, open the Customization popup window on the Form Dashboard and save changes. Attempts to close the Aeon Client from will fail as the Customization window is unable to fully close.
Bug# 10792
0 votes -
Cybersource payment confirmations may not be processed correctly
The "Unable to process payment at this time. Please contact library staff if this problem persists. Response signature provided from CyberSource payment provider could not be confirmed." error occurs when a user makes a payment in CyberSource but closes out before successfully navigating back to Aeon.
Bug# 9361
0 votes