Aeon Known Issues
41 results found
-
Appointment name can't be edited in the v5.1.8 Aeon Client
Edits to the name of an appointment will not be saved when attempting to make changes in the Aeon Client.
Note that this issue only affects Aeon Client v5.1.8.
Bug# 19121
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Routing from Client addons does not work if the target queue is under a menu group.
Set up a Client addon that will route a request to a specific queue.
In Customization Manager, assign that queue a Menu Group name so that it's under a submenu in the Route button dropdown.
When the addon tries to route, it will report an error indicating the queue doesn't exist.1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Aeon 4.0.1
-
Aeon forms can be shrunk a lot smaller than they should be able to
Present in: Main form, Activity form, Request form, User form.
1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in Aeon 4.0.1
-
BillingCategory combobox is not anchored on user billing form
If you open the User form and resize it, the Billing Category dropdown does not reposition itself.
1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in 4.0
-
Date fields export as UTC when exporting data from a grid in the Aeon client
Repro Steps
1. Open the Aeon client and navigate to a grid that has date fields
2. Right click and Export the grid
3. If you view the grid in Excel, the date columns show as UTC, instead of showing as the server time1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in Aeon 4.0.1
-
Field customizations will not hide duplicate field names in grids.
Repro Steps
1. Assign a staff template to a user in Staff Manager and add a field customization rule to hide the username field.
2. Perform a request search from the main form.
3. Although the 'Username' field will be hidden, there will be a "Username1" field which is not.1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in Aeon 4.0
-
Field customizations may not apply on some grids.
Field customizations and layout customizations may conflict on grids depending on which order they are applied. To reproduce:
1. Assign a layout template to a staff user in Staff Manager, but make sure there are no field customization rules yet.
2. Open the Client with that staff user.
3. Perform a basic user search from the main menu.
4. On the list of user search results, choose a field such as Username and drag it to a different position.
5. Close the Client, saving layout changes.
6. In Staff Manager, add a field customization to hide the field you selected.…1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in Aeon 4.0
-
Searching for user details in the 'Proxies' tab of the Client user form will cause an error if the search terms include an apostrophe.
Repro Steps
Open a user form and click on the proxies tab.
Perform a search using a single apostophe in the username or name field.
An application-level exception will be raised.1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in 4.0
-
Client ignoring confirm exit dialog response when activity forms open
Repro Steps
Open an activity form in the client. Do not make any pending changes to the activity record
Close the main client form
Choose "No" on the Confirm Exit promptThe client will close .
1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in 4.0
-
Bundle search does not work when bundle field is NULL
This happens because of a like comparison of the string '%%' against a NULL value.
This is going to be resolved with the ability to edit bundle name and description after creation feature.
1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in 4.0
-
Identical Username - unhandled exception caused by primary key violation
One user can cause another to receive an error while creating a new user.
- Open 2 Aeon client windows.
- Navigate to the add new user form in both windows.
- Give both new users the same user ID.
- Save one, type a password, do not click OK.
- Save the other, give them a password, and click OK.
- Click OK on the password dialog created in step 4.
1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released
-
Error occurs when using "Request For" control when not associated with any requests
Steps to reproduce:
- Open a user form for a user that has no requests.
- Switch to the requests tab
- Click the Request For ribbon button.
- Either double click with no selected researchers or activities or choose to clear an association.
Data Error: Incorrect syntax near ')'
1 votereleased ·AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released
-
Formatting error in Aeon Client log entry when user is set to away
The following formatting error will appear in the Aeon Client log when a user signed into a reading room is set to away:
INFO AtlasSystems.Aeon.FormDashboard - <log4net.Error>Exception during StringFormat: Input string was not in a correct format. <format>Setting user {)} to away.</format><args>{username}</args></log4net.Error>
Bug# 19730
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Aeon Client Options form controls are incorrectly aligned
The controls located within the Aeon Options form in the Aeon Client are not aligned properly within the borders of each section of options on this screen.
Bug# 18418
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Aeon Client dashboard does not properly handle database connection errors
The Aeon Client dashboard will correctly catch database connection errors, but will then attempt to use the connection, which causes an additional error.
Bug# 17093
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Multithreading error during Aeon Client dashboard refresh
The following error can sometimes occur in the Aeon Client logs upon a dashboard refresh and may lead to Client slowness:
ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
System.InvalidOperationException: A multithreading issue is detected. The DevExpress.Data.CurrencyDataController.DisableThreadingProblemsDetection option allows you to disable the exception, but it does not resolve the underlying issue.
ManagedThreadId: 20; ThreadName: ''Bug# 16762
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Custom fields are highlighted yellow when added to a custom tab group in the Aeon Client
Custom fields defined in the Aeon Customization Manager's CustomFieldDefinitions table will display highlighted yellow if added to a custom tab group created on a form in the Aeon Client.
Bug# 15993
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Leaving FutureRoutingDays customization key blank causes errors
If the FutureRoutingDays customization key value is blank, the following error will occur when attempting to import requests from file:
ERROR AtlasSystems.Aeon.FormCreateRequests - An error occurred when creating the requests: Input string was not in a correct format.
Bug# 15791
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
Appointments can't be saved using the request form's appointment control if system time zone is UTC
If the system time zone is set to UTC, the following error is logged when attempting to save an appointment with the appointment control on the request form:
ERROR AtlasSystems.Aeon.Program - A thread exception has occurred.
System.ArgumentException: The conversion could not be completed because the supplied DateTime did not have the Kind property set correctly. For example, when the Kind property is DateTimeKind.Local, the source time zone must be TimeZoneInfo.Local.Note: This only applies to the system time zone labeled simply as "Coordinated Universal Time," and not other time zones with no UTC offset. It does not occur when both…
0 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2
-
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 votesreleased ·AdminBrittany de Gail (Technical Writer/Content Developer, Atlas Systems, Inc.) responded
Released in Aeon v5.2