Aeon Known Issues
27 results found
-
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 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 -
Request queue grouping customizations do not load when saved to custom templates
Customizations made to the request queue groupings on the Aeon Desktop Client home page using the layout template editor do not load for the custom layout template after the client application is closed.
Bug# 27694
0 votes -
Error occurs when creating appointments from a request using improper username casing
If a transaction is created with a casing for the user's username that does not match the value used on the user record in the database, the following error will appear when creating appointments from the Request form for that transaction:
"Database Error
Error refreshing appointments:
Error in the PreferredName mapping
Some appointments could not be loaded. Please contact support."Bug# 27423
0 votes -
Appointments can be created using a casing for the username that does not match the user's record in the database
If you search for a user in the Aeon Desktop Client using a casing for the user's username that does not match the value stored on the user's record in the database, new appointments created for that user from the User Information form will use the casing used to perform the search, which can subsequently cause errors in the client.
Bug# 27453
0 votes -
Requests can be created using a different casing for the username that does not match the user's record in the database
If you search for a user in the Aeon Desktop Client using a casing for the user's username that does not match the value stored on the user's record in the database, new requests created for that user from the User Information form will use the casing used to perform the search, which subsequently causes errors when an appointment is associated with the request.
Bug# 27452
0 votes -
Invalid End Date can be entered on the Appointment form in Aeon Client
Manually confirming or unconfirming an appointment via the Appointment form in the Aeon Client will save any other changes made to the information on the form without enforcing data validation, which can lead to the following error loading appointments in the Client if an invalid End Date was entered and saved:
“Error refreshing appointments
Error in the End mapping
Some appointments could not be loaded. Please contact support.”Bug# 26376
0 votes -
Aeon Client crashes on first load of addon from a network location
The Aeon Client will crash upon first startup if addons are loaded from a network location (i.e., when the My Documents folder on the workstation is hosted in a network location such as OneDrive).
Workaround: Open the My Documents folder in File Explorer before starting Aeon.
Bug# 20962
0 votes -
Aeon Options form displays incorrect version numbers for Staff and Customization Managers
The version numbers for the Staff and Customization Managers displayed on the Resources tab of the Aeon Options form in the Aeon Client are incorrect.
Bug# 19887
0 votes -
Aeon Client will throw errors after idle period
If the Aeon Client has been idle for 30 minutes (for example, if the PC has entered sleep mode) the database connection used by the Client will close and throw the following error in the logs:
ERROR AtlasSystems.Configuration.Settings - A transport-level error has occurred when receiving results from the server.
Recommendation: Close down the Aeon Client before putting the computer to sleep or before leaving the computer for an extended period of time.
Bug# 16075
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 -
"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 -
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 -
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