ILLiad Known Issues
143 results found
-
Routing rule errors may be misleading in the logs Routing rules errors are logged as "Invalid match string" errors even when the error is not caused by an issue with the match string.
Bug# 26555
1 vote -
Docline Lending Request Import excludes certain formatted data 'Pages' and 'Issue' values are not properly imported from the 'Citation' section of incoming Docline lending requests if these values are not formatted in a specific way. The page range for the 'Pages' value must be formatted with a hyphen (e.g., 123-126) and the 'Issue' value must be formatted as a single numeric value to properly import.
Bug# 27806
1 vote -
Request data may be lost when a request is submitted after the user's NVTGC is changed If a user's NVTGC is changed while the user is filling out a request on the ILLiad web pages, the request will still be submitted when the user clicks the Submit Request button, but the data the user entered into the request form will not be saved to the request.
Bug# 27212
0 votes -
Ampersand in username causes error in ILLiad web pages when viewing PDFs If a user has an ampersand (&) in their username, they are unable to view PDFs on the ILLiad web interface and receive the following error:
"Error: You may only view transactions that belong to you."
Bug# 27622
0 votes -
Default entry in WorkFormMapping table is missing closing ">" symbol The default entry in the WorkFormMapping table for WorkFormType "OCLC Article" and OCLCFieldName "volume" is missing the closing ">" symbol in the default value configured in the ILLiadFields column ("<#PhotoJournalVolume").
Bug# 27320
0 votes -
WebView2 dependency of ILLiad Client installer attempts to run even if WebView2 is already installed Attempting to install the ILLiad Client with Powershell and SCCM causes issues during the WebView2 installation even if WebView2 is already installed on the system before installing the ILLiad Client. This issue prevents the client installation from being completed.
Bug# 26820
0 votes -
The Atlas Authentication Portal is missing the log configuration file The Atlas Authentication Portal has support for logging, but is not currently distributed with the necessary App_Data folder and log.config file to enable logging.
Bug# 26220
0 votes -
Z39.50 may duplicate item records for holdings Z39.50 will pull in any hardcoded holding elements in the XML for a holding record, which can cause the first item listed in the record to be duplicated in ILLiad.
Bug# 25965
0 votes -
Submitting an OpenURL request as new RemoteAuth user can lead to a blank form submission In a Shared Server setup, requests submitted via OpenURL by new RemoteAuth users may be blank after the user creates their account and submits the request form.
Bug# 25395
0 votes -
Timestamps may be inconsistent for actions performed via the ILLiad web interface The date-times used on Transaction and other records to record timestamps for actions performed via the ILLiad web interface (e.g., updating Transaction Status) may be inconsistent in value when the server timezone differs from the database timezone.
Bug# 25157
0 votes -
Invalid routing rules cause error during custom routing When a request's transaction status is changed, ILLiad will loop through active routing rules and check for a rule matching the request's TransactionStatus and ProcessType, and then apply the rule when appropriate. However, if that routing rule is invalid because it has null fields (e.g., a null value for TransactionStatus, ProcessType, MatchString, NewTransactionStatus, or NewProcessType), an error will be logged and the routing process will fail.
ILLiad should instead check to ensure the routing rule is valid before applying the rule to the request and, if the rule is invalid, provide detailed information in the ILLiad Client log to state…
0 votes -
Routing rules can be created with only a rule number entered The ILLiad Customization Manager allows new routing rules to be added to the Routing table with only a rule number entered and all other required fields for the rule left blank.
Bug# 25295
0 votes -
Lending shipping label printing will not apply sort settings Lending shipping labels will not be sorted by the sort settings configured in the Print Configurations form of the ILLiad Client when printed.
Bug# 25067
1 vote -
Connection Manager logs warning intended for shared server sites for single server sites upon restart The ILLiad Connection Manager will log a "Cannot find User views. Verify ILLiad account has permissions to all User views." warning message for single server sites when the Connection Manager service is restarted.
Bug# 24685
0 votes -
ILLiadAuthUserRegistrationEnabled customization key does not work if the WebAuthType key is not set to ILLiadAuth Setting the ILLiadAuthUserRegistrationEnabled customization key to No does not disable ILLiadAuth user registration unless the WebAuthType key is set to ILLiadAuth.
This means that if a site is using LDAP, they cannot prevent ILLiadAuth user accounts from being created by setting the ILLiadAuthUserRegistrationEnabled key to No.Workaround: Remove or rename the FirstTimeUsers.html page so that patrons cannot get there to click to get to the NewUserRegistration.html page. Optionally also rename/remove the NewUserRegistration.html page.
Bug# 25019
1 vote -
ILLiad SAML Module overwrites multiple values for same attribute If multiple values are received for the same SAML attribute, the ILLiad SAML module will overwrite those values in the order received instead of concatenating them.
Bug# 24338
0 votes -
Deleting a DSP addon that is used in business rules causes database constraint error Attempting to delete a DSP addon that is being used as a target in DSP business rules will trigger the following database constraint error message in the Customization Manager:
'Error deleting server addon. The DELETE statement conflicted with the REFERENCE constraint "FKDecisionSupportPipelineBusinessRulesAddonTarget".'
Bug# 23937
0 votes -
Rapid Manager initializes new lender records with NULL values for Odyssey trusted sender settings In some cases, Rapid Manager will create new lender address records with NULL values set for TrustedSender and TrustedSenderOverride, which can break the logic to determine if a given sender is trusted if there are many records that have the same URL for the Odyssey IP. This is because the code will use the IP address associated with an incoming request to look up all lender address records using that same IP address as their Odyssey IP rather than looking up address records based on the symbol.
In the case of items sent by RapidX, there can be hundreds of…
0 votes -
Byte arrays passed to .NET methods are converted to null due to an NLua bug Byte arrays (often referred to as Byte[] in Microsoft's .NET documentation) passed from Lua to .NET methods are converted to null, causing those .NET methods to fail when included in addon code.
This is a known NLua bug present in the version of the NLua component used by the ILLiad application, detailed here: https://github.com/NLua/NLua/issues/438.
Bug# 24017
0 votes -
Rapidly clicking Docline buttons can cause ILLiad Client to crash Clicking a button on the Docline interface three or more times in rapid succession causes the ILLiad Client to crash when the WebView2 browser control is used.
Bug# 23031
0 votes