FinancialForce PSA supports Salesforce's Shield Platform Encryption on all current standard fields, except those detailed in below sections, and also supports encryption of files and attachments.
When encryption is enabled for a field, disabling the encryption later does not remove the querying restrictions on that field. This means that any current or future packages on your org which use that field must continue to support encryption on it. For example, when searching for accounts, users cannot filter by a field that is, or was, encrypted because the querying restrictions imposed by encryption don't allow filtering on encrypted fields.
Refer to the Salesforce Shield Platform Encryption Implementation Guide if you are considering enabling encryption on your organization. If you are unsure whether to proceed, contact your Salesforce representative before making any decisions.
Encrypted Contact Name
Where the Contact Name is encrypted in your org:
- If you have a field set used for the search function containing the Resource First Name or Last Name, searches are conducted against the Resource Name field.
- A maximum of 2000 records are returned from any Resource search.
- Search results may sort differently than in orgs that do not have Contact Name encrypted.
Encrypted Account Name
Where the Account Name is encrypted in your org, when searching for the Account Name on a PSA record, the following fields on the Account object are also searched:
- Website
- Site
- NameLocal
Resource and Project/Assignment Lookups
An information message displays in the Resource and Project/assignment lookups (for example in Time Entry) advising users to refine their searches when Shield Platform Encryption is switched on, and a SOSL limit is reached during filtering.