ILLiad Known Issues
143 results found
-
Duplicate form submission does not work under remote authentication
Remote auth validation does not load the user's reported session id, duplicate form submissions aren't being prevented.
Bug# 9013
0 votes -
Webreports login crashes with wrong Username
The debug web reports log doesn't show anything for the crash, just stops logging.
See attached screenshot for an example error message.
Bug# 7688
0 votes -
Order of Web Alerts
There is no specific ordering that determines the way the web alerts appear within the client.
Bug# 6725
0 votes -
0 votes
-
Long Routing Matchstring (e.g., over 40,000 characters) Disappears Visually
When copying and pasting a long matchstring (e.g., over 40,000 characters) into the Customization Manager, the match string will disappear after clicking out of the field and then saving. The matchstring will still work; however, you won't be able to see the entire matchstring in the field.
Bug# 4649
0 votes -
Disposing Article Exchange Processor error
The Odyssey Manager does not correctly dispose of its ArticleExchangeProcessor after processing Article Exchange due to the ILLiadOdysseyManagerHost.ArticleExchangeTimerTimer functionality.
Bug# 5454
0 votes -
ServerVariable support for RemoteAuth and Authentication Enhancments
The RemoteAuthValidation would prevent the ILLiad web DLLs from looking at IIS server variables when determining remote authentication details, such as the username.
v9.0
Bug# 5021 & 50210 votes -
0 votes
-
Documents can't be delivered electronically, or get stuck in a electronic delivery queue/workflow because of corrupt PDF files
Files that are corrupt can't be retrieved through ILLiad and can potentially cause the client to crash or freeze until the client has been restarted. If the corrupt files were found, canceled, or delivered manually, they will need to be manually updated in the OdysseyRecieved table once the client has been restarted.
Bug# 4727
0 votes -
0 votes
-
Null reference exception if unknown user attempts login
When a staff member attempts to login to the web reports with a username that does not exist as a staff account, they will receive a null reference due to the log entry.
Bug# 4833
0 votes -
Routing in Scripting can be overwritten by SaveDataSource
In an ILLiad addon:
When you make changes to transaction fields, route the transaction and then SaveDataSource it will undo the Route action.
Workaround: This can be avoided by saving before routing.
Bug# 4681
0 votes -
ILLIAD: Removed profile groups still appear in recently used menu
Profile groups removed from the GAC table still appear in the recently used menu, and the recently used menu appears to grow infinitely. See attached screenshot.
Bug# 4650
0 votes -
0 votes
-
Web validation rules for required fields don't account for 'NULL' special value
The ILLiad web DLL will perform special handling for text values equivalent to 'null,' replacing them with an actual null value when it updates the database.
Bug# 4602
0 votes -
In the web, 'null' is a special string that can prevent some valid data from being inserted, specifically as a user last name.
ILLiad does a case-insensitive comparison of the field value and will treat a user record with the LastName of Null as null when it updates the database.
Bug# 4601
0 votes -
ILLiad can incorrectly create a new user under RemoteAuth if the provided username is NULL
This is because RemoteAuth takes authority. As a result patron requests may fail after being submitted since the user is invalid.
Bug# 4575
0 votes -
The renewal button in the ILLiad web pages may be enabled even if the due date is outside the renewal window
The renewal button doesn't consider the due date and the RenewalWindowDays/RenewalBeforeWindowDays customization keys when determining if the button is visible in the web pages.
Bug# 4571
0 votes -
Changing skins will cut off the Holdings window, hiding the Delete and Clear buttons from the Selected Lenders box
This issues occurs when you change the skin then navigate to Open request>OCLC tab>Holdings tab.
Workaround: Restarting the client fixes the issue; however, you will need to restart the client each time you change the skin or else the error will occur again.
v9.0
Bug# 44810 votes -
The BillingInformation table in the Lending Web Pages will not display if BillingActive is set to false
The lending web pages prevent the display of the billing information table when BillingActive is set to false.
Workaround: If BillingActive is set to BillingActiveLending, then the BillingInformation table will always display in the lending web pages.
Bug#4444
0 votes