ILLiad Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. PDF Document Processor prevents PDF from being closed until the Client is closed

    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.

    Bug# 8578

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

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  3. Blank Password in Client Forms Prompts Error Message

    A blank error message pops up when you:


    1. Open ILLiad Client

    2. Enter a valid username

    3. Leave password blank

    4. Attempt to login

    Bug# 8363

    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  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  4. Clones original request instead of request with staff changes

    When the user goes back into the web and clones the request again, it takes them back to the loan request page and submits a loan request without any changes staff made to the original request. This occurs for situations where a user creates a loan request on the web and staff changes the loan request to an article request and updates the doctype, then fulfills the request.

    Bug# 8345

    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  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 →
  6. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    0 comments  ·  Addons  ·  Flag idea as inappropriate…  ·  Admin →
  8. Order of Web Alerts

    There is no specific ordering that determines the way the web alerts appear within the client.

    Bug# 6725

    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  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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 →
  10. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    0 comments  ·  Docline  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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  ·  OCLC  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 →
  14. The On Reserve and Publisher Embargo reasons for cancellation do not display properly in OCLC

    The following lending reasons for cancellation do not properly display in OCLC:

    11 – ONRESERVE
    25 – PUBLISHER
    EMBARGO

    ILLiad 9.1 uses WorldShare version 2.1 which does not include support for the OCLC Reasons for No numbers 11 and 25. The WebService works properly from WorldShare to WorldShare but not with ILLiad to WorldShare or WorldShare to ILLiad.

    Bug# 5932

    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  ·  OCLC  ·  Flag idea as inappropriate…  ·  Admin →
  15. Application menu button is not visible when using Office 2019 skins

    The default white hamburger is not visible against the white background of the skin. This bug impacts the client, staff manager, and customization manager.

    v9.0 & v9.1
    Bug# 5890

    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  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 →
  17. 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 →
  18. Long Routing Matchstring (e.g., over 40,000 characters) Disappears Visually

    When copying and pasting a long matchstring (e.g., over 40,000 characters) into the Customization Manager, the match string will disappear after clicking out of the field and then saving. The matchstring will still work; however, you won't be able to see the entire matchstring in the field.

    Bug# 4649

    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  ·  Customization Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. Disposing Article Exchange Processor error

    The Odyssey Manager does not correctly dispose of its ArticleExchangeProcessor after processing Article Exchange due to the ILLiadOdysseyManagerHost.ArticleExchangeTimerTimer functionality.

    Bug# 5454

    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  ·  Odyssey Manager  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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  ·  Staff Client  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4

Feedback and Knowledge Base