Skip to content

ILLiad Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

143 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Printing  ·  Admin →

  2. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  3. Copyright data can't be saved for requests in the Awaiting Copyright Clearance - Pipeline queue

    The "Save CCC Information" button can't be used to save copyright information for requests in the Awaiting Copyright Clearance - Pipeline queue.

    Bug# 18914

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Staff Client  ·  Admin →

  4. Format field value (e.g., DVD, CASSETT, etc.) on the Multimedia form does not save to database

    v9.1
    Bug# 5852

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Web Interface  ·  Admin →

  5. Odyssey Manager creates blank pdfs

    Odyssey Manager fails to convert large TIF files of approximately 1 GB to PDF. The log does not indicate a problem but shows the process occurring in just a few seconds.  The resulting PDF file is blank.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Odyssey Manager  ·  Admin →

  6. Unable to modify some ZServer configuration fields in Customization Manager for MARC records

    If a Z39.50 server configuration is set to use MARC  holdings, the availability fields become read-only. If you need to edit the availability fields, please contact your support representative so they can edit directly in database for you. v8.7 and v9.0

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Customization Manager  ·  Admin →

  7. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Web Interface  ·  Admin →

  8. Request cloning from the staff client will always set the RequestType to Article

    Repro Steps
    1. Open a loan request in the staff client
    2. Clone the request. The behavior is the same regardless of cloning to same user or different user and if the request is/is not opened after the process is completed.

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  9. Invalid characters in title error when submitted to OCLC

    Workform Mapping should be replacing invalid XML characters.

    Currently workform mapping handles replacement of \r & \n.

    Repro
    1. Create a borrowing request in the client.
    2. Via the database update an Article Title to include "&#x1F"
    3. Close the request form and re-open after the invalid characters are added.
    4. Search OCLC and attempt to send the OCLC request.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  OCLC  ·  Admin →

  10. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Web Interface  ·  Admin →

  11. Certain ILLiad default web page files contain unnecessary FORMSTATE tags

    In both the Borrowing and Lending default web pages, there are unnecessary FORMSTATE tags on web page files for request forms such as ArticleRequest.html, BookChapterRequest.html, etc.

    Bug# 25397

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  12. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  13. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Web Interface  ·  Admin →

  14. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Staff Client  ·  Admin →

  15. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Customization Manager  ·  Admin →

  16. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

  17. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →

  18. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Decision Support Pipeline  ·  Admin →

  19. 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.

    Bug# 23892

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Rapid Manager  ·  Admin →

  20. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Addons  ·  Admin →
← Previous 1 3 4 5 6 7 8

ILLiad Known Issues

Categories

Feedback and Knowledge Base

(thinking…)