My Account | Internet Creations
Welcome, Guest.

Email to Case Premium Release Notes 6.46.1 - 7.13

What's New

  • Variation Presets [Change 00189890] (7.0)
    • Email to Case Premium now offers the flexibility to have multiple preferences for specific settings, based on factors such as the inbound email address used on case correspondence and other case criteria. It can help segment different use cases for Email to Case Premium. For example, if you’re using Email to Case Premium for both internal and external support, have multiple support teams, or are supporting multiple product lines.


  • When searching for new recipients to add, the New Comment page will now prioritize Contacts matching the Case's Account. [Change 00189970] (6.48)
  • A new setting hides the Inline Image option from the Enhanced Comment Editor on the New Comment page. This change accommodates organizations wishing to refrain from sending out inline images that result in publicly accessible links. [Change 00189252] (6.48)
  • File names displayed in Timeline will no longer include the extension type. This update was made to provide a cleaner title and avoid situations where the extension would sometimes be duplicated. [Change 00190336] (6.50)
  • Removed dependencies on Name and Phone fields on Contact, allowing them to be encrypted with Email to Case Premium installed. [Change 00190940] (6.51)
  • Update Exclude Most Recent Comment from History Text setting to apply to all history text fields, not the public only history text. [Change 00190749] (6.52)
  • Improved the @ mention logic to avoid accidentally mentioning someone when typing an email address into a comment. [Change 00191466] (6.53)
  • Update package to allow for encrypting of Case.Subject field. [Change 00192008] (7.1)
  • Updated processing of pasted text to remove zero-width spaces to avoid encoding issues in outbound emails. [Change 00192101] (7.1)

Bugs Fixed

  • Resolved upgrade issue for Orgs with chatter disabled by removing chatter dependencies on the new Widespread Issues feature. [Change 00189728] (6.46.2)
  • Resolved issue where emails processed via Email to Case Premium would result in a "URLDecoder: Illegal hex characters in escape (%) pattern" error message. [Change 00189696] (6.47)
  • Resolved issue where clicking Save/Send on the New Comment page would result in an infinite spinning page load. [Change 00189663] (6.47)
  • Resolved issue where required dependent fields on the New Comment page maintained their required status even when no values were applicable. [Change 00189350] (6.48) 
  • Resolved issue where uploading a file on the classic New Comment page would go through a javascript remoting error. [Change 00189747] (6.48)
  • Resolved an issue where removing recipients on the New Comment page would sometimes result in duplicate draft comments being saved. [Change 00189562] (6.48)
  • Resolved an issue causing Case Comment Draft Comments to persist after sending the comment from the New Comment Page. [Change 00190143] (6.49)
  • Resolved an issue where Auto Add New Contact would result in an error if a converted Lead was found without a matching Contact with the same email address. [Change 00190391] (6.50)
  • Resolved an issue where a Case Comment Draft saved as a private comment would be loaded as a public comment on subsequent visits to the New Comment Page. [Change 00190416] (6.50)
  • Resolved 'System.StringException: Invalid id:' error related to a specific configuration of settings including Enable Private Comments Based on Recipients. [Change 00190852] (6.50)
  • Resolved issue preventing Forwarding Addresses for Inbound Email Addresses from displaying on the classic setup page. [Change 00190996] (6.51)
  • Resolved "Inserting new case comment failed: unexpected token: 'FROM'" error when no settings variations are configured. [Change 00192243] (7.11)
  • While viewing the Timeline, field history with the same timestamp will now be displayed in the correct order. [Change 00192285] (7.12)
  • Rich text edit fields will no longer have a duplicated label in the lightning New Comment page. [Change 00192285] (7.12)
  • Fixed an issue while using the lightning New Comment page where required fields being left blank did not prevent a Save & Send Comment from completing [Change 00192342] (7.13).

Known Issues


Email to Case Premium


Open a Case