When a PDF has been loaded by a PDF Document Processor (on the scanning form or the electronic delivery form), the filesystem keeps a lock on that file until the ILLiad client is closed. This is because the processor is not closing the file.

Error Log Message Example: The process cannot access the file 'C:\Program Files (x86)\ILLiad\elecdel\o48034.pdf' because it is being used by another process.

Bug# 8578

The volume/issue and pages blank are not being imported when there are non-numeric values in the Citation field such as supplemental issues and e-page numbers.

Bug# 6539

The web pages with extra div tags include:

EditArticleRequest
EditBookChapterRequest
EditConferencePaperRequest
EditGenericRequestTesting

Bug# 6022

v9.1
Bug# 5852

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.

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

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.

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.

For OpenURL requests, if the patron already has an active websession and do not have to log in the characters are correctly translated.

The error parameter for the PhotoJournalTitle field on EditPatentRequest.html has an incorrect value of ERRORLoanAuthor in the ILLiad 9.1 web pages. The correct value for this parameter is ERRORPhotoJournalTitle.

Bug# 14817

The text configured in the SLLogout status line key will not display on the 9.1 web pages after the user logs out of ILLiad.

Bug# 14798

Values will not persist properly when using Safari or any other WebKit-based browsers.

Workaround: Add the following code to line 52 of atlasUtility.js within the block of code handling persistedValue:

$(this).find("option[value='" + persistedValue + "']").prop("selected", true);

Bug# 14597

Requests in ILLiad may sometimes be created with a blank/NULL transaction status that can then cause issues with web reports, routing rules, and custom searches.

Bug# 14436

If a transaction doesn't have value in the Title field, Author field, or any other field encased in a heading element (h4,h5, etc) on a datarow template, then the heading will appear empty in the web pages and cause confusion for screen reader users.

Bug# 14456

The colors set in the default CSS for "small-notes," "req," and <p> tags do not meet the WCAG AA accessibility requirements for color contrast.

Bug# 14424

When a request is edited on the web, ILLiad will pull in the latest note regardless of the value in the WebTNNotesFilter key.

Bug# 14374

If the "Route Request to Review" action is selected in the configuration settings for the OCLC Automated Request Manager, this can lead to ILLiad unexpectedly closing the affected direct requests.

Bug# 14342

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

The Microsoft Excel file produced when exporting results from the Copyright web report populates the results from the Finished Requests table in all three sheets (Finished Requests, Outstanding Requests, and Completed Orders).

Bug# 14244

The role="heading" attribute on the <div> containers surrounding most web pages can cause strange behavior with screen readers depending on the content of the file.

Bug# 13849