ILLiad Known Issues
143 results found
-
Notification preferences not set for users created from UserValidation with LDAP
Notification preferences will not be set for new users created via the UserValidation table if LDAP authentication is being used.
Bug# 20309
0 votes -
Volume information will not import if the DOCLINE citation doesn't contain an issue number
After the DOCLINE 6.2.41 update, volume information will not import into the ILLiad request if the DOCLINE citation does not contain an issue number. This affects both ILLiad 9.1 and 9.2.
Bug# 20282
0 votes -
Electronic Delivery Utility routes requests to Delivered to Web before file is processed by Odyssey Manager
The Electronic Delivery Utility routes borrowing requests to the Delivered to Web status before the file is successfully processed and delivered by the Odyssey Manager, which can make the file inaccessible to the patron on the web if Odyssey processing fails.
Bug# 20030
0 votes -
Electronic Delivery Utility sends 0 KB files
The Electronic Delivery Utility (EDU) will send 0 KB files, which are invalid and may cause processing errors. Instead of sending these files, the EDU should check for 0-byte files or ensure that the size in the file metadata matches the actual file size before sending.
Bug# 20029
0 votes -
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# 19824
0 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# 19547
0 votes -
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# 19562
0 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# 19084
0 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# 19179
0 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# 18901
0 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# 18933
0 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# 18747
0 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# 18506
0 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# 18395
0 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# 18013
0 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# 18091
0 votes -
Unused JavaScript file in the ILLiad Lending web pages
The userNotificationPreferences.js file located in the default ILLiad Lending web pages is unused in the web interface and unnecessary.
Bug# 18086
0 votes -
Error page is not displayed by the Lending DLL when the DBC file can't be found
A "File Not Found" error is displayed instead of the Error.html web page when the Lending DLL is unable to find the DBC file containing logon settings.
Bug# 18004
0 votes -
Lending web directory path is logged incorrectly by the DLL
The path to the Lending web directory is incorrectly logged by the Lending web DLL.
Bug# 17999
0 votes -
Transaction tags are encoded twice by the web DLL
Transaction tags are encoded twice by the ILLiad web DLL, which can lead to the resulting text being displayed as encoded on the web page.
Bug# 17973
0 votes