ILLiad Known Issues
143 results found
-
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 -
"Not Wanted After" column sorts results incorrectly in grid view
Sorting by the "Not Wanted After" column while in a grid view will order results by the first digit in the date string rather than by the date itself.
Bug# 17798
0 votes -
The data source file path for invoice print templates is incorrect
The invoice print templates (BorrowingBillingManagerInvoice.doc, LendingBillingManagerInvoice.doc, and DocDelBillingManagerInvoice.doc) are set to use C:\Program Files (x86)\ILLiad\Print as the path to the data source files instead of C:\Users[username]\Documents\ILLiad\Print.
Bug# 17615
0 votes -
Billing Manager requires a trailing slash in the PrintDocumentsPath value
If the file path specified in the PrintDocumentsPath customization key doesn't contain a trailing slash, documents will not be printed from the Billing Manager and no error will display noting the problem.
Bug# 17614
0 votes -
Unable to force password reset on Lender Address records
When using the Change Password button on a Lender Address record in the ILLiad Client, checking the Force Password Reset checkbox will not force the lender to update the password upon login.
Bug# 17402
0 votes -
ILLiad SAML Module will not log signing response errors
If the SAML.config file for the SAML Module indicates responses will be signed, the module will throw a 500 error when a response is not signed but will not log the error.
Bug# 17263
0 votes -
ILLiad Client displays incorrect count for requests imported from Docline
The ILLiad Client will display an incorrect count in the status bar for the number of requests imported from Docline when importing multiple requests.
Bug# 17278
0 votes -
ISOFieldMapping table is missing from the ILLiad Customization Manager
The ISOFieldMapping table is not present/customizable in the ILLiad Customization Manager in both ILLiad v9.1 and v9.2.
Bug# 17150
0 votes -
Creating new staff users allows trailing spaces
Trailing spaces are allowed for values in the Username, First Name, and Last Name fields when creating new staff users in the Staff Manager, which may cause issues with matching the user in other systems (e.g., AtlasBI).
Bug# 16656
0 votes -
Leaving the ILLiad Client idle will trigger CCC credentials error on the Process Copyright form
Leaving the ILLiad Client idle for a period of time will trigger the following error if the Process Copyright form was left open:
ILLiad 9.1: "Error communicating with the CCC. Please ensure that your CCC credentials are configured correctly."
ILLiad 9.2: "Unable to authenticate with CCC. Please check your configuration."
The Client logs will display the following message:
-DEBUG AtlasSystems.ILLiad.Client.Controls.CopyrightSearch - System.Exception: Error communicating with CCC.
at AtlasSystems.Copyright.CccApiClientBase.<Reauthenticate>d__20.MoveNext()Workaround: Close the Process Copyright form and reopen it.
Bug# 16750
0 votes -
LendingPrintRequest.doc print template contains incorrect merge fields
Several merge fields used on the LendingPrintRequest.doc print template are incorrect.
Bug# 16538
0 votes -
Some server addons may not log errors
Certain kinds of server addons may experience an issue where errors are not logged. INFO and DEBUG entries for the addon will still log properly.
Bug #16386
0 votes -
Initial Cleared User email may fail to send when using certain authentication types
When using certain authentication types (including PatronAPI, ILLiadExclusive) with the automatic user clearance feature, the notification preferences for newly registered users on the web will not be set before the Cleared User email is sent, leading to failure to send the email and the following error:
ERROR AtlasSystems.ILLiad.WebPlatform.Controllers.V1.NotificationController - AtlasSystems.ILLiad.DomainLogic.Exceptions.NotificationRequiredException: Exception of type 'AtlasSystems.ILLiad.DomainLogic.Exceptions.NotificationRequiredException' was thrown.
Bug# 15092
0 votes