ILLiad Known Issues
-
Web report dates cache incorrectly
Numbers in Lending Fill Rates and Lending Requests Received by SystemID and numbers in DocDel Fill Rates and DocDel Finished and Cancelled aren't matching up in the web reports. This is because dates are incorrectly caching by date and time rather than solely by date. This leads to the report grabbing an incorrect number of requests for a given range of dates if the start date or end date gets a time included.
Short-term workaround: Clear the cache to make sure the dates don't change.
Bug# 10598
0 votes -
Docline Login with Google authentication is not working
Google Authentication for Docline is not working properly in ILLiad 9.1. This is causing users to receive script errors or a message indicating the browser is not secure when logging in. The issue is a result of a conflict with Google's authentication. If you're experiencing issues with using a Google account, there are several other supported login methods.
See this article for information about the different login methods supported: https://support.atlas-sys.com/hc/en-us/articles/1500002760821
See this article to learn how to change your login method: https://support.atlas-sys.com/hc/en-us/articles/1500002870502
Bug# 10417
0 votes -
Duplicate classes on Lending pages
ILLiad Lending datarowDefaultRequest and includeTransaction menu contain duplicate classes.
Bug# 10147
0 votes -
Persist Settings bug if a search group is not selected
The "Error saving z39.50 persistent settings to registry" occurs if you don't have a default Z39.50 Search Profile/Configuration and open the request form.
Bug# 10020
0 votes -
FormClearUser doesn't populate Yes/No values for ElectronicDelivery field
The ElectronicDelivery field on the Clear User form does not have any default or selectable values in the dropdown, but will accept Yes or No if manually typed in.
Bug# 10281
0 votes -
Copyright reports are exporting as blank to Excel
v9.0 and v9.1
Bug# 9892
0 votes -
hangeUser Button Alignment
The alignment for the buttons at the bottom of ChangeUserInformationare set to be right-aligned by default. For consistency, these need to be left-aligned like in the NewRegistration page.
Bug# 7683
0 votes -
0 votes
-
Duplicate form submission does not work under remote authentication
Remote auth validation does not load the user's reported session id, duplicate form submissions aren't being prevented.
Bug# 9013
0 votes -
PDF Document Processor prevents PDF from being closed until the Client is closed - Error message 'file in use'
When a PDF has been loaded by a PDF Document Processor (on the scanning form or the electronic delivery form), the filesystem keeps a lock on that file until the ILLiad client is closed. This is because the processor is not closing the file.
Error Log Message Example: The process cannot access the file 'C:\Program Files (x86)\ILLiad\elecdel\o48034.pdf' because it is being used by another process.
Bug# 8578
0 votes -
ILLiad Client Overdues null reference exception error
In OverduesList.cs, the gridViewRequest_CustomColumnDisplayText function may throw a null reference exception when it attempts to call ToString() on e.Value.
Bug# 8564
0 votes -
Blank Password in Client Forms Prompts Error Message
A blank error message pops up when you:
- Open ILLiad Client
- Enter a valid username
- Leave password blank
- Attempt to login
Bug# 8363
0 votes -
DLL shows incorrect date/time on transaction notes
The date shows up correctly in the client and the database but not in the transaction notes.
v9.1
Bug# 78470 votes -
Webreports login crashes with wrong Username
The debug web reports log doesn't show anything for the crash, just stops logging.
See attached screenshot for an example error message.
Bug# 7688
0 votes -
Special characters in URL break search for Get It Now ILLiad addon
Special characters/diacritics in the Author or Title field of a transaction will break the search for the Get It Now addon. The characters appear as they should in the client, and the URL works outside of ILLiad, but when left in the fields the search breaks. Once the characters are removed/replaced it works fine.
Bug# 7600
0 votes -
Order of Web Alerts
There is no specific ordering that determines the way the web alerts appear within the client.
Bug# 6725
0 votes -
Adding new lines to the web alerts breaks the alert
When adding carriage returns, it breaks the JSON parse.
Workaround: Use a <br> tag before starting a new line to ensure the alert will display properly.
v9.1
Bug# 71720 votes -
Deleted OdysseyReceived Item Cleanup Error
Under System Manager > Cleanup.ProcessOdysseyHoldingsXmlFile, when the TransactionNumber is received from OdysseyReceived, it may return a null value if the record has not been matched to a transaction.
Bug# 6560
0 votes -
Docline Citation not importing volume/issue numbers.
The volume/issue and pages blank are not being imported when there are non-numeric values in the Citation field such as supplemental issues and e-page numbers.
Bug# 6539
0 votes -
0 votes