Skip to content

Aeon Known Issues

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

6 results found

  1. Aeon System Manager does not refresh custom field definitions

    The Aeon System Manager caches custom field definitions defined in the Customization Manager and does not automatically refresh these when new entries are made.

    Bug# 18405

    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 Interface  ·  Admin →
  2. 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

  3. Changing a staff user's password sets "StaffPasswords.ModifiedBy" to the staff user's username

    The "Modified By" field is being set to the username of the Staff User whose password was changed instead of the username of the logged-in user when resetting a staff user's password.

    Bug# 4258

    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 Interface  ·  Admin →
  4. Activity Grid not saving grid changes/customizations

    The activity grid in Aeon 5.0 doesn't save any changes made to the layout after the client has been restarted.

    v5.0
    Bug# 4449

    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 Interface  ·  Admin →
  5. Date values export as plain text instead of date values when exporting transactions from the grid to Excel

    In Aeon 3.9 the date values would be exported as a date value which you could then sort chronologically. In Aeon 4.0, the new values only allow you to sort them alphabetically unless you manually remove the AM/PM text from all the cells and change the format of the cells to a date format.

    v4.0 & 4.1 & 5.0
    Bug# 4432

    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 Interface  ·  Admin →
  6. Error logging in when StaffPreviousPasswordCount Customization Key is less than one

    When you set the StaffPreviousPassword to 0, Aeon should default to checking a minimum of 4 unique passwords before an old password can be reused. Instead, a bug is causing the system to read the 0 as a null value, which in turn made it to unable to recognize any passwords. Until the bug is fixed, do not set the default value to 0.

    v4.1
    Bug#4238

    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

Feedback and Knowledge Base