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

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.

Numbers in Lending Fill Rates and Lending Requests Received by SystemID and numbers in DocDel Fill Rates and DocDel Finished and Cancelled aren't matching up in the web reports. This is because dates are incorrectly caching by date and time rather than solely by date. This leads to the report grabbing an incorrect number of requests for a given range of dates if the start date or end date gets a time included.

Short-term workaround: Clear the cache to make sure the dates don't change.

Bug# 10598

Google Authentication for Docline is not working properly in ILLiad 9.1. This is causing users to receive script errors or a message indicating the browser is not secure when logging in. The issue is a result of a conflict with Google's authentication. If you're experiencing issues with using a Google account, there are several other supported login methods.

See this article for information about the different login methods supported: https://support.atlas-sys.com/hc/en-us/articles/1500002760821

See this article to learn how to change your login method: https://support.atlas-sys.com/hc/en-us/articles/1500002870502

Bug# 10417

ILLiad Lending datarowDefaultRequest and includeTransaction menu contain duplicate classes.

Bug# 10147

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

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

v9.0 and v9.1

Bug# 9892

The alignment for the buttons at the bottom of ChangeUserInformationare set to be right-aligned by default. For consistency, these need to be left-aligned like in the NewRegistration page.

Bug# 7683

v9.1
Bug# 7323

Remote auth validation does not load the user's reported session id, duplicate form submissions aren't being prevented.

Bug# 9013

In OverduesList.cs, the gridViewRequest_CustomColumnDisplayText function may throw a null reference exception when it attempts to call ToString() on e.Value.

Bug# 8564

A blank error message pops up when you:

1. Open ILLiad Client


2. Enter a valid username


3. Leave password blank


4. Attempt to login

Bug# 8363

The date shows up correctly in the client and the database but not in the transaction notes.

v9.1
Bug# 7847

The debug web reports log doesn't show anything for the crash, just stops logging.

See attached screenshot for an example error message.

Bug# 7688