- Cascade de-identification allows you to de-identify any number of records attached to the objects in the hierarchy mapped.
- Up to three levels of the hierarchy of objects can be mapped. For the Nth level RTBF de-identification refers to the Nth Level RTBF/De-identification article.
Note – Nth level De-identification supports for version 2.27 and above. Cascade de-identification supports only three-level de-identification for version 2.26 and below.
- To create the mapping for cascade de-identification, click on the “Add” button on RTBF/De-identification tile.
- Refer to the RTBF/De-identification Mappings article to create the mapping for a single object.
- A child object field will appear, select the child object. Click on the add child button. A child object will be added.
- You can also add the search filter, on the basis of this search filter records will be selected.
- To add the mapping of the child object “Contact” in this example, click on the contact and add the mapping of the fields in the same way as above.
- To add the grandchild object click on the radio button.
- A grandchild section will appear, add the grandchild object, “Case” in this example.
- Click on the case to add the field mapping.
- Once the mapping is ready for the contact and case go to the list of mapping and mark it as “set as default”.
- Now navigate to the case to create a new case to process cascade de-identification.
- Select “DSAR – De-identification” and click next.
- In the Data Subject field enter the salesforce ID of the parent Record.
Note – if it is a contact record, then the user can directly select a contact from the lookup field of contact.
- Save the case
- Go to the “Data subject records” related list.
- Click on the “Populate Data Subject” button.
- Background scripts will run and all the child and grandchild records related to the Account record will show up in the related list.
- Status is “Awaiting Processing” as the de-identification is yet to be processed.
- Select the drop-down list near the “Populate data Subject” button and click on the “Process Records” button.
- Now the status has changed to “Processed”.
Note: If org is upgraded from 2.19 to 2.20 version of Cloud Compliance then make sure that the “Processed” value is added in the “DSAR Status” picklist field on Case object.
- You can check the deidentified records according to the mapping.
Note: in a similar way users can de-identify any records of any object by mapping them in the hierarchy.