PROTECTED fields (regulated fields) are fields that contain information that may be used to identify the person. Due to regulations of different countries, such information must be protected, and in some situations stored in the origin country.
For each Salesforce object, you can define the PROTECTED fields that store the personal identifiable information (PII) or any sensitive information users choose to localize. Such fields will be processed by the package according to the configured data store policy.
Managing PROTECTED fields
The package lets you manage PROTECTED fields as follows:
Add PII fields for each Salesforce object
Delete the no longer needed PROTECTED fields for each Salesforce object
On the menu, select Settings. The page with the app settings loads, as follows:
Here you need to select the Salesforce object which PROTECTED fields will be added for.
Adding PROTECTED fields
Select the Salesforce object which PROTECTED fields you want to add.
Click Add Field. The Add PII Fields form opens.
In the Select Field box, start entering the field name. Select the field from the prompted matches.
In the Hash Function box, select the hash function which will be applied to the value of the field. Ensure that the applied hash function is valid for data contained within the field, otherwise the hashed data pattern will be incorrect for storing in Salesforce. You can use the fixed hash function to apply your own custom value to hashed fields.
In the Lookup relationship box, enter the lookup relationship for the current field. In Salesforce this corresponds to the
Lookup Relationship Name.
In the Reference field box, enter the field name which value the current field will reference.
In the Reference order box, specify the order in which fields are referenced. Use the comma to separate different fields from each other.
In the Lookup api name box, enter the field name of the Salesforce object for making calls to Salesforce API. In Salesforce this corresponds to the
In the Key box, select the key if available to make the field searchable in Salesforce. You can have up to ten searchable PROTECTED and regular fields per one Salesforce object. This setting defines the field value searchability against the object and key.
Check the Need to hash box to enable the hashing for the PROTECTED field. By default, it it enabled automatically when you select the hash function.
Check the Is Compound box to indicate that the field is comprised of multiple fields.
Check the Is Country field box to indicate that the field contains information about the country.
When complete, click Add.
The newly added PROTECTED field will appear on the list with other PROTECTED fields that are attributed to the currently selected Salesforce object. These fields will be processed by the package and shown according to the configured data regulation policy.
Selecting hash functions for PROTECTED fields inline
You can select or change hash functions for PROTECTED fields inline when viewing the list of such fields for a specific Salesforce object.
On the list with PROTECTED fields, locate the field for which you want to change the hash function.
Hover over the field with the hash function.
Click the Edit icon.
Select the appropriate hash function.
The selected hash function will be applied to the current PROTECTED field.
Mapping fields to hash functions
While configuring fields, please consider the using of the proper hash function for a specific data format. For example, if you need to tokenize the email address, you should use uniqueEmailHash function. Otherwise, email address will not be properly handled by Salesforce. For names, use the uniqueHash function.
If you use the redaction data regulation policy, you need to apply the correct hash functions to fields. Please check the mappings of hash functions to fields in the following table:
|Internal Salesforce field||UI field||Hash function||Conditions||Notes|
|ANYTYPE||N/A||This function is on our roadmap and is not available yet.|
|BASE64||N/A||If the field length is greater than or equal to 50 characters.||Supporting the backward compatibility.|
|BASE64||N/A||If the field length is greater than or equal to 64 characters.||Supporting the backward compatibility.|
|CALCULATED||N/A||This function is on our roadmap and is not available yet.|
|CURRENCY||Currency||A new function is to be implemented.|
|DATACATEGORY||N/A||This function is on our roadmap and is not available yet.|
|DOUBLE||Number||A new function is to be implemented.|
|Email/80||Use the |
|Email/80||Use the |
|ENCRYPTEDSTRING||Text (Encrypted)/175||This function is on our roadmap and is not available yet.|
|HIERARCHY||N/A||This function is on our roadmap and is not available yet.|
|ID||N/A||This function is on our roadmap and is not available yet.|
|LOCATION||Geolocation||A new function is to be implemented.|
|LONG||N/A||This function is on our roadmap and is not available yet.|
|LOOKUP||N/A||This function is on our roadmap and is not available yet.|
|MULTIPICKLIST||Picklist (Multi-Select)/4099||This function is on our roadmap and is not available yet.|
|PERCENT||Percent||A new function is to be implemented.|
|PHONE||Phone/40||A new function is to be implemented.|
|PICKLIST||Picklist/255||A new function is to be implemented.Use the |
|PICKLIST||Picklist/255||A new function is to be implemented.|
|REFERENCE||Lookup Relationship/18||This function is on our roadmap and is not available yet.|
|REFERENCE||External Lookup Relationship||This function is on our roadmap and is not available yet.|
|STRING||AutoNumber/30||If the field length is greater than or equal to 50 characters.||Preparing the backward compatibility.Use the |
|STRING||Text/255||If the field length is greater than or equal to 64 characters,||Use the |
|STRING||If the field length is less than 30 characters,|
|TEXTAREA||Text Area (Long)/32768||If the field length is greater than or equal to 50 characters.|
|TEXTAREA||TextArea/255||If the field length is greater than or equal to 64 characters,|
|TEXTAREA||Text Area (Rich)/32768|
|TIME||Time||A new function is to be implemented.|
|Specifics of the compound Address field|
|PICKLIST||Accuracy/40||Use the |
|PICKLIST||Country/80||Use the |
|PICKLIST||CountryCode||Use the |
|DOUBLE||Latitude/18.15||A new function is to be implemented.|
|DOUBLE||Longitude/18.15||A new function is to be implemented.|
|PICKLIST||StateCode||Use the |
Using the fixed hash function
You can use the fixed hash function to apply custom values that you need instead of using the built-in hash functions returning random strings.
This function supports the following fields types:
The length of the values that the fixed hash function can apply depends on the field type.
Linking child objects to parent objects
To correctly support the links between child and parent objects, you need to set up the additional attribution for each child Salesforce object.
Select the child Salesforce object.
Click Add field.
In the Add PII Fields form, define the following configuration:
- Select Field - select the field which is used to link a child object to the parent object (for example, for the Contact object this is 'AccountId').
- Hash Function - select 'Nothing'.
- Reference order - enter '0'.
- Lookup api name - enter the name of the parent object.
- Key - select the key which will provide searchability of the field.
When complete, click Add.
Deleting PROTECTED fields
You delete PROTECTED fields from the configuration of the InCountry Data Residency for Salesforce package only. These fields will be preserved in Salesforce itself.
You can delete the not needed PROTECTED fieds from the data store policy for a specific Salesforce object. Such fields will be no longer protected by the package when showing their values in the interface of Salesforce.
Select the Salesforce object which PROTECTED fields you want to delete.
On the list with PROTECTED fields, locate the one you want to delete.
Click the box with the down arrow and then select Delete.
If you want to delete all the fields from the current configuration of the selected Salesforce object, click Delete All Fields.