ILLiad Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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# 7847

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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# 7172

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  6. Extra closing div tags in ILLiad 9.1 Default Web Pages

    The web pages with extra div tags include:

    EditArticleRequest
    EditBookChapterRequest
    EditConferencePaperRequest
    EditGenericRequestTesting

    Bug# 6022

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  7. Web alerts not appearing for Status and Delivery Location

    Web alerts for Status and DeliveryLocation don't appear on the web pages for users to when generated through the use of the AJAX (https://support.atlas-sys.com/hc/en-us/articles/360039292194-Performing-an-AJAX-Request-to-View-Customize-Web-Alerts).

    Workaround: Adding the <#ALERTS> tag will show all of the alerts (see attached image)

    v9.1
    Bug# 5893

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  8. Routing in Scripting can be overwritten by SaveDataSource

    In an ILLiad addon:

    When you make changes to transaction fields, route the transaction and then SaveDataSource it will undo the Route action.

    Workaround: This can be avoided by saving before routing.

    Bug# 4681

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  9. Web validation rules for required fields don't account for 'NULL' special value

    The ILLiad web DLL will perform special handling for text values equivalent to 'null,' replacing them with an actual null value when it updates the database.

    Bug# 4602

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  10. In the web, 'null' is a special string that can prevent some valid data from being inserted, specifically as a user last name.

    ILLiad does a case-insensitive comparison of the field value and will treat a user record with the LastName of Null as null when it updates the database.

    Bug# 4601

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  11. The renewal button in the ILLiad web pages may be enabled even if the due date is outside the renewal window

    The renewal button doesn't consider the due date and the RenewalWindowDays/RenewalBeforeWindowDays customization keys when determining if the button is visible in the web pages.

    Bug# 4571

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  12. The BillingInformation table in the Lending Web Pages will not display if BillingActive is set to false

    The lending web pages prevent the display of the billing information table when BillingActive is set to false.

    Workaround: If BillingActive is set to BillingActiveLending, then the BillingInformation table will always display in the lending web pages.

    Bug#4444

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  13. Lender password change from client only changes the password for NVTGC logged into client

    When a user changes a Lender's password from the ILLiad client, it only changes the password for the NVTGC that the user is logged into the client under, instead of changing it for all NVTGCs. As a result, the lender may be able to log into the client under that particular NVTGC but unable to log into the web.

    v9.0 & 8.7
    Bug# 4436

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  14. SLLoginFailed not showing up for invalid Username on Forgot Password

    The invalid username status line doesn't seem to be triggering the SLLoginFailed customization key on the Forgot Password page. The status line does appear if triggered on the logon pages.

    v9.0 & 8.7
    Bug#4147

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  15. 0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  16. Change Password form does not have correct tab ordering for the ForcePasswordReset checkbox

    The Force Password Reset checkbox does not have the focus prior to the Ok button for proper Top->Bottom & Left->Right expectations. v9.0.3

    0 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  17. ILLiad- Statuses do not alert screen readers about the problem on the page (incorrect password, failed validation, etc)

    It is very confusing to fail validation while using a screen reader because it isn't apparent that validation failed.

    It should likely alert the user on page reload.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Flag idea as inappropriate…  ·  Admin →

Feedback and Knowledge Base