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

91 results found

  1. Reading rooms may allow overbooking when a full-day appointment is modified by staff

    If a reading room is configured to only allow full-day appointments (i.e., if the minimum and maximum appointment length are equivalent to the open hours duration), and one of the booked appointments for a particular day is manually adjusted by staff in the Aeon Client to a shorter duration, the reading room will allow an additional appointment to be booked that day, leading to potential overbooking.

    Bug# 16912

    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. Billing Account field label has incorrect 'for' attribute value

    The Billing Account field found in the PhotoduplicationRequest.html file, Generic Photoduplication request pages, and all corresponding edit pages for these files contains an incorrect value in the label element's 'for' attribute. This value should match the 'id' attribute value in the field's input element to avoid accessibility issues.

    Bug# 16833

    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. Selecting a "Request For" value may cause validation issues with billing fields on EADRequest.html

    If any billing fields (Format, Service Level, Shipping) are marked with the HTML5 'required' attribute on an EADRequest.html form that also uses a photoduplication request toggle option, selecting a "Request For" value may enable these fields when they are hidden by the toggle and cause the request to fail browser validation.

    Bug# 16440

    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 scheduling web calendar incorrectly shows the entire day as unavailable when a Reduced Availability exception is set

    When setting a Reduced Availability exception for a reading room in the Customization Manager's Appointment Scheduling tab, the appointment scheduling calendar on the web pages shows the entire day as unavailable, even if seats should be left after the reduced availability is set.

    Bug# 16362

    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. SLRequestLimitMet status line appears incorrectly on ViewUserReviewRequests

    When submitting a request that would meet or exceed the request limit on the ViewUserReviewRequests page, the SLRequestLimitMet status line text will appear but will be formatted incorrectly on the page. The user also will not be returned to the top of the page.

    Bug# 15801

    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. Status lines are missing from GenericRequestManuscript/MonographPhotodup when using Clone to Copy option

    Accessing the GenericRequestManuscriptPhotodup or GenericRequestMonographPhotodup request forms from the Clone to Copy option in the Actions menu or Transactions details page will cause the status line(s) not to appear on the page.

    Bug# 15485

    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. "Skip to main content" link remains invisible when focused on in certain browsers

    The "Skip to main content" link remains invisible when it is focused on using the keyboard in certain browsers including Chrome and Safari. The link appears as intended in Firefox.

    Bug #15254

    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. Edit option within the Transaction Menu can still be activated by keyboard when disabled

    When the Edit action is not allowed for a request, the button is visually disabled and made un-clickable within the Transaction Menu options but can still be activated using the keyboard, which takes the user back to the main menu page with a status message.

    Bug #15246

    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. <#OPTION> web tag cannot be used to automatically generate a list of checkbox options for CustomDropDown-type custom fields

    Using the <#OPTION> web tag to automatically generate a list of checkbox options for a group defined in the CustomDropDown table does not work if the group is a CustomDropDown-type field defined in the CustomFieldDefinitions table.

    Bug# 14532

    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. Cloning a photoduplication request in the web creates a non-photoduplication request

    Cloning a photoduplication request from the web interface will take the user to the default request form for a non-photoduplication request.

    Bug# 14459

    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. Small notes in Aeon can be easily missed by screen readers

    Small notes are located outside the label for fields on web forms where they are still accessible by screen readers but are not read out automatically like they would be if located inside the label. This can lead to screen readers skipping these notes unknowingly.

    Bug# 14420

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

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

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

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

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

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

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

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

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

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)