Parse Additional Field Values from a Templated Email

Suppose your business has a system that generates an email message that you want to capture in Salesforce. You know that the message will always have a consistent format and contain data that you want to populate into specific fields on the case. While a direct integration with Salesforce might be preferable, Email to Case Premium could assist with the inbound processing by parsing the email message. Here are the two basic scenarios:

• The inbound email creates a new case with values from the parsed email and maps additional fields on the case.
• The inbound email creates a new case or updates an existing case and then creates a related object record using values from the parsed email.

We would need to create an interface to allow admins to upload a sample message, tag that message with a means to map its contents to fields or a related record, and the email origination to prevent spamming the system.

Editing Sales price

There needs to be a way to not allow editing of the 'Sales Price'.

Use Case: 
Our sales reps need to see what the unit cost is but they should not have access to edit the field. Only higher level users should be able to control pricing. This is a basic need that is being overlooked.
 

Display HTML Version in Case Comments List

When creating public or private comments with the enhanced formatting editor enabled, HTML result is saved in a Salesforce field. That is also the information sent by email to the customer if using the proper merged field. This is the HTML information that should also be used and displayed to users / support agents when accessing the Case Comments list of a case when using the Timeline component in Lightning, rather than the plain text version saved by default by Salesforce.

We can all vote on that Salesforce Idea to add HTML to default case comments (13 year in the making...), but I'm confident there is a way in the meantime for Internet Creations to leverage the saved HTML information with the Timeline component so we can see formatted text and images directly in the comments list, which would be a much better experience for case owners.

Alert/Prompt when a Unrelated Recipient is Added to a Public Reply

Business or use case:

We have an agreement with our customers to protect their privacy and confidentiality. We have observed that sometimes our employees and our customers have similar first/last names.

Ex: While working on a case from Customer ABC, if one of our employee 'john.doe@companyname.com' is required to be added on cc and another customer XYZ has a similar email 'john.doe@XYZ.com' , it is possible that we may end up adding  john.doe@XYZ.com instead of john.doe@companyname.com on the case from Customer ABC, violating the agreement with both ABC and XYZ.

A summary of the idea:

While adding a recipient on the Public comments, prompt if there is an email from an unrelated customer domain ( or account). The exception is the domains set up as the 'Internal domains'. 

A thorough description of the functionality you have in mind:

In the above example, on a case raised by Customer ABC, if john.doe@XYZ.com added as a recipient on the public comment, show a prompt/alert on the UI that will warn against such domain mismatches. This should not stop from sending the email but just alert so that the composer of the email is aware of this potential risk.

An error message similar to "Warning: One of the recipients is not related to this account." should help.

Configurable Column Sizes in Timeline

Looking at the list of comments in the Timeline component can be tricky for users with a vertical screen, because the left column (private/public toggle and picture) and the right column (Preview Email link, list of attachments, Actions) are taking a lot of horizontal space.

It would be much better if these users could simply drag and drop to modify each column's size in the comments list; this way even on their vertical monitor they could grant much more space to the comments content itself.

Include "License Expiring on mm/dd/yyyy" message inside of all application LEX components

To prevent any surprise license expirations, we should run a check to seen when a license expires when a packaged component loads. If the product will expire within the next 7 days (or similar), we would display a message in the component (or through another mechanism) that says, "The license for <Product Name> expires on MM/DD/YYYY. Please contact your System Administrator."

Accommodate "Plus" Addresses when Creating/Matching Contacts

Modern email services handle plus addressing, or sub-addressing, to support dynamically created recipients. On the inbound processing side, Email to Case Premium treats "support@companydomain.com" and "support+productname@companydomain.com" as two unique addresses, allowing one to set Origin, Priority, and Record Type differently for each. However, Email to Case Premium does not account for this when creating new contacts or matching existing contacts.

Email to Case Premium should recognize the plus address as a sub-address for the contact and attempt to match it to an existing contact. For example, when a message is received from "person.name+tag@somedomain.com," Email to Case Premium will search for both the original address and "person.name@somedomain.com" to match the contact.

Indicator on Case Cards within Switchboard that a Draft Comment is in progress

It would be awesome if from the Switchboard View we could see if a draft comment is either currently being typed or was started within the last X number of minutes.

This would allow for support managers to not only see which cases are flagged and need attention, but also know when/if agents are actually taking action on those cases.

This feature would of course be limited to those who are also using E2CP, as draft comments are part of that package.

Expose Keep option for Images displayed in Timeline.

When managing images inside of the Signature Slayer Lightning Component, we provide options to Remove or Keep the image.

However, for customers who also have Email to Case Premium and are managing images inside of comments in Timeline, we do not provide a Keep option.

To keep an image means simply ignoring the sword icon. However, the sword will continue to display.

We should consider providing a Keep option for Signature Slayer users inside of Timeline who would like to hide the sword for images they don't intend to slay.

Advanced merge logic settings to clone child case field values to the primary case

Standard and custom case field values from secondary cases do not get moved to the primary case even when the primary case field value is empty.  Add advanced merge logic settings to enable options like...

For text fields concatenate all of the values from child cases into the primary case text field.

For other fields provide an option to use the min, max, earliest or latest value

Or choose the value from the latest or earliest secondary case.

Press Enter in Find Cases Search by Text to Display All Results in the List

After typing the term in the Search by Text box, press enter to bring up the full list of results, and cases can be selected as per the usual CMP selection method.

Could even add a "Search" button to the right side of the search box in case the person doesn't realize they can press enter.

Note: The type-ahead search remains, allowing a single click to select a case from the popup

Cross-Field Search in Duplicate Criteria

Find duplicate cases by defining criteria where the value of one case object field is found in another case object field. For example the case subject is found contained in the description of another case.

Cross-Object Search in Duplicate Criteria

Find duplicate cases by defining criteria where the value of a case object field is found in a related object field of other cases. For example the case subject is found in the email body of other cases.

Logging Information

If an exception occurs (such as a validation rule failing), there is currently no way of knowing being that it fails in the managed package. Suggestion would be to either create an error record within the org with the details, or to send an email to the admin. This way, if this occurs, we have a diagnostic tool to refer to.

Rapid Products Extension pack for Orders Object

With the Rapid Products application, you have an extension pack so the application can be used for Quotes. Do you have something similar that can be utilised for the standard Salesforce Order object?

If no, is it possible to have one?