Some web users have been able to re-submit requests after they are placed in statuses that should not allow re-submission.0 votes
When an individual user has a request limit of “0” set in the client (so that the user can have unlimited requests), that “0” then shows up in web status lines as the user’s request limit if the <#requestlimit> tag is used in any status lines."
Status line message: "Thank you for your request(s). If you have more than 0 active requests, your requests will be placed in review and you will need to submit individual requests from the Saved Requests page."
Should clarify message if request limits are used overall, but individual user has unlimited limit.0 votes
Using the web request form, users can enter a new/blank line(s) before the item's title. That character is saved in the database causing the ItemTitle Field to appear blank in the client's grid view, and missing in the email templates when the ItemTitle tag is used.0 votes
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
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
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