ILLiad Known Issues
149 results found
-
Changing layout of tabbed groups on Main Menu causes owner issue
Repro Steps
When splitting out the Borrowing, Doc Del, and Lending tabbed groups to all show, an error is shown and queues do not load properly when the client is opened.- Customize Layout on main form by right clicking on Borrowing and choosing customize layout. 2, Switch to the Layout Tree View. Choose the Requests tabbed group and right click and select "Ungroup Tabbed Group"
- Save the layout for the user
- Close/Reopen the client.
1 vote -
Some unicode characters are not properly encoded on OpenURL submissions if the user must log in first.
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.
2 votes -
UTF-8 characters are not decoded properly in some cases
For OpenURL requests, if the patron already has an active websession and do not have to log in the characters are correctly translated.
2 votes -
The ILLiad DLL does not correctly set more than one cookie at a time.
This is not actually a bug yet because the illiad.dll doesn't set more than one cookie at a time. However, if SetCookie() were to be called more than once it would overwrite the cookie custom header.
1 vote -
Request cloning from the staff client will always set the RequestType to Article
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.4 votes -
Need to remove ESPUpdate table entry for Received when the error is "Received not allowed here"
If we receive the error we should ensure that the ESPupdate is removed so that it will not attempt to retry since we already know that OCLC will consider it invalid based on it's current state.
1 vote -
Scan button too close to Article Exchange button leading to missends
I hate the location of "Article Exchange" icon in ILLiad It is located just to the left of "SCAN." Once again, I had to rescan a 30 page article because my curser slipped and the article sent without the last two pages, plus every other page was upside down, and nothing had been cropped.....so I called MND and told him that he would need to delete the article exchange in his email and I would start all over. He said "I understand" because I do the same thing about once a week. Please help and get the location of Article…
1 vote -
Invalid characters in title error when submitted to OCLC
Workform Mapping should be replacing invalid XML characters.
Currently workform mapping handles replacement of \r & \n.
Repro
1. Create a borrowing request in the client.
2. Via the database update an Article Title to include ""
3. Close the request form and re-open after the invalid characters are added.
4. Search OCLC and attempt to send the OCLC request.1 vote -
Information in ShippingAddresses is not updated with newer information if there is a lender conflict
Repro Steps
The ShippingAddresses table is populated with ReturnTo address information when ConnectionManager detects a lender has shipped material. In the event that a lender undo's shipped and a new lender supplies the material, the ShippingAddresses info on the borrowing side will contain the wrong ReturnTo address information since it is not updated in the event of a lender conflict.1.) UCW request a book from Lender-A
2.) Lender-A updates shipped but recalls book right away and perhaps never actually ships it
3.) UCW rerequests and is filled by Lender-B, which updates as shipped as expected.
4.) UCW checks in…1 vote