Aeon Known Issues
102 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 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 -
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 -
Using an nonexistent researcher username in the create request endpoint returns inaccurate validation messages
When using the create request endpoint, attempting to use a nonexistent researcher username as the reference when the RequestFor type is "researcher" returns inaccurate validation messages that do not make it clear that the user doesn't exist:
"{ResearcherUsername} is not a valid researcher username.",
"{ResearcherUsername} has been marked as an Anonymous user and cannot be a researcher username.",
"{ResearcherUsername} does not have a researcher association with {username}."Bug# 27504
0 votes -
Researchers cannot be associated with requests using the create request endpoint
When using the create request endpoint to create a request via the Aeon API, attempting to associate a researcher with the request via the RequestFor field will allow the request to be created, but Aeon will set the RequestFor field to the username associated with the request instead of to the researcher's username.
Bug# 27503
0 votes -
The Users/{username}/requests endpoint returns a 500 when setting activeOnly to 'true'
Setting activeOnly to 'true' when using the GET Users/{username}/requests endpoint to limit the requests returned for the user to only return those that are active results in a 500 error. Since the activeOnly parameter defaults to 'true', not setting a value for this parameter also returns a 500 error.
Bug# 27501
0 votes -
Activities cannot be associated with requests using the create request endpoint
When using the create request endpoint to create a request via the Aeon API, attempting to associate an activity with the request via the ActivityId field will always fail with the following validation message:
"User [username] is not associated with Activity [id]"
Bug# 27495
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 -
Duplicate reminder emails may be sent out for appointments
If a staff user manually sends the appointment reminder email from the Appointment form, the System Manager will not acknowledge that the email has already been sent and will still send its automated reminder email to the user, leading to duplicate reminder emails.
Bug# 27163
0 votes -
Null username error occurs when using the Clone to Current User option from a request list
In Aeon Client v5.2.4, using the Clone to Current User button from a queue's request list will result in a pop-up error stating "An exception occurred while attempting to clone the selected requests: Value cannot be null. Parameter name: Username"
Workaround: Open an individual request and use the Clone to Current User option from the Request form or select the Clone to New User option from the request list and then select the current user's username from the search.
Bug# 26834
0 votes -
Request callslips cannot be printed from an Activity record if custom fields are defined
Using the Print Callslips button on an Activity record results in an "invalid merge field" error if any custom fields are defined in the CustomFieldDefinitions table.
Bug# 26639
0 votes