Aeon Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  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

    under review  ·  0 comments  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  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

    under review  ·  0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  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

    under review  ·  0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  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  ·  Flag idea as inappropriate…  ·  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

    under review  ·  0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  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  ·  Flag idea as inappropriate…  ·  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

    under review  ·  2 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  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

    0 comments  ·  User Management  ·  Flag idea as inappropriate…  ·  Admin →
  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  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  11. The Web API request creation endpoint does not properly validate an activity association.

    If a request is created via the request creation endpoint, validation will not apply to enforce that the username on the request is associated with the specified activity ID.

    Bug# 13748

    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  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  16. "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)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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)

    We’ll send you updates on this idea

    0 comments  ·  Email  ·  Flag idea as inappropriate…  ·  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)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  19. Backslashes are not handled in the Aeon API for the username field

    If a username contains a backslash, it will not be handled/returned by the Aeon API.

    Bug# 12999

    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  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  20. "Item0" control in the Customize Layout menu can freeze or prevent the Client from closing.

    When editing template layouts on the main form of the Aeon Client, a layout control named "item0" may appear in the Customize Layout menu, and then will appear as "Root" if placed on the form. Dragging "item0" onto the form freezes the Client, and just opening the Customize Layout menu and seeing it prevents the Client from closing normally.

    These issues may occur in both Aeon 5.0 and 5.1.

    Bug# 12791

    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  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4

Feedback and Knowledge Base