ILLiad Known Issues
-
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 -
0 votes
-
The borrowing tab is displaying the list of queues in reverse alphabetical order
On the Borrowing tab, ILLiad is displaying the list of queues in reverse alphabetical order and is adding new custom queues to a new "Requests" group, instead of the existing "Requests" group.
Bug# 5642
0 votes -
Recommended Action Tooltip is not updating
The Recommended Action Tooltip is not updating when hovering over the Select Recommended Action button on the Pipeline Request Review form.
v9.1
Bug# 56430 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
-
Database field size not consistent for the Staff field
The Staff field in the TestModeInvoiceTracking table does not match other tables using "Username". The field should be expanded to be the same size as other Username fields in the database - nvarchar(100).
Bug# 4913
0 votes -
Database field size not consistent for the AddedBy field
The AddedBy field in the Notes and LibraryNotes tables do not match other tables using "Username". The field should be expanded to be the same size as other Username fields in the database - nvarchar(100).
Bug# 4912
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
-
Article Exchange Documents not Delivered when Odyssey Trusted Sender is set to Always
Documents delivered via Article Exchange are getting stuck in Awaiting Odyssey Processing even though the Customization Manager key ArticleExchangeTrusted is set to Always and Override Trusted Sender is NOT checked in the Lender Address record.
Bug# 4837
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 -
Some Customization Keys do not have a description explaining its purpose
The following Key do not have a description in the Customization Manager:
RenewalWindowDays
ISOCanSendReceived
ISOCanSendReturned
ISOCurrencyCode
ISOMonetaryValueBug# 4569
0 votes