92 results found
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
This was discovered in a very particular situation but is still good to account for.1 vote
Go to Aeon Customization Manager.
Edit the SLMainMenu customization key.
Change the value to <#STATUS>.
Log on to Aeon Web.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
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
The mail merge data files need to be XLSX in order to overcome data length limitations in the XLS format.1 vote
Merging users in a common user database configuration cannot update user requests across site databases1 vote
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
When an Aeon user has an ampersand (&) in their username, this causes the following error to display in the Aeon web interface when that user attempts to view or edit a request: "You may only manage transactions that were created by you or for you by your proxy."
Bug# 241840 votes
If merge fields containing appointment-related data are added to the PrintCallslip.docx print template, the Aeon Client will throw an "Invalid Merge Field" error when attempting to print callslips for activities.
Bug# 239290 votes
When a request is resubmitted from the Aeon web interface either through cloning or by using the option to convert the request into a photoduplication request, the new request may not be put into the same status as that of the original request since Aeon will always set it to the first status it finds in the Queues table that uses the same StateCode as the original request's status.
Bug# 236280 votes
An appointment must be manually confirmed/re-confirmed after it is edited on the web, even when the option to auto-confirm appointments has been enabled for the reading room in the Aeon Customization Manager.
Bug# 240740 votes
Byte arrays (often referred to as Byte in Microsoft's .NET documentation) passed from Lua to .NET methods are converted to null, causing those .NET methods to fail when included in addon code.
This is a known NLua bug present in the version of the NLua component used by the Aeon application, detailed here: https://github.com/NLua/NLua/issues/438.
Bug# 240190 votes
System information from the LocalInfo table is not properly imported into the From field on email templates
System tags used to import information from the LocalInfo table (e.g., <#System.GeneralEMailAddress>) will not import the correct value when configured in the From field on email templates.
Bug# 237640 votes
Creating requests from a spreadsheet file in the Aeon Client will fail when user-defined custom fields are included in the spreadsheet.
Bug# 235970 votes
Global service packages cannot be applied to photoduplication requests in the Aeon Client and will result in an error. Non-global service packages may also result in an error when applied.
Workaround: Apply a global service package to trigger the error, then apply a non-global service package to the request. This will allow the non-global service package to be applied. There is currently no workaround for applying global service packages to requests.
Bug# 234730 votes
Client-side HTML5 validation (e.g., the 'required' attribute) cannot be used for fields on the Saved Requests web page (ViewUserReviewRequests.html).
Bug# 223000 votes
The panel on the left of the Options form in the Aeon Client does not change color based on the Client skin selected and the links on the Resources tab have poor color contrast when using the Office 2016 Dark skin.
Bug# 222460 votes
Email routing allows activity requests to be routed into non-activity queues and internal routing controls will not be applied to move the request into the proper activity queue.
Bug# 217550 votes