Clicking the "Cancel - Return to Logon" button on the NewAuthRegistration.html page doesn't allow users to stop the request form and return to the logon menu.

Bug# 12648

When using the Reprints Desk Unmediated Server Addon, the Estimate ID is sometimes added to the ILL Number field instead of the Order ID.

Bug# 11345

ILLiad Lending datarowDefaultRequest and includeTransaction menu contain duplicate classes.

Bug# 10147

An empty string would be produced when the persist value drop-down in the atlasUtility.js due to the handling of the double-quotes.

Bug# 10061

Bug# 9673

​On user pages, delivery methods and "web" fields are set to display 'none' when the correct attribute needs to be:

<input type=hidden...

Bug# 8653

There is an extra span in include_TransactionMenu.html and any HTML files with the undelete button in the Templates folder.

Workaround- change this:

<a class="btn btn-light <#TRANSACTION field='RequestActionAllowed' name='UndeletePDF' disabledValue='hidden'>"href="<#ACTION action='21' type='11'>&Value=<#TRANSACTION field='TransactionNumber'>" class="menuUndeletePdf">
<span aria-hidden="true" <span class="fa-stack" style="vertical-align: top;">
<span class="fas fa-trash-alt fa-stack-1x"></span>
<span class="fas fa-ban fa-stack-2x text-danger"></span>
</span> Undelete Item
</a>

To this:

<a class="btn btn-light menuUndeletePdf <#TRANSACTION field='RequestActionAllowed' name='UndeletePDF' disabledValue='hidden'>"href="<#ACTION action='21' type='11'>&Value=<#TRANSACTION field='TransactionNumber'>">
<span aria-hidden="true" class="fa-stack">
<span class="fas fa-trash-alt fa-stack-1x"></span>
<span class="fas fa-ban fa-stack-2x text-danger"></span>
</span> Undelete Item
</a>

Bug# 9309

The default blocked user page needs to be updated to consistently look like other pages.

Bug# 7682

Some drop-downs in the ILLiad default pages are missing options.

Workaround - To add these options back into the default pages change this:

<select id="AcceptAlternateEdition" name="AcceptAlternateEdition" size="1" class="custom-select mr-sm-2">
<option selected><#PARAM name='AcceptAlternateEdition'></option
<option>No</option>
</select>

To this:

<select id="AcceptAlternateEdition" name="AcceptAlternateEdition" size="1" class="custom-select mr-sm-2" data-persistedValue="<#PARAM name='AcceptAlternateEdition'>">
<option>Yes</option>
<option>No</option>
</select>

Bug# 9383

v9.1
Bug# 7323

Lending web pages don't have an explicit request type tag/field and when an article request is submitted it's being reclassified as a loan causing the titles do not appear in the main menu.

v9.1
Bug# 5935

Editing a request in the lending web pages creates a duplicate request with the changes made instead of saving the changes to the original request.

v9.1
Bug# 5969

v9.1
Bug# 4765

The batch Copyright Clearance processing form would check to see if the request was at the 'Awaiting Copyright Clearance' status to ensure the request wasn't being processed by someone else simultaneously. When checking for the status of the request, ILLiad should have considered the 'Awaiting Copyright Clearance - Pipeline' status to also be a valid status. Instead, this status was seen as invalid and would prevent latter requests from being processed.

v9.0
Bug# 4930

LDAP users who attempted to create a new user after coming in through an OpenURL link are being sent to the Main Menu instead of the Request Page after registration.

v9.1
Bug# 5018

Custom queues are not added to the list of business rules as possible targets for shared server installations when utilizing the Decision Support Pipeline feature.

v9.1
Bug# 4961

In the 9.1 default web pages, some fields are not displaying at the correct width within the default web pages.

v9.1
Bug# 5062

The wrong ID (CurrentPassword) is being assigned to the Username field on NewUserRegistration form.

v9.0
Bug# 5066

The search button on the Navbar is green instead of utilizing the default blue for consistency. In addition, the size of the nav_search button needs to be adjusted for consistency.

v9.1
Bug# 5071

Custom statuses set in the DisplayStatus table (e.g., using "Ready for Pickup or Checked Out" as a display status for "Checked Out to Customer") would not display certain menu options (e.g., renew, clone, etc.) in the patron web pages because the <#MENU> tag would not read the custom statuses as a valid status.

v9.1
Bug# 5050