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

89 results found

  1. "Approve Billing" button does not work on request pages

    Clicking the "Approve Billing" button from the "Actions" dropdown menu for a request or on the request's detailed information page will result in an error.

    Workaround: Use the "Approve Order" button on the Order Billing web page to approve the billing charges for the request.

    Bug# 14404

    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. Several incorrect links in Aeon action menus

    Two Aeon web action menus, includeTransactionMenu.html and DataRowDefaultRequest.html, have incorrect links for the following menu items:

    -Delete Item
    -Approve Estimate
    -Approve Billing

    The links for these items contain Form parameters where they should instead have Type parameters.

    Bug# 14398

    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 →

  3. Credit card webpages do not specify type attribute on button elements.

    The credit card payment webpages are missing the type="button" attribute on <button> elements, which can lead to issues when submitting the payment forms.

    Bug #14371

    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. The role="heading" attribute on top level <div> containers may cause issues for screen readers

    The role="heading" attribute on the <div> containers surrounding most web pages can cause strange behavior with screen readers depending on the content of the file.

    Bug# 13847

    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 →

  5. Certain activity requests trigger the appointment requirement on web pages

    Submitting a request for an activity through the web pages incorrectly triggers the appointment requirement for reading rooms requiring appointments. This issue does not occur for EAD and external requests.

    Bug# 13821

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

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

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

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

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

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

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

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

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

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

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

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

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

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

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

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

  20. 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 →
1 3 5

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)