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# 46020 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# 46010 votes
This is because RemoteAuth takes authority. As a result patron requests may fail after being submitted since the user is invalid.
Bug# 45750 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# 45710 votes
The following Key do not have a description in the Customization Manager:
Bug# 45690 votes
The Odyssey Manager does not check to see if the Library is a Trusted CopyrightPayer so the CopyrightAlreadyPaid checkbox never gets checked when the file has been received. As a result, the Journal Titles received from a Copyright Payer end up on the Copyright Reports.
Bug# 44910 votes
The DLL is trimming any leading or trailing spaces from the password field within the web, whereas the client just runs the password as it's entered with the spaces. For example, if my password is "ABC" when logging in the client "ABC " fails, whereas it works in the web pages because the space is being removed.
Note: A space can exist within the password itself, e.g., "P@ss W0rd", as long as it's an accepted requirement in the Customization Manager. The spaces within the password will not be trimmed by the DLL.
Bug# 44900 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.
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.
The email import behavior when creating a new user from an import request with the EMailImportAutoUserRecord set to yes will cause the generateuser call to appear as though it has failed, but the request is still imported, and assigned to a default user
Should also be noted that this process works correctly when the user already exists in the system. This is only occuring when AutoUserRecord is set to yes, and the Username value from the email does not exist in the database.
Bug# 44410 votes
When a user changes a Lender's password from the ILLiad client, it only changes the password for the NVTGC that the user is logged into the client under, instead of changing it for all NVTGCs. As a result, the lender may be able to log into the client under that particular NVTGC but unable to log into the web.
v9.0 & 8.7
Bug# 44360 votes
When a user who has an ILLiad login and an AuthType of Default tries to log in to the ILLiad web pages when WebAuthType=RemoteAuth, they are able to log in without being prompted to change their password (when trying to log in for the first time after the upgrade).
An error message/feedback pop-up will appear when a staff user attempts to group transactions by a field (e.g., username) in dd stacks searching. The log will record this error as "Transaction number 0 not found".
v8.7 & 9.0
Bug# 41720 votes
Workaround: Try different numbers in the parameters of the report.0 votes
Workaround: Some sites have reported that changing to another skin and back to original skin allowed Login As to work again.
The Client Error log may say the following: A thread exception has occurred.
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
When downloading an update, the Client may hang if it receives a 404 response when trying to download the update executable
The RegEx used assumes the first angle bracket as part of the tag instead of a bracket inside a tag parameter. This impacts email and SMS templates.
This error occurs with Aeon and ILLiad integrations.