ILLiad 9.1 Release Notes

Print Friendly and PDF Follow

Important Update Information

Released December 18th, 2019


As promised on the ILLiad Roadmap, here are the main features/enhancements of ILLiad 9.1:

  • Authentication Enhancements  
  • Automatic User Creation
  • New, Fully Accessible and Responsive Web Pages  




To view the pictures on a larger scale, click the image to expand. 
  • Enhanced Rapid / RapidR Integration


  • Decision Support for Request Processing    




     There are over 60 bug fixes and several underlying component updates to continue supporting external systems in this release. 

Considerations Before You Update   

Review ILLiad 9.1 FAQ

For frequently asked questions and additional information regarding the 9.1 features and fixes, please see the ILLiad 9.1 FAQ. You can also view the recorded 9.1 pre-release webinars in the VTL (ILLiad in Focus 9.1 and ILLiad in Focus 9.1 Encore). For all other questions, please contact support at

Updating During Normal Working Hours

Please consider running updates and installations during standard support hours 8 am - 5 pm eastern time (business days Monday - Friday) so that help is readily available if any issues are encountered.

Updating Procedures

Before you begin updating, please review the Hardware and Software Requirements for Version 9.1. For specific instructions on updating, see Updating ILLiad to the Newest Version.

Updating from Version 8.7

If you are updating from ILLiad 8.7, please review the ILLiad 9.0 Release Notes and FAQ since all the password change requirements will impact you after updating to version 9.1. You will need to update the server and the client on each machine to 9.0 prior to updating the server and clients for ILLiad 9.1. It's not required to login or change any passwords until after you've updated to 9.1.

NoteWorthy Changes in the 9.1 Update

  • The existing RemoteAuthUserVariable Customization Key will be removed and recreated as a default line in the new RemoteAuthValidation table. This change was added in support of the Authentication Enhancements feature.

Manual ISO Service Upgrade

The ISO Service requires a manual upgrade after the 9.1 update due to the new database configuration. For instructions on upgrading, see 9.1 ISO Service Upgrade.

Rapid Returnable Workflow Configuration

After updating ILLiad to v9.1, please contact Rapid staff at There is a UsesReturnableWorkflow flag that needs to be turned on. If the flag has not been configured when a lender sets a Book request to Filled via the Rapid API and the borrower utilizes the UsesReturnableWorkflow, then instead of setting the request to Filled, it sets it to Shipped.

Point Releases

Bug fixes and new features are added periodically as point releases. See 9.1.x point releases below:

16 January 2020 (9.1.1) Server & Web DLL Release

ILLiad 9.1 Features & Fixes 

Addons | Administrative | Authentication | Connection Manager | Decision Support for Request Processing | DOCLINE | Email | ISO | OdysseyRAPID | Staff Client | Staff Customization Manager | Staff Manager | Web Interface |  Web Platform



Added support for addon history entries added to the Request Form using the ExecuteCommand("AddHistory", {TransactionNumber, Entry, Username}).



ILLiad 9.0 and 9.1 are now supported to run on Windows Server 2019. 


Fixed issue where the ILLiad API was not using database defaults for creating new requests. For example, a request would not appear on the ILLiad reports even though it was in the Client if the CopyrightAlreadyPaid key is set to Null via the API since the reports are looking for the default value of No or Yes. Bug# 4093



Added Authentication Enhancements that allow ILLiad to validate patron registration through their external authentication system by verifying access and importing relevant user information. At each login, ILLiad will validate credentials and verify access as well as update any relevant identity information. For more information, see Authentication Enhancements


Through the use of Automatic User Creation, ILLiad will now create a user record automatically based on identity information provided by an external authentication system for unregistered users who login to ILLiad. This feature is supported by the Authentication Enhancements feature. For more information, see Automatic User Creation. Removed the Customization Key RemoteAuthUserVariable and replaced it with a line item in the RemoteAuthValidation table.


Sites will be able to force patrons to update their user information by Auto Expiring Users. Four new Customization Keys have been added to support auto expiration: 

  • AutoExpireUsers
  • AutoExpireUsersClearedValue 
  • RenewedUsersClearedValue
  • AutoUpdateExpiration

For more information, see Automatic Expiration of Users.


Added SLUserLockedOutUserLoginAttemptsBeforeLock, and UsingUserLockout Customization Keys to temporarily block web users after a configurable number of invalid password login attempts. In support of temporarily blocking web users after exceeding the failed login limit, the two new columns have been added to the user's table (FailedLoginCount and Locked). See Temporarily Block Web User for Failed Login Attempts for more information. 

Connection Manager

Changed Removed the DevExpress MemData component that caches transaction statuses from the Connection Manager and replaced it with JSON functionality.

Fixed issue where the updater may cause a hang-up in the Client if it receives a 404 response when trying to download the update executable. Bug# 4007


