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