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

202 results found

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

  2. OtherHeaders property used on SMTP.config does not function as expected.

    The OtherHeaders property used on SMTP.config is set initially but is then overwritten and will not function as expected, which can lead to issues with configuring emails.

    Bug# 14378

    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  ·  Admin Tools  ·  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. Filtering/sorting requests by appointment start or stop time breaks results

    Trying to filter or sort requests associated with an appointment by either their start or stop time in the grid view breaks the results and changes the grid to a blank page with an orange X over it.

    Bug# 14166

    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. Cannot select the current date when adding attendance count to an activity

    Selecting the current date when adding attendance count to an activity throws an error stating that the date cannot be in the future.

    Aeon v5.1

    Bug# 13930

    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 →

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

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

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

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Admin →

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

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Admin →

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

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Admin →

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

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Admin →

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

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

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

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

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

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

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

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

  20. 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 →
1 2 … 5 7 9 10 11

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)