ILLiad Known Issues
122 results found
-
UserNotificationPreferences are not initialized for new users created through Automatic User Creation v9.1
Bug# 48080 votes -
RAPID Lending requests are not downloading correctly for shared server sites RAPID Lending requests are not downloading correctly for shared server sites who share a RAPID symbol but have different branches.
v9.1
Bug# 48340 votesReleased in ILLiad version 9.1.1.
-
HTTP Headers The HTTP headers could potentially pose a risk of cross-frame scripting (XFS) in the ILLiad web pages.
v9.1
Bug# 48480 votesReleased in ILLiad version 9.1.1.
-
Document Type Tags Document type tag can be a potential risk of cross-site scripting (XSS) in the ILLiad web pages.
v9.1
Bug# 47660 votesReleased in ILLiad version 9.1.1.
-
Lending Returns will not refresh OCLC status v9.1
Bug# 48670 votesReleased in ILLiad 9.1.2
-
Change Password submission does not display status line for passwords successfully changed 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# 47950 votesReleased in ILLiad 9.1.2
-
Some Customization Keys do not have a description explaining its purpose The following Key do not have a description in the Customization Manager:
RenewalWindowDays
ISOCanSendReceived
ISOCanSendReturned
ISOCurrencyCode
ISOMonetaryValueBug# 4569
0 votesreleased ·
AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
Released in ILLiad 9.2
-
CopyrightPayer check not done by Odyssey Manager during Check In The Odyssey Manager does not check to see if the Library is a Trusted CopyrightPayer so the CopyrightAlreadyPaid checkbox never gets checked when the file has been received. As a result, the Journal Titles received from a Copyright Payer end up on the Copyright Reports.
Bug# 4491
0 votesReleased in ILLiad 9.1
-
Spaces at the beginning or ending of a password are trimmed off in the web but not in the client The DLL is trimming any leading or trailing spaces from the password field within the web, whereas the client just runs the password as it's entered with the spaces. For example, if my password is "ABC" when logging in the client "ABC " fails, whereas it works in the web pages because the space is being removed.
Note: A space can exist within the password itself, e.g., "P@ss W0rd", as long as it's an accepted requirement in the Customization Manager. The spaces within the password will not be trimmed by the DLL.
Bug# 4490
0 votesReleased in ILLiad 9.1
-
0 votesreleased ·AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
Released in ILLiad 9.2
-
The generateuser call appears to fail when creating a new user from an import email request The email import behavior when creating a new user from an import request with the EMailImportAutoUserRecord set to yes will cause the generateuser call to appear as though it has failed, but the request is still imported, and assigned to a default user
Should also be noted that this process works correctly when the user already exists in the system. This is only occuring when AutoUserRecord is set to yes, and the Username value from the email does not exist in the database.
Bug# 4441
0 votesreleased ·AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
Released in ILLiad 9.2
-
Docline scripts not importing patron name if it is in the imported info Bug#4263
v9.0.3 & 8.7.30 votesReleased in DOCLINE 3.1.2.1 Scripts
-
ILLiad users are not prompted for password change after 9.0 update When a user who has an ILLiad login and an AuthType of Default tries to log in to the ILLiad web pages when WebAuthType=RemoteAuth, they are able to log in without being prompted to change their password (when trying to log in for the first time after the upgrade).
v9.0
Bug#42140 votesReleased in ILLiad 9.1
-
Grouping by field in In Document Delivery (DD) Stacks Searching causes error An error message/feedback pop-up will appear when a staff user attempts to group transactions by a field (e.g., username) in dd stacks searching. The log will record this error as "Transaction number 0 not found".
v8.7 & 9.0
Bug# 41720 votesReleased in ILLiad 9.1
-
Some specific parameter settings may cause Index and Length Server Error Workaround: Try different numbers in the parameters of the report.
0 votesreleased ·AdminBrittany de Gail
(Technical Writer/Content Developer, Atlas Systems, Inc.)
responded
Released in ILLiad 9.2
-
Login as... error causes an error popup and sometimes crashes the client 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
0 votesReleased in ILLiad 9.1
-
0 votes
Released in ILLiad 9.1
-
TemplateProcessor for emails does not handle parameters that have a right angle bracket The RegEx used assumes the first angle bracket as part of the tag instead of a bracket inside a tag parameter. This impacts email and SMS templates.
v8.6
Bug#14700 votesReleased in ILLiad 9.1
-
External Request Controller is checking for the Aeon status even if ExternalId is null The ILLiad ExternalRequestController is attempting to retrieve statuses for external requests that had never been created in Aeon. The check is parsing the ExternalID as an integer but when null, fails.
This error occurs with Aeon and ILLiad integrations.
v8.7.2
Bug# 38290 votesReleased in ILLiad 9.1
-
0 votes
Released in ILLiad 9.1
