Aeon Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Duplicate Requests in Aeon by double clicking submit button

    Users can submit duplicate requests through external requesting by rapidly clicking the submit button.

    Bug# 4702

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  2. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  3. 400 Bad Request error handling is insufficient when using the request creation endpoint.

    When the request creation endpoint encounters a 400 Bad Request error, a generic error message is returned that does not contain sufficient detail describing the problem.

    Bug# 13747

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  5. The Web API caches some database values beyond the scope of a web request.

    When making changes to an Aeon configuration via the Customization Manager, the Web API will continue to use cached values in some instances beyond what is needed to process the current request until the app is restarted in IIS.

    Bug# 13746

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  6. Request creation validation error message is inaccurate when the specified researcher user doesn't exist.

    Creating a new request via the request creation endpoint that specifies a non-existent researcher will correctly return a validation error stating that the researcher's username does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid.

    Bug# 13743

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Custom fields of the 'Transaction' context type break API routing

    Using a custom field with the context type set to 'Transaction' in the CustomFieldDefinitions table breaks routing through the Aeon API and returns a 500 error.

    Aeon v5.1

    Bug# 13642

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  8. Unnecessary div element with id="username" on include_appointment_info.html

    The hidden field containing the username on includeappointmentinfo.html is not necessary as this information is obtained from the user's web session:

    <div id="username" hidden><#PARAM name="Username"></div>

    Bug# 13641

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  9. "Submit Request" button does not enforce the appointment requirement for saved requests

    Using the "Submit Request" button for a saved request via the Actions dropdown menu or from the Request Details page allows the user to submit a request without an appointment, even if appointments are required.

    Workaround: Comment out the Submit Request option on the DataRowDefaultRequest, RequestsInReviewDataRow/DataRowReviewRequest, and include_TransactionMenu pages.

    Bug# 13543

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  10. Email From Address and From Name values are not populated from template values when sending e-mails

    When sending templated emails from the Aeon Client, the From Address and From Name are set to the default values in the LocalInfo Table or EmailFromAddress/EmailFromName customization keys instead of the values specified in the email template.

    Bug# 13531

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Email  ·  Flag idea as inappropriate…  ·  Admin →
  11. Some button elements in the default web pages do not include a type attribute

    When a button does not explicitly declare a type in its code, it defaults to type="submit", which can sometimes lead to problems when processing transactions through a payment provider gateway.

    Workaround: The code for the buttons in includepaymentbuttons.html should include the attribute 'type="button"'

    Aeon v5.0.73/5.1 Default Web Pages

    Bug# 13028

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  13. "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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  14. EAD requests that skip order estimate can become uneditable

    An EAD request can become uneditable if the SkipOrderEstimates parameter is set to "Yes" and the request fails web validation. This is because SkipOrderEstimates will set the Photoduplication status of the request to "Awaiting Order Processing," which makes the request uneditable, even though the web validation failure sent the request to Awaiting User Review.

    Bug# 12663

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Alias Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Database  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4

Feedback and Knowledge Base