Skip to content

Aeon Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

187 results found

  1. "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)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  2. 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)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Email  ·  Admin →

  3. Appointment Exception Dates sometimes may not be reflected in the web scheduling interface

    Appointment Exception Dates set in the Customization Manager for a reading room may not be reflected in the web scheduling interface in some cases but will display correctly in the Client.

    Bug# 13196

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  4. Appointment times sometimes display as UTC in the Client

    In some places in the Aeon Client, an appointment's start and end times display as UTC instead of being converted to the appropriate server time.

    Bug# 13160

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  5. Appointment scheduling calendars on the web may load slowly if the reading room is fully booked

    If a reading room is fully booked with appointments for a long period of time, the appointment scheduling calendar for that room on the web pages will take an excessive amount of time to load.

    Bug# 13107

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  6. Setting a custom field to a blank value can cause an internal error in the Aeon web DLL

    If a custom field (defined in the CustomFieldDefinitions table) is added to a form on the web as an optional field, submitting the form without a value for that field will return an error.

    Aeon v5.1

    Bug# 13020

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  7. 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)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  8. Some default EditGenericRequest forms are missing the required Transaction Number field

    The following Edit pages are missing a hidden TransactionNumber input, which is required for edit pages, and instead have a hidden TransactionLink input, which is not used on edit pages:
    -EditGenericRequestManuscriptPhotodup.html
    -EditGenericRequestMonographPhotodup.html

    Aeon 5.0/5.1 Default Web Pages

    Bug# 12899

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  9. Buttons not working on DataRow_ElectronicDelivery

    The View and Delete buttons, as well as the Details, View Item, and Cancel Request options from the Actions dropdown menu do not work on the DataRow_ElectronicDelivery template (used on the Electronically Delivered Items web page).

    Workaround: Click on the item title and use these options from the top of the item details page.

    Aeon 5.1

    Bug# 12824

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  10. The "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't return users to the logon menu

    Clicking the "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't allow users to stop the request form and return to the logon menu.

    Bug# 12668

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  11. The Web DLL does not properly validate researcher request links when submitting requests

    When submitting a request for a researcher, the DLL does not properly validate the proxy relationship between the user submitting the request and the selected researcher.

    Bug# 11699

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  12. Missing validation for activities in transactions

    In TransactionValidator, there is no validation for ensuring that ActivityId and ResearcherUsername are mutually exclusive or that the user is associated with the activity.

    Bug# 11562

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Admin →

  13. BillingAccountsVisible param tag does not work on PhotoduplicationRequest.html

    In the default Aeon web pages, the BillingAccountsVisible param tag on PhotoduplicationRequest.html does not properly hide the BillIng Account dropdown if Billing Accounts are disabled.

    Bug# 11533

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  14. Certain Transaction Emails do not use LocalInfo Table to populate the email's from address

    Generating a new email that is not based on a template from a request form in the client incorrectly populates the email's from address with the value in the EmailFromAddress customization key instead of the site's information entered in the LocalInfo table.

    Bug# 11000

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Email  ·  Admin →

  15. Transaction numbers do not pass to Touchnet

    Transaction numbers do not get to Touchnet due to an issue with ancillaryData handling.

    Bug# 10472

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Credit Card Payment Providers  ·  Admin →

  16. DataRow headers don't meet accessibility

    Once the h5 header is updated to h4, there is an empty header that breaks accessibility.

    Bug# 10178

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  17. There is no quoting style differentiation between HTML elements and DataRow elements

    Bug# 9774

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  18. Empty persist value string

    An empty string would be produced when the persist value drop-down in the atlasUtility.js due to the handling of the double-quotes.

    Bug# 9632

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  19. Not enough contract with the gray text in web pages

    The gray text used on some of the default pages doesn't meet contrast requirements for WCAG.

    Bug# 8005

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  20. Adding a transaction to a bundle with long name throws error

    When adding a transaction to a bundle, Aeon is creating an entry in the History table. The Entry column is limited to 255 characters, which throws an error if the bundle has a name that exceeds the limit.

    Bug# 8806

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →
1 2 3 5 7 8 9 10

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)