29 results found
The "Save CCC Information" button can't be used to save copyright information for requests in the Awaiting Copyright Clearance - Pipeline queue.
Bug# 189140 votes
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 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# 259650 votes
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# 232850 votes
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# 229340 votes
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# 213510 votes
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# 195620 votes
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# 177980 votes
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# 174020 votes
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.
Workaround: Close the Process Copyright form and reopen it.
Bug# 167500 votes
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# 143320 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# 128410 votes
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# 119100 votes
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# 115720 votes
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# 100200 votes
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# 102810 votes
There is no specific ordering that determines the way the web alerts appear within the client.
Bug# 67250 votes
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
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