ILLiad Known Issues
31 results found
-
ILLiad 9.2 Client crashes when Rapid API not responding When Rapid API endpoint is not responsive and Rapid requests are opened in the client, the client crashes.
Bug# 31499
1 vote -
Save of address is not Done when selecting it on the Add Address form When an address is selected/added to a request for a Lending request the record is not saved to the database (LenderAddressNumber field on Transactions table) but appears on the request when user is returned to the Request Form so user thinks it is saved.
Bug# 32016
1 vote -
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 -
Request cloning from the staff client will always set the RequestType to Article Repro Steps
1. Open a loan request in the staff client
2. Clone the request. The behavior is the same regardless of cloning to same user or different user and if the request is/is not opened after the process is completed.4 votes -
Z39.50 may duplicate item records for holdings Z39.50 will pull in any hardcoded holding elements in the XML for a holding record, which can cause the first item listed in the record to be duplicated in ILLiad.
Bug# 25965
0 votes -
Invalid routing rules cause error during custom routing When a request's transaction status is changed, ILLiad will loop through active routing rules and check for a rule matching the request's TransactionStatus and ProcessType, and then apply the rule when appropriate. However, if that routing rule is invalid because it has null fields (e.g., a null value for TransactionStatus, ProcessType, MatchString, NewTransactionStatus, or NewProcessType), an error will be logged and the routing process will fail.
ILLiad should instead check to ensure the routing rule is valid before applying the rule to the request and, if the rule is invalid, provide detailed information in the ILLiad Client log to state…
0 votes -
Changes to the Location field dropdown selection on the Users to Clear form will revert if another dropdown is modified Changes to the dropdown selection in the Location field on the Users to Clear form will revert if the value of another dropdown on the form is modified.
Bug# 23285
0 votes -
PDFs from HathiTrust experience visual bugs during import PDFs from HathiTrust do not properly display in the ILLiad Client's Scanning form during import and may contain visual bugs such as blank pages, but will send and deliver as expected in ILLiad 9.2.
Bug# 22934
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 -
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 -
"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 -
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 -
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 -
Screenshots submitted through the Feedback form are corrupted when saved Screenshots submitted through the Feedback form of the Client will display correctly on the form but will be corrupted after the file is saved.
Bug# 14332
0 votes -
Leaving the ILLiad Authentication checkbox unchecked/unchanged when creating a new user will default the user to ILLiad Authentication type. Leaving the "ILLiad Authentication" checkbox unchecked/unchanged while creating a user in the Client still defaults to ILLiad Authentication when the user is created, even though the option is not checked when saving.
Workaround: Check and uncheck the box before saving.
Bug# 12841
0 votes -
Large number of saved layouts causes a database timeout If the combined file size of saved layouts is too large, it may occasionally cause database timeouts and revert all Client layouts to the default.
Bug# 11910
0 votes -
Errors opening/sending some types of PDFs in the Client The ILLiad Client may fail to open PDFs downloaded from databases/online sources or PDFs that are password-protected/encrypted, leading to delivery failures when attempting to send the documents via Odyssey. The following errors are returned in the Client log:
-"An error occurred while attempting to load a file."
-"Input data is not recognized as valid pdf."Workaround: Convert the affected PDFs files to TIFF format and upload the converted file into ILLiad.
Bug# 11572
0 votes -
Persist Settings bug if a search group is not selected The "Error saving z39.50 persistent settings to registry" occurs if you don't have a default Z39.50 Search Profile/Configuration and open the request form.
Bug# 10020
0 votes -
FormClearUser doesn't populate Yes/No values for ElectronicDelivery field The ElectronicDelivery field on the Clear User form does not have any default or selectable values in the dropdown, but will accept Yes or No if manually typed in.
Bug# 10281
0 votes -
Order of Web Alerts There is no specific ordering that determines the way the web alerts appear within the client.
Bug# 6725
0 votes