ILLiad Known Issues
137 results found
Lending DLL is not configured as an application in IIS by default
When the SAML module is configured for ILLiad, the Lending web pages may direct the user to the identity provider (IdP) login page since the Lending folder within the ILLiad web folder is not configured as an IIS application by default in ILLiad installs.
Bug# 198240 votes
Email subject encoding can fail for non-ASCII characters
Encoding for the subject line of an email sent from ILLiad can fail if it contains non-ASCII characters.
Workaround: If an email is bounced back for this issue, you can change the subject line of the email to remove any non-basic characters
Bug# 195470 votes0 comments · Email · Admin →
Switching users with an addon or PubMed form open causes an error
When switching staff users in the ILLiad Client, if the request form is open and currently displaying an addon form or PubMed, the following error occurs:
2022-10-24 23:11:52,590 ERROR AtlasSystems.ILLiad.Client.Program - A thread exception has occurred.
System.NullReferenceException: Object reference not set to an instance of an object.
Bug# 195620 votes
DOCLINE scripts may incorrectly import library name into the lender string
If a library's name contains an all-caps string inside parentheses such as "(ABCD)," this text will be incorrectly imported into the lender string for the ILLiad request from DOCLINE.
This bug affects DOCLINE scripts for both ILLiad 9.1 and 9.2.
Bug# 190840 votes
DOCLINE Manual Request information does not import to ILLiad
After the DOCLINE 6.2.40 update, Manual Requests do not switch back to the Details tab in the ILLiad 9.2 Client when placed and do not auto-populate fields with request information.
Note that this issue only affects the DOCLINE scripts for ILLiad v9.2.
Bug# 191790 votes
AlwaysTrustLocalDelivery customization key value is ignored by Odyssey
Odyssey will only automatically deliver files for a request from another site on the same server if the Trusted Sender option on that site's lender address record is checked even when the AlwaysTrustLocalDelivery customization key is set to "Yes."
Bug# 189010 votes
Overdue notices may be sent incorrectly if the System Manager can't connect to the database
ILLiad will ignore "No" values in the BorrowingOverdueNoticesActive or LendingOverdueNoticesActive customization keys and set these to "Yes" if the System Manager can't connect to the database when checking the key values, which may cause overdue notices to be sent out incorrectly.
Bug# 189330 votes
Buttons that are disabled can still be used with keyboard controls
In both the Actions menu dropdown and the Transaction menu, some actions that are completely disabled for mouse users can still be fully used by keyboard users without being blocked and with no error message.
Bug# 189190 votes
Transaction menu button text is not fully visible on certain display sizes
The text content of the transaction menu buttons does not fully display on small screen sizes or high zoom levels and requires horizontal scrolling to view. In some cases, horizontal scrolling is not enough to read the full button text.
Bug# 189180 votes
Actions dropdown options are not fully visible on certain display sizes
The Actions menu dropdown options do not fully display on small screen sizes or high zoom levels and require horizontal scrolling to view.
Bug# 189160 votes
The color used for web alert titles does not pass color contrast requirements
The default color used to display titles for web alerts does not have sufficient color contrast against the default background color in the web pages.
Bug# 187740 votes
Modal dialog for web alerts contains broken 'aria-labelledby' attribute
The 'aria-labelledby' attribute used on the modal dialog for web alerts is broken and causes an accessibility issue.
Bug# 187750 votes
The label color for fields that fail server validation does not pass color contrast requirements
When a field fails server validation, the web pages set the color of the field label to a red color that does not pass contrast requirements with the default form section color.
Bug# 187670 votes
Hyperlinks added to the cookie consent banner will fail color contrast requirements
If a hyperlink is added to the cookie consent banner, the default hyperlink color will not provide sufficient contrast against the banner's background color.
Note: Hyperlinks are not present in the banner by default.
Bug# 184850 votes
Set Default (Local Machine) option in SQL Alias Manager v1.3.2 may fail due to permissions issue
Staff with local admin privileges on their desktops or VMs are unable to successfully use the Set Default (Local Machine) option with SQL Alias Manager v1.3.2 without also requiring Full Control privileges on the folder where the DBCs reside, which causes issues in shared environments.
Bug# 187470 votes
Special characters prevent Docline citation information from importing
Transaction information is not imported when there are special characters in Docline's citation field.
Bug# 185060 votes
Processed requests can be resubmitted if edit form is left open in the web
If a request is left open in the edit form by the user on the web interface and staff proceeds to process that request to a status where editing is not allowed (e.g., Request Sent), the user will still be allowed to submit the request from the edit screen, which will return it to a prior processing status.
Bug# 183950 votes
LendingWebPath customization key is referenced in the DLL but missing from the Customization Manager
A LendingWebPath customization key to specify the path of the Lending web directory is referenced in the DLL but missing from the ILLiad Customization Manager.
Bug# 180130 votes
Default FAQ web page contains inaccurate information about cookies
The default FAQ web page contains information about cookies stating that "the technology that we use sends a Session ID to be stored on your machine. You can refuse this cookie and still be able to use ILLiad without any problems."
This information is inaccurate as the Session ID cookie is essential for the ILLiad web interface.
Bug# 182650 votes
An error status message is not displayed by the Lending DLL when the web page can't be found
If the Lending DLL can't find a web page, the user is sent to the Error.html page but a status line is not displayed explaining the error.
Bug# 180910 votes