When the Merge User form is opened, the height of the screen is too small and requires the user to scroll down to access some fields and all buttons. The form is also freely resizeable and does not have a minimum size or fixed size.
Bug# 118800 votes
Changing a user's username in the User Information Form causes an error if a Request Form is also open
If the Request Form and User Information Form are open at the same time in the Client, and the relevant user's username is changed in the User Information Form, an error will occur when switching back to the Request Form even if the User Information Form is still open.
Bug# 114030 votes
If the Aeon Client cannot find a DBC file on startup, it will correctly display an "Error Loading Database Settings" message, but will incorrectly continue trying to connect to the database after the error message is dismissed until this process eventually times out.
Bug# 111070 votes
Clicking "No" when prompted to edit activity notification e-mail still presents the e-mail for editing
When a user is added to an activity on the Activity form, a prompt asks if you would like to edit the notification being sent to the user. Clicking "No" presents the e-mail for editing the same as if "Yes" were clicked.
Bug# 109380 votes
In Template Edit Mode, open the Customization popup window on the Form Dashboard and save changes. Attempts to close the Aeon Client from will fail as the Customization window is unable to fully close.
Bug# 107920 votes
When scaling an item record's window down, the notes field becomes inaccessible, even when a note is present.
Bug# 103170 votes
When adding a transaction to a bundle, Aeon is creating an entry in the History table. The Entry column is limited to 255 characters, which throws an error if the bundle has a name that exceeds the limit.
Bug# 88060 votes
The custom search is displaying the correct, converted, time in the client; however, custom searches look for the unconverted UTC time from the database.
v5.0.3 and 188.8.131.52
Bug# 86890 votes
When submitting a Get Barcode request to the Aeon API with the ActiveOnly parameter set to True will prompt an error.
Bug# 83080 votes
Requests can be incorrectly associated with activities when browsing through a request list with mixed "RequestFor" associations. The form request isn't being initialized when switching between forms.
Bug# 57510 votes
Templates are occasionally being corrupted and resulting in a System.NullReferenceException error.
Bug# 36890 votes
Invalid data row displays when "Show Auto Filter Row" option is turned on0 votes
The password reset email template should be hidden in client email template options.0 votes
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
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