Fixed an issue that would generate an Undo Shipped error "Received unexpected undo shipped message for transaction from [lender symbol]" when an item was Checked In from a lender with a lowercase lender symbol. Bug# 3989

Decision Support for Request Processing


The Decision Support Pipeline (DSP) combines the power of addons, pipelines, stages, business rules, and routing rules to gather data from external systems in an effort to help make better fulfillment decisions and automate the borrowing request process for both articles and loans. 

For more information, see the new DSP articles below: 

New addons supported by DSP:


As a part of the 9.1 update, the ILLiad client installer will update the DOCLINE scripts to accommodate the URL change which will occur on January 1st, 2020. For information on this change, please see the DOCLINE FAQ.


Added support for handling requests placed using the "Place Requests - PMIDs" borrowing option. If the request is placed through the DOCLINE web interface, the lending library will receive a separate transaction number for each item requested. Since each DOCLINE request must be associated with a single ILLiad request, multiple borrowing requests using the Place Requests - PMID is not supported.


The DOCLINE scripts (v3.2) have been updated to use the new DOCLINE URL The DOCLINE scripts will be updated as a part of the 9.1 update. 


Removed the DOCLINE username and password customization keys since DOCLINE 6.0 no longer allows for automatic authentication into the website and requires each user to have a unique username and password.


Fixed issue where the default shipping option value for articles in Docline is being set to the default shipping value of loans. When the lending library imports the lending request, it imports the LenderAddresses. The DefaultShippingMethodLoan value was being placed into the Transactions.ShippingOptions field instead of using the LenderAddresses.DefaultShippingMethodArticle value. Bug# 4028



Fixed issue where the email and SMS template tag processor does not properly handle parameters that have a right angle bracket. The RegEx used assumes the first right angle bracket is part of the tag instead of a bracket inside the tag parameter. Bug# 1470



The ISO Service requires a manual upgrade after the 9.1 update due to the new database configuration and the OpenJDK bundle. For instructions on upgrading, see 9.1 ISO Service Upgrade.

  • Database Configuration: The ILLiad 9.1 ISOService has been changed to connect to the ILLiad database using the SQL DBC file. 
  • OpenJDK: The ILLiad 9.1 ISOService no longer requires Java 8 to be installed on the server. The ISO Service is now bundled with the OpenJDK (an open-source implementation of the Java platform) and does not require an Oracle Java license. 

As a part of the configurations, new installs of the ISO Service Manager will be installed via a ps1 PowerShell script instead of the InstallService.bat.


Fixed issue where the ESPNumber and InstitutionSymbol are not being set on outgoing ISO requests resulting in the error message "Could not execute JDBC batch update". Bug# 1453



Updated the Odyssey Manager to check if the lending library is a Trusted CopyrightPayer. If the lending library is a CopyrightPayer, then the CopyrightAlreadyPaid field will be checked. Bug# 4491



Enhanced RAPID/RAPIDR integration with live RAPID status updates, support for variable due dates, ability to share RAPID symbols in Shared Server setups, and capability to determine if the lender has shipped an item through the RAPID API. Note: Most of these feature enhancements (e.g., live status updated) require both the lending and borrowing institutions to have updated to v9.1 to utilize. For more information, see the ILLiad 9.1 FAQ under the RAPID heading. 

Staff Client

Changed Removed the Atlas Systems and OCLC ILLiad web links from Systems ribbon.
Changed Removed the OCLC Resource Sharing Settings interface within the client (the interface used to change Custom Holdings Paths, Custom Holdings Groups, Constant Data, and Direct Request Profiles) and replaced it with a button that links out to the OCLC Interface where the updated settings can be located. This allows OCLC to rapidly change the Service Config without having to maintain a duplicate interface or breaking ILLaid until an update can be released.
Fixed Fixed issue where the transaction status that displays in the lower left-hand corner of the Client status bar on a request form is not visible when using some skins due to the color contrast with the default black text. Bug# 4166
 Fixed Fixed issue where the Outgoing Notification grid columns reset their size whenever the Outgoing Notifications are closed or the client is restarted. Bug# 3927
 Fixed Fixed issue where closing the client after switching sites using `Login as...` caused an error pop-up and would sometimes cause a temporary crash in ILLiad client. Bug# 3980
 Fixed Removed several deprecated OCLC WsKey URLs from messages as a result of the shortened OCLC domain causing the missing WSKey prompt in the Client. Bug# 3788 
