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

2 results found

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

  2. Email subject encoding can fail for non-ASCII characters

    Encoding for the subject line of an email sent from ILLiad can fail if it contains non-ASCII characters.

    Workaround: If an email is bounced back for this issue, you can change the subject line of the email to remove any non-basic characters

    Bug# 19547

    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 →

ILLiad Known Issues

Categories

Feedback and Knowledge Base

(thinking…)