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

12 results found

  1. Using an nonexistent researcher username in the create request endpoint returns inaccurate validation messages

    When using the create request endpoint, attempting to use a nonexistent researcher username as the reference when the RequestFor type is "researcher" returns inaccurate validation messages that do not make it clear that the user doesn't exist:
    "{ResearcherUsername} is not a valid researcher username.",
    "{ResearcherUsername} has been marked as an Anonymous user and cannot be a researcher username.",
    "{ResearcherUsername} does not have a researcher association with {username}."

    Bug# 27504

    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 →

  2. Researchers cannot be associated with requests using the create request endpoint

    When using the create request endpoint to create a request via the Aeon API, attempting to associate a researcher with the request via the RequestFor field will allow the request to be created, but Aeon will set the RequestFor field to the username associated with the request instead of to the researcher's username.

    Bug# 27503

    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 →

  3. The Users/{username}/requests endpoint returns a 500 when setting activeOnly to 'true'

    Setting activeOnly to 'true' when using the GET Users/{username}/requests endpoint to limit the requests returned for the user to only return those that are active results in a 500 error. Since the activeOnly parameter defaults to 'true', not setting a value for this parameter also returns a 500 error.

    Bug# 27501

    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 →

  4. Activities cannot be associated with requests using the create request endpoint

    When using the create request endpoint to create a request via the Aeon API, attempting to associate an activity with the request via the ActivityId field will always fail with the following validation message:

    "User [username] is not associated with Activity [id]"

    Bug# 27495

    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 →

  5. Request creation validation error message is inaccurate when the specified username doesn't exist.

    Creating a new request via the request creation endpoint that specifies a non-existent username will correctly return a validation error stating that the user does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid, even if valid values had been entered.

    Bug# 17649

    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 →

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

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

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

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

  10. Missing validation for activities in transactions

    In TransactionValidator, there is no validation for ensuring that ActivityId and ResearcherUsername are mutually exclusive or that the user is associated with the activity.

    Bug# 11562

    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. Aeon Web API reports invalid X-AEON-API-KEY header in logs unnecessarily

    The ApiKeyAuthenticationMiddleware layer is invoked unnecessarily for non-secure endpoints, resulting in invalid X-AEON-API-KEY header log statements.

    Bug# 10273

    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. TransactionValidator creates some redundant and/or incorrect error messages

    For example, validating a transaction without username results in the following:
    2x "username can't be empty"
    1x " is not a valid username"
    1x "user cannot be anonymous"

    Bug# 8889

    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 →

Aeon Known Issues

Categories

Feedback and Knowledge Base

(thinking…)