When staff force a password is forced reset from the client for a web user, pressing the submit button successfully changes the password, BUT it reloads the change password page with blank values and without a status message stating the password has been successfully changed.

v9.1
Bug# 4795

This issue can be identified by the borrowing system error: "Received unexpected undo shipped message for transaction from [lender symbol]".

The issue occurs if the current lender of the request (in OCLC) is the same that was stored on the request when it was shipped and checked in and, the value in OCLC is stored as lower case but the value in ILLiad is stored as uppercase. This causes the request to not match and prompt the undo shipped note.

Workaround: Some sites have reported that changing to another skin and back to original skin allowed Login As to work again.

The Client Error log may say the following: A thread exception has occurred.
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

Bug#3980

External systems running on the user's machine such as McAfee AntiVirus can affect web traffic. Since Docline is running through the web, users may receive a script error upon login. If the user clicks No or closes the script error, they will receive a blank Account Type box.

Bug# 4111
v8.7.3 and Docline 6.0

When dragging the last server from the included listbox to the available servers listbox and then saving, an error will occur.

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

v9.1
Bug# 4808

RAPID Lending requests are not downloading correctly for shared server sites who share a RAPID symbol but have different branches.

v9.1
Bug# 4834

The HTTP headers could potentially pose a risk of cross-frame scripting (XFS) in the ILLiad web pages.

v9.1
Bug# 4848

Document type tag can be a potential risk of cross-site scripting (XSS) in the ILLiad web pages.

v9.1
Bug# 4766

v9.1
Bug# 4867