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

149 results found

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

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

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

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

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

    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 →

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

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

    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  ·  Docline  ·  Admin →

  8. Changes to the Location field dropdown selection on the Users to Clear form will revert if another dropdown is modified

    Changes to the dropdown selection in the Location field on the Users to Clear form will revert if the value of another dropdown on the form is modified.

    Bug# 23285

    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 →

  9. PDFs from HathiTrust experience visual bugs during import

    PDFs from HathiTrust do not properly display in the ILLiad Client's Scanning form during import and may contain visual bugs such as blank pages, but will send and deliver as expected in ILLiad 9.2.

    Bug# 22934

    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 →

  10. Error is returned in logs for PDF files using non-numeric filenames during ElecDel cleanup process

    When PDF files using filenames that contain non-integer values are handled by the ILLiad System Manager's electronic delivery file clean-up process, the following error will be returned in the logs:

    "ERROR AtlasSystems.ILLiad.SystemManager.Cleanup - ERROR PROCESSING C:\ILLiad\PDF<FILENAME>.pdf -- Skipping -- Could not parse transaction number from the filename.
    System.FormatException: Input string was not in a correct format.
    at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
    at AtlasSystems.ILLiad.SystemManager.Cleanup.ProcessPdf(FileInfo fileToProcess)"

    Bug# 22556

    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 →

  11. Improperly formatted routing rules can lead to email spam

    When a routing rule is improperly formatted and returns an error, the transaction will not complete the routing process and will remain "stuck" in its original status. This can lead to email spam if the original status is a queue that sends an email notification to the user (e.g., Awaiting Customer Contact) as the notification will be sent repeatedly until the request is manually routed out of the original queue.

    Bug# 22851

    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  ·  Email  ·  Admin →

  12. Address matching for some Docline requests may fail

    For some Docline requests, only part of the shipping address is matched and saved from the request text on the Lender Selection form, which then causes address matching to fail when that request is imported from Docline into ILLiad.

    Bug# 22013

    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  ·  Docline  ·  Admin →

  13. Database Manager may fail to delete CopyrightSessions records

    The ILLiad Database Manager will fail to delete CopyrightSessions records that contain non-integer values in the OrderHeader and OrderDetail fields.

    Bug# 21882

    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 →

  14. Log messages may contain extra punctuation marks

    Several log messages (e.g., the "Error refreshing system alert list" message) are improperly formatted and contain extra punctuation marks at the end.

    Bug# 21726

    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 →

  15. User notification preferences are not set if user is moved across NVTGC web pages as they register

    If a user creating a new account on the ILLiad web pages selects a pickup location/NVTGC on the user registration form that is different from the NVTGC associated with the set of web pages being used to register, then notification preferences will not be set when the account is created.

    Bug# 21707

    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 →

  16. Missing trailing slash breaks WebPDFPath key

    The file path entered in the WebPDFPath customization key will not be recognized unless it contains a trailing slash at the end.

    Bug# 21457

    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 →

  17. Users without layout customization permissions can't view customized layouts in the ILLiad Client

    Custom layout changes will not show in the ILLiad Client unless the logged-in staff user has the "Can Customize Layouts" permission enabled in the ILLiad Staff Manager.

    Bug# 21351

    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 →

  18. Some characters are not correctly encoded when logging.

    Some characters (such as those with diacritics) are not properly encoded in log files.

    Workaround: Add <encoding value="utf-8" /> under the <appender> element in the default log.config files.

    Bug# 21306

    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 →

  19. ILLiad API errors when DueDateOverride value is NULL

    The ILLiad API will return an error when submitting a Loan request for a Lending Library that belongs to a Group with a NULL DueDateOverride value (i.e., when no Lending Due Date Override value has been set for that Group).

    Bug# 20813

    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 Platform  ·  Admin →

  20. PDF Utility handling fails for PDFs generated by iTextSharp 4.1.6

    The PDF Utility used by the Odyssey Manager will return errors when delivering PDFs generated by iTextSharp 4.1.6.

    Bug# 20683

    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  ·  Odyssey Manager  ·  Admin →
2 4 5 6 7 8

ILLiad Known Issues

Categories

Feedback and Knowledge Base

(thinking…)