Fixed Fixed issue where the DocDel form would not save grid layout customizations in the Staff Client. Bug# 3758
Fixed Fixed issue where grouping a column row by a field (e.g., username) in Document Delivery (DD) Stacks Searching would prompt an error message in the Client. Bug# 4172
Fixed Fixed issue where the "TransactionNumber could not be determined from the OCLC request." error appears when a staff user clicks the Show button on a borrowing request that is linked to an OCLC request in the Cancelled status. Bug# 3595
Fixed Fixed the error dialog message for requests that have been resubmitted with a previous OCLC status of Cancelled. The error message will now include a more descriptive message instead of saying"Nullable object must have a value". Bug# 3594
Fixed Fixed issue where the OCLC Request form would not properly open for completed requests if they have a WorldShare ILL Status of Closed and disposition of Supplied. Bug# 3787
Fixed Fixed issue where the spaces  at the beginning or ending of a password were being trimmed off in the web but not in the client. Bug# 4490
Fixed Fixed issue where the ClientUpdateLocation Customization Key does not allow index files with names other than "ClientUpdates.xml". Bug# 4006

Staff Customization Manager

New Added SLPasswordResetInvalidEmail, a status line customization key that displays when a user attempts to reset their password with an unknown or invalid email address.
Changed Changed the value requirements for the SLPasswordResetEmailConfirmation customization key. To ensure the privacy and security of the user account, the value for the SLPasswordResetEmailConfirmation and SLPasswordResetInvalidEmail customization keys must match. This will prevent ILLiad from revealing if an account exists for that particular email address.
Changed The ServerAddons Table has been removed from the database since it was replaced by the Addons Table in the 8.7 release and will no longer be used.
 Fixed Fixed issue where dragging the last server from the included listbox to the available servers listbox and then saving during a ZSearch with no included servers would cause an error in the Customization Manager. Bug# 1456
 Fixed Fixed issue where creating or editing a Z39.50 server would not clear the yellow highlighted indicator in the modified ISSN search field after changes are saved in the Customization Manager. Bug# 1481

Staff Manager

Fixed Fixed issue where database connection problems would result in an 'Unhandled Exception' error upon startup of the Staff Manager. Bug# 3775
Fixed Fixed issue where status messages were showing up multiple times on the bottom status bar of the Staff Manager. Bug# 3826

Web Interface

New New fully accessible and responsive web pages that adhere to WCAG 2.1 & Section 508 compliance. The new web pages are not installed automatically to prevent overwriting any customizations your institution may have created. The complete set of 9.1 webpages are available for download on the ILLiad Downloads. For more information, see ILLiad 9.1 Fully Accessible and Responsive Web Pages

Hidden user fields are no longer required on HTML forms to preserve the values in the user record. The DLL will only update the data in the database for user fields that exist on the HTML form instead of updating al the fields. 

Fixed Fixed issue where in some cases ILLiad users can login unprompted for password change if WebAuthType=RemoteAuth and users AuthType=Default. Bug# 4214

Web Platform

Changed Changed the name of the Web Report RequestSentByHour's filename when exported. The filename prefix was being set incorrectly to 'RequestsSentbyDay' instead of 'RequestSentByHour.' Bug# 2764
Fixed Fixed issue where the ElecDelTurnaroundTime WebReport would cause an error when attempting to download the report due to a visible ungrouped date column. Bug# 2765 

Fixed issue in Web Reports where the Article Details Grid will leave the transaction parameters blank for the Turnaround Time Reports when exported to excel. Bug# 3931


Fixed an ILLiad and Aeon integration issue that was causing the ExternalRequestController to error out when checking for an Aeon status that had not yet been created in Aeon. The ExternalRequestController will no longer check the Aeon status if the ExternalID is set to null. Bug# 3829


ILLiad 9.1.x Point Release Notes

16 January 2020 (9.1.1) Server & Web DLL Release

In conjunction with the Web DLL release, a revised set of web pages that adhere to the changes mentioned below are now available for download on the ILLiad Downloads page.

Fixed Fixed a bug that was preventing RAPID Lending requests from downloading correctly for shared server sites who share a RAPID symbol but have different branches. 
Fixed Fixed the document type tag to mitigate the potential risk of cross-site scripting (XSS) in the ILLiad web pages. 
Fixed Fixed how ILLiad handles the HTTP headers to mitigate the potential risk of cross-frame scripting (XFS) in the ILLiad web pages. The Customization Key HttpContentSecurityPolciyHeader was added to add the Content Security Policy header to responses from the webserver. The Customization key HttpXFrameOptionsHeader will add the X Frame Options header. The values for the key are deny, sameorigin, and allow-from (uri).
Fixed an issue where the ILLiad WebAlerts may contain HTML tags in both the title and the body of the message.

There are no special styling requirements for these elements; therefore, adding HTML to the WebAlert message will change the default styling.

Fixed the Automatic User Creation feature to include support for user notifications preferences. 

  • The Notification Method for all users will be set to Electronic by default unless an alternative value is passed through when a request is submitted. The default can be changed to one of the acceptable values of Phone or Mail by adding an entry to the RemoteAuthValidation table. 
  • The Account Notification Preferences (e.g., account cleared) and Request Notification Preferences (e.g., item shipped) will be set to Email by default for all new users. The default can be changed to Text/SMS by adding an entry to the RemoteAuthValidation table.



If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation: