ILLiad Known Issues
149 results found
-
User notification preferences are not set if user is moved across NVTGC web pages as they register
If a user creating a new account on the ILLiad web pages selects a pickup location/NVTGC on the user registration form that is different from the NVTGC associated with the set of web pages being used to register, then notification preferences will not be set when the account is created.
Bug# 21707
0 votes -
Missing trailing slash breaks WebPDFPath key
The file path entered in the WebPDFPath customization key will not be recognized unless it contains a trailing slash at the end.
Bug# 21457
0 votes -
Users without layout customization permissions can't view customized layouts in the ILLiad Client
Custom layout changes will not show in the ILLiad Client unless the logged-in staff user has the "Can Customize Layouts" permission enabled in the ILLiad Staff Manager.
Bug# 21351
0 votes -
Some characters are not correctly encoded when logging.
Some characters (such as those with diacritics) are not properly encoded in log files.
Workaround: Add <encoding value="utf-8" /> under the <appender> element in the default log.config files.
Bug# 21306
0 votes -
ILLiad API errors when DueDateOverride value is NULL
The ILLiad API will return an error when submitting a Loan request for a Lending Library that belongs to a Group with a NULL DueDateOverride value (i.e., when no Lending Due Date Override value has been set for that Group).
Bug# 20813
0 votes -
PDF Utility handling fails for PDFs generated by iTextSharp 4.1.6
The PDF Utility used by the Odyssey Manager will return errors when delivering PDFs generated by iTextSharp 4.1.6.
Bug# 20683
0 votes -
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 -
Copyright data can't be saved for requests in the Awaiting Copyright Clearance - Pipeline queue
The "Save CCC Information" button can't be used to save copyright information for requests in the Awaiting Copyright Clearance - Pipeline queue.
Bug# 18914
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 -
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# 18919
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