• - All partner contracts state that any public mention of salesforce.com or any of its brands MUST be approved by Salesforce
• - All materials must be submitted via our Google form to obtain approval for any public mention of Salesforce.

Submit content via Google Form >

• - Approval of partner press releases can take up to 14 days for Summit and Crest level partners, and up to 30 days for all other partners. 

• - All partner contracts state that any public mention of salesforce.com or any of its brands MUST be approved by Salesforce
• - All materials must be submitted via our Google form to obtain approval for any public mention of Salesforce.

Submit content via Google Form >

• - Approval of partner press releases can take up to 14 days for Summit and Crest level partners, and up to 30 days for all other partners. 

Q: What's the difference between Platform Encryption and Classic Encryption?

A: Classic encryption lets you protect a special type of custom text fields, which you create for that purpose. With Platform Encryption, you can encrypt a variety of widely-used standard fields, along with some custom fields and many kinds of files.Platform Encryption also supports person accounts, cases, search, workflow, approval processes, and other key Salesforce features. See this table to understand the differences.

Q: Why should I support Platform Encryption?

A: Encryption at rest becomes a requirement, like SSL/TLS is today for network communications, it allows you to position your app ahead of the industry, reveals new opportunities, big customers choose to encrypt, and it can be a key differentiator of your app. 

Q: Can we selectively encrypt files?

A: No, you can only encrypt all files. 

Q: Can you encrypt custom fields in custom settings? 

A: Yes, you can apply encryption on custom fields added to custom settings but remember it is subscriber-control, meaning the customer can apply encryption on it in their org (as long as the custom field made encryptable and listed in the supported fields). 

Q: Will global search find document CONTENT, or just tags of documents in Box? 

A: Yes, it supports full text search within documents on Box. Files Connect on Box global searches would work analogous to how it is supported for Google Drive and Sharepoint. 

Q: Does Workflow support all actions on PE orgs? 

A: Only Email alerts and Outbound messaging are supported in PE orgs.

Q: Which standard objects' standard fields are encryptable in Spring '16? 

A: On the Account object, Account Name, Fax, Website, Phone are encryptable. On the Contact object, Description, Email, Fax, Home Phone, Mailing Address (Encrypts only Mailing Street and Mailing City), Mobile, Name (Encrypts First Name, Middle Name, and Last Name), Other Phone, and Phone are encryptable. On the Case object, Subject and Description are encryptable. On Case Comments, Body is encryptable.

Q: What data type of custom field can be encrypted?

A: You can encrypt the contents of these custom field types: Email, Phone, Text, Text Area, Text Area (Long), and URL. You cannot use currently or previously encrypted custom fields in custom formula fields or criteria-based sharing rules. In addition, you cannot use Schema Builder to create an encrypted custom field. Keep in mind that some custom fields can’t be encrypted such as fields that have the Unique or External ID attributes or include these attributes on previously encrypted custom fields, fields that are used in custom formula fields, and fields on external data objects. 

Q: Can customer encrypt managed package's custom field? 

A: Not at this time.

Q: Why can't I see "Custom Field" when selecting Setup | Platform Encryption | Encrypt Fields?

A: Encryption of custom field is available from the object | Field itself. Check the box "Encrypt the contents of this field".

Q: Does Platform Encryption, replace or enhance other AppExchange Partner (ISV) apps like CipherCloud and Perspecsys?

A: Many of these vendors are partners on our AppExchange and can add value to your use of Salesforce, with regards to to DLP and policy enforcement. When it comes to strongly encrypting data and making it available throughout the Salesforce Platform services functionalities, this brittle technology tends to break quite often, especially when we release software out to customers. The way in which these vendors interact with Salesforce to encrypt your data results in complex, costly projects, a fragile integration that can be difficult for these vendors to maintain, weakened encryption security, and a loss of functional capabilities. Based on our experience with similar technology, we believe that the native encryption-as-a-service is the most secure, robust, scalable and functional solution customers can use to add another level of security and protection to their private, regulated and sensitive data.

Q: Can Platform Encryption be undone? 

A: Since Platform Encryption is enabled at the customer org level, your customer has to open a case directly with Salesforce in order to get it deactivated. If they have no direct support from Salesforce, then you will need to submit this case.

Q: Does Platform Encryption replaces FLS and other security rules? 

A: No, Platform Encryption extends current security rules (sharing model, object/field level security, data residency options) and facilitates regulatory compliance, unauthorized access to database, contractual obligations, PII & data privacy rules. 

Q: What happens if a package uses an encrypted field in an unsupported way? 

A: Package installation will fail. 

Q: What happens if my customer tries to encrypt a field used in a package (or their own code) in an unsupported way? 

A: Encryption will be rejected. 

Q: Will "Where", "Order by" or "Group by" SOQL clauses be natively supported in future? 

A: These clauses are hard limitations. We won't be able to offer a native solution anytime soon.

Q: What happens if Dynamic SOQL uses an encrypted field in a "Where", "Group by" or "Order by" clause? 

A: An exception is thrown at run-time. Keep in mind that there is no exception during package installation.

Q: How can I tell if a field is encrypted or not?

A: There's a describe method where the field level that will let you know if the field is encrypted or not. Based on this you can implement a similar pattern for unsupported SOQL:

if (field.isencrypted()) {

static sosl 

apex filtering logic

} else {

dynamic soql 

}

Q: When will the Lightning Experience be supported?

A: The Lightning Experience is on the roadmap. Some areas will be supported in Summer '16.

Q: What should I do if I have additional questions about Platform Encryption?

A: Ask your questions in the Platform Encryption Group on the Partner Community.