ILLiad Known Issues
136 results found
-
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 -
Format field value (e.g., DVD, CASSETT, etc.) on the Multimedia form does not save to database
v9.1
Bug# 58520 votes -
Odyssey Manager creates blank pdfs
Odyssey Manager fails to convert large TIF files of approximately 1 GB to PDF. The log does not indicate a problem but shows the process occurring in just a few seconds. The resulting PDF file is blank.
1 vote -
Unable to modify some ZServer configuration fields in Customization Manager for MARC records
If a Z39.50 server configuration is set to use MARC holdings, the availability fields become read-only. If you need to edit the availability fields, please contact your support representative so they can edit directly in database for you. v8.7 and v9.0
1 vote -
Some unicode characters are not properly encoded on OpenURL submissions if the user must log in first.
This seems to be a new issues introduced in ILLiad 8.7 when we switched to Delphi XE 8. To reproduce, submit an OpenURL request using the included URL both with and without a session. When you're already logged in, the cyrillic characters are rendered correctly in the author field and a ligature is used in the title. If you don't have an active session and are sent through the logon2 page, those fields will be rendered as ?s or boxes, indicating a problem with the form state encoding. I confirmed this URL worked correctly on ILLiad 8.6.x and earlier.
2 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 -
Invalid characters in title error when submitted to OCLC
Workform Mapping should be replacing invalid XML characters.
Currently workform mapping handles replacement of \r & \n.
Repro
1. Create a borrowing request in the client.
2. Via the database update an Article Title to include ""
3. Close the request form and re-open after the invalid characters are added.
4. Search OCLC and attempt to send the OCLC request.1 vote -
UTF-8 characters are not decoded properly in some cases
For OpenURL requests, if the patron already has an active websession and do not have to log in the characters are correctly translated.
2 votes -
ILLiad SAML Module overwrites multiple values for same attribute
If multiple values are received for the same SAML attribute, the ILLiad SAML module will overwrite those values in the order received instead of concatenating them.
Bug# 24338
0 votes -
Deleting a DSP addon that is used in business rules causes database constraint error
Attempting to delete a DSP addon that is being used as a target in DSP business rules will trigger the following database constraint error message in the Customization Manager:
'Error deleting server addon. The DELETE statement conflicted with the REFERENCE constraint "FKDecisionSupportPipelineBusinessRulesAddonTarget".'
Bug# 23937
0 votes -
Rapid Manager initializes new lender records with NULL values for Odyssey trusted sender settings
In some cases, Rapid Manager will create new lender address records with NULL values set for TrustedSender and TrustedSenderOverride, which can break the logic to determine if a given sender is trusted if there are many records that have the same URL for the Odyssey IP.
Bug# 23892
0 votes -
Byte arrays passed to .NET methods are converted to null due to an NLua bug
Byte arrays (often referred to as Byte[] in Microsoft's .NET documentation) passed from Lua to .NET methods are converted to null, causing those .NET methods to fail when included in addon code.
This is a known NLua bug present in the version of the NLua component used by the ILLiad application, detailed here: https://github.com/NLua/NLua/issues/438.
Bug# 24017
0 votes -
Rapidly clicking Docline buttons can cause ILLiad Client to crash
Clicking a button on the Docline interface three or more times in rapid succession causes the ILLiad Client to crash when the WebView2 browser control is used.
Bug# 23031
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 -
Error is returned in logs for PDF files using non-numeric filenames during ElecDel cleanup process
When PDF files using filenames that contain non-integer values are handled by the ILLiad System Manager's electronic delivery file clean-up process, the following error will be returned in the logs:
"ERROR AtlasSystems.ILLiad.SystemManager.Cleanup - ERROR PROCESSING C:\ILLiad\PDF<FILENAME>.pdf -- Skipping -- Could not parse transaction number from the filename.
System.FormatException: Input string was not in a correct format.
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at AtlasSystems.ILLiad.SystemManager.Cleanup.ProcessPdf(FileInfo fileToProcess)"Bug# 22556
0 votes -
Improperly formatted routing rules can lead to email spam
When a routing rule is improperly formatted and returns an error, the transaction will not complete the routing process and will remain "stuck" in its original status. This can lead to email spam if the original status is a queue that sends an email notification to the user (e.g., Awaiting Customer Contact) as the notification will be sent repeatedly until the request is manually routed out of the original queue.
Bug# 22851
0 votes -
Address matching for some Docline requests may fail
For some Docline requests, only part of the shipping address is matched and saved from the request text on the Lender Selection form, which then causes address matching to fail when that request is imported from Docline into ILLiad.
Bug# 22013
0 votes -
Database Manager may fail to delete CopyrightSessions records
The ILLiad Database Manager will fail to delete CopyrightSessions records that contain non-integer values in the OrderHeader and OrderDetail fields.
Bug# 21882
0 votes -
Log messages may contain extra punctuation marks
Several log messages (e.g., the "Error refreshing system alert list" message) are improperly formatted and contain extra punctuation marks at the end.
Bug# 21726
0 votes