Aeon Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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

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

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

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

    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 →
  5. 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

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

    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  ·  Printing  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. 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

    0 comments  ·  User Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    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. Force password reset option may fail in certain cases

    If the WebAuthType key is set to RemoteAuth in the Customization Manager and the force password reset option is toggled for a user using Aeon Authentication, the user will not be prompted to change their password upon logging in if the Aeon Authentication checkbox is not checked on the user record.

    Bug# 18390

    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 Interface  ·  Flag idea as inappropriate…  ·  Admin →
  11. Aeon System Manager does not refresh custom field definitions

    The Aeon System Manager caches custom field definitions defined in the Customization Manager and does not automatically refresh these when new entries are made.

    Bug# 18405

    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 Interface  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 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 →
  13. DataRow_ElectronicDelivery.html does not display File Size and Transaction Number

    The DataRow_ElectronicDelivery data row template does not display the associated file size and transaction number for requests.

    Bug# 18112

    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 →
  14. Default FAQ web page contains inaccurate information about cookies

    The default FAQ web page contains information about cookies stating that "the technology that we use sends a Session ID to be stored on your machine. You can refuse this cookie and still be able to use Aeon without any problems."

    This information is inaccurate as the Session ID cookie is essential for the Aeon web interface.

    Bug# 18264

    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. Appointment merge fields are blank when used in Transaction type email templates

    Appointment merge fields used in Transaction type email templates will appear blank when emails are generated for the template.

    Bug# 17993

    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 →
  16. ViewSearchResults.html contains an incorrect <u> tag

    The default ViewSearchResults.html web page contains an incorrect usage of the <u> tag to emphasize text where a <strong> tag should be used instead.

    Bug# 17985

    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 →
  17. Alma Primo Catalog addons do not display linked records

    The Aeon Alma Primo and Alma Primo VE Catalog addons may only import one call number for a record associated with multiple call number entries.

    Bug #17908

    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  ·  Addons  ·  Flag idea as inappropriate…  ·  Admin →
  18. Request creation validation error message is inaccurate when the specified username doesn't exist.

    Creating a new request via the request creation endpoint that specifies a non-existent username will correctly return a validation error stating that the user does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid, even if valid values had been entered.

    Bug# 17649

    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 →
  19. Navigation bar dropdown links do not meet contrast requirements in hover and focus states

    When a dropdown is opened from the main navigation bar and one of the containing links is hovered over or focused on, the default background color that appears does not meet WCAG contrast requirements against the default white background of the other links.

    Bug# 17643

    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 →
  20. Default button colors do not meet contrast requirements in certain cases

    The default button colors in certain states such as "active" and "hover" don't meet WCAG contrast requirements with commonly used default background colors like grey or white.

    Bug# 17604

    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 →
← Previous 1 3 4 5 6 7

Feedback and Knowledge Base