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# 47270 votes
Ctrl-S does not save on Addons form in Customization Manager like it does with the other CustMan forms
Bug# 46530 votes
Bug# 48670 votes
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# 48370 votes
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# 48330 votes
When staff force a password is forced reset from the client for a web user, pressing the submit button successfully changes the password, BUT it reloads the change password page with blank values and without a status message stating the password has been successfully changed.
Bug# 47950 votes
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# 46810 votes
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# 46500 votes
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
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