Skip to content

Aeon Known Issues

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

130 results found

  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

  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

  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

  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  ·  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

  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  ·  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

  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

  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  ·  Admin →
  10. Some characters are not correctly encoded when logging

    Some characters (such as those with diacritics) are not properly encoded in log files.

    Workaround: Add <encoding value="utf-8" /> under the <appender> element in the default log.config files.

    Bug# 21305

    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  ·  Admin Tools  ·  Admin →
  11. The Save for Later button on the EAD Request form may submit requests for processing

    When the SubmitEadRequestsUpToRequestLimit customization key is set to Yes, using the Save for Later button on the EAD request form submits the request for processing instead of saving it for user review. As a result, requests can bypass the appointment requirement.

    Bug# 21000

    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  ·  Admin →
  12. Aeon Client crashes on first load of addon from a network location

    The Aeon Client will crash upon first startup if addons are loaded from a network location (i.e., when the My Documents folder on the workstation is hosted in a network location such as OneDrive).

    Workaround: Open the My Documents folder in File Explorer before starting Aeon.

    Bug# 20962

    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  ·  Admin →
  13. Search box on ViewSearchResults.html has poor contrast in some browsers

    The border used for the search box on ViewSearchResults.html does not meet color contrast requirements in some browsers, including Safari.

    Bug# 19937

    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  ·  Admin →
  14. Aeon Options form displays incorrect version numbers for Staff and Customization Managers

    The version numbers for the Staff and Customization Managers displayed on the Resources tab of the Aeon Options form in the Aeon Client are incorrect.

    Bug# 19887

    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  ·  Admin →
  15. Duration of a booked appointment can't be shortened for reading rooms configured with a single seat

    Attempting to shorten the duration of an existing appointment booked in a reading room configured with only a single seat on the web will return a "No appointment availability for this start and stop time" error.

    Bug# 19849

    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  ·  Admin →
  16. Using the Enter key on the Saved Requests page selects all requests without announcing selection to screen readers

    Pressing Enter on the ScheduledDate field on the Saved Requests page (ViewUserReviewRequest.html) will checkmark select all requests on the page, without this change being announced to screen readers.

    Bug# 19801

    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  ·  Admin →
  17. Formatting error in Aeon Client log entry when user is set to away

    The following formatting error will appear in the Aeon Client log when a user signed into a reading room is set to away:

    INFO AtlasSystems.Aeon.FormDashboard - <log4net.Error>Exception during StringFormat: Input string was not in a correct format. <format>Setting user {)} to away.</format><args>{username}</args></log4net.Error>

    Bug# 19730

    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  ·  Admin →
  18. MinimumLeadDays behavior functions differently for appointments vs requests

    The MinimumLeadDays value for a reading room configured in the Aeon Customization Manager will consider not only the current date, but also the current time when calculating whether a request can still be submitted for an appointment, but will not consider the current time when making the same calculation for whether an appointment can still be scheduled in the room.

    This means that it is possible for an appointment to be scheduled for the room that would then not allow any requests to be associated with it.

    Bug# 19633

    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  ·  Admin →
  19. Email subject encoding can fail for non-ASCII characters

    Encoding for the subject line of an email sent from Aeon can fail if it contains non-ASCII characters.

    Workaround: If an email is bounced back for this issue, you can change the subject line of the email to remove any non-basic characters

    Bug# 19548

    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  ·  Admin →
  20. Requests are sometimes created with a NULL transaction status

    Requests in Aeon may sometimes be created with a blank/NULL transaction status that can then cause issues in the Aeon Client.

    Bug# 19511

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

Feedback and Knowledge Base