ILLiad 9.1 FAQ

Print Friendly and PDF Follow

In this article, we will go over frequently asked questions pertaining to the ILLiad 9.1 update. For a list of Features and Fixes in the 9.1 update, see the ILLiad 9.1 Release Notes

Updating to ILLiad 9.1

How do I receive updates when new versions or point releases of ILLiad are made publically available?

Atlas Systems provide release updates through the following modes of communication:

ILLiad Community Forum:

ILLiad Client

Why was the OCLC Resource Sharing Settings interface removed from the client?

The ability to directly change WorldShareILL Settings (this includes functions like Custom Holdings Groups & Paths, Direct Request Profiles, and Constant Data) has removed from Client and replaced with a new button on the System Ribbon that links out to the OCLC Service Configuration. This allows OCLC to rapidly change the Service Config without having to maintain a duplicate interface or breaking ILLiad until an update can be released. 


How do I change the OCLC Resource Sharing Setting since the interface was removed from the ILLiad client?

You may need to contact OCLC to get credentials to access Service Configuration if you have not accessed it previously. These credentials are different than the 9-digit authorization number and password that you used previously.

New, Fully Accessible and Responsive Web Pages 

Will the new default web pages overwrite any customizations I may have on my current web pages?

No, the web pages are not installed automatically during the update. A complete set of 9.1 web pages will be available for download on the ILLiad Downloads page when v9.1 is released. Having the web pages downloaded separately from the update installers prevents overwriting any customizations your institution may have created. 

When updating your web pages, please download the new default web pages and move any customizations you may have from your old web pages to the new defaults. 

If you have any questions or require Concierge Services when implementing the new web pages, please contact support at

What customizations will Concierge Services perform if I request assistance in migrating my old web pages to the new defaults? 

Concierge Services can make the following changes to help you brand the new web pages:

Change the logo
Change the name of fields
Add additional fields (does not include drop-down menus)
Change background and font colors
Change font style

For questions regarding Concierge Services or to request a quote for a web tune-up, please contact Please note, additional customizations may be approved for the web tune-up under the circumstances that it will not prevent the web pages from being WCAG compliant or break mobile accessibility. 

Where can I find the Voluntary Product Accessibility Template (VPAT) for the new default web pages?

For a copy of the most up-to-date VPAT, see About ILLiad- Including Frequently Requested Documentation (e.g., VPAT).

If my institution doesn't allow patrons to request a patent, report, or any other request form, can we delete or change the name of the request forms? 

Yes, you may delete or change the names of any default request form. Please bear in mind each form has its own set of default fields designed specifically for that particular type of request and how the  DLL passes those fields into the database. You may have to change field names, add fields, or delete fields to match your new request type. 

Can I add fields to the request form that used to be in the default web pages that are no longer in the new web pages?

To add a hidden field back to the request form, remove the comment <--! --> tags. Any of the removed fields (e.g., Not Wanted After Date) may also be added back to the request form; however, these fields will not be in the default web pages.

Can I add extra fields to a request form? 

You can customize the request form to add additional available fields such as PMID or DOI, or use one of the blank item info (e.g., ItemInfo1) fields to add a custom field for any other desired information.

Can the "required" field note be changed on the request form?

The red required field note is just plain text; therefore, it can be removed, the verbiage can be changed, the text color can be changed, and the required text can be added to additional fields. The required notes are also populated based on the FieldNames that have been checked as required in the WebValidation table. 

Will the new Multimedia form have the DLL actions to handle the form fields?

Yes, it will be treated as a default form, unlike the generic "Other" form which has been removed as a default request form.

Is there a different max character limit for the alert heading since it has been moved from the side of the web page to the top of the page?

The max character limit has not changed from the default 255 character limit.

Can a link be added to a user or system alert?

Both system alerts and user alerts allow for clickable links in the body of the message.

Can we change the headings? For example, Electronically Received Requests?

Any text such as headings, fields, alert messages, etc. can be customized. These pages are just as customizable as the previously existing pages. The new default web pages are built on Bootstrap 4.

What happens if a patron if not able to renew an item?

The button will remain visible in the request details so patrons can see where to go if they were able to renew a request; however, the button would be greyed out so they can't actually click the button.

Can I hide one or more of the navigation bar items? 

Yes, any of the navigation items can be hidden or removed. For example, institutions, where users are authenticated into ILLiad through an external system and their contact information is automatically imported over may want to hide the Profile tab so users only have to maintain contact info in one system. 

Enhanced RAPID / RAPIDR Integration

Why is the request being set to Shipped instead of Filled?

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.

Where can I find documentation on the RAPID changes?

For information on the live RAPID status updates and the use of the RAPID API, see Processing: Rapid Borrowing Request. Note: To take advantage of this feature enhancement, both the borrowing institution and the lending institution need to be utilizing v9.1 for the History/Tracking to be updated properly.  If either the borrower or lender is using an older version of ILLiad, the statuses will not be shared.

For information on shared RAPID symbols/accounts for shared server systems, see Initial Configuration: Enabling the Rapid Manager

For information on variable due dates, see Processing: Rapid Lending Requests.

Decision Support for Request Processing    

Does the DSP feature support lending processing?

The DSP feature currently only handles the borrowing request process but we hope to build more pipelines in the future that support lending and document delivery. 

Will this break my legacy addons?

No, the legacy addons will act as they normally would. If you wish to integrate any of these addons into the decision support pipeline, see DSP Addon Development for a guide explaining the addon requirements to be supported by the DSP feature. 

Will Atlas be creating any additional addon for the DSP in the future?

Yes, Atlas plans on developing more addons in the future. In conjunction with the 9.1 release, Atlas has developed 3 addons that are supported by the DSP feature  (Open Access, DOI, and Reprints). If there are any particular addons you would like to see in the future, please submit your idea to UserVoice. For example, a CCC GetItNow addon, a Z39.50 addon, or an addon the checks for the PMID. To get a jump start and develop your own addon for the Decision Support Pipeline, see DSP Addon Development for more information. 

Is there a character limit for the Match String?

The business rules match string is unlimited for those who want to create complex rules. 

Can business rules be set without having them automatically sending the request?

Selecting Recommended for the Rule Type will run the addons through the pipeline(s) to gather information and provide the best option based on your business rules without sending the request. The Pipeline Request Review form allows staff to review the information and select the recommended option or an alternative option. This screen will provide a better understanding of why ILLiad chose a particular fulfillment option by displaying the fulfillment data gathered from each addon. Once you are more comfortable with the business rules and how the feature handles the process, you can easily switch a business rule from recommended to automatic. The recommended vs. automatic is set per business rule. This way you can have a rule automatically send the request if you have the item in your holdings but review a request that will require paying royalties. 

Is it possible to bypass the CCC screen for the awaiting Copyright Clearance?

The Borrowing Article Pre-Copyright pipeline stops at the CCC screen during the pipeline because there isn't an easy way to bypass copyright. The CCC screen offers several decision considerations such as applying the rule of 5, fair use guidelines, or handling requests with high royalty fees. Processing requests in this screen helps gather information from the CCC to be compared against fulfillment information from other external systems. Obtaining the most information possible allows ILLiad to make the best decision based on your business rules. During development, it was decided to stop at the CCC before continuing through the rest of the pipeline was the best way to ensure the feature wouldn't violate any institution's copyright requirements. 

Would the DSP feature interrupt the Rapid workflow or any other workflows in ILLiad?

The feature could potentially skip parts of your Rapid workflow if you have a routing rule that goes around a queue that the Rapid service normally picks up requests from. Out of the box, the feature should not skip over the Rapid Workflow. It is recommended to check which queues other workflows may use and modify your routing rules and/or business rules to accommodate the DSP feature and the other services. For example, you can create a business rule with the Target Type of Queue and a Target of Awaiting Rapid Request Sending for Rapid Requests that are in the Borrowing Article Pre-Copyright Pipeline and meet your custom business rule criteria. This would ensure your request does not skip over the Rapid workflow if Rapid meets your business rule criteria (e.g., cheapest, fastest, etc.). 




If this article didn’t resolve your issue, please contact Atlas Support for assistance:

Contact Support