Uploading Custom CVs to Seven20 via PipeLaunch - Technical Details

PipeLaunch offers a native, zero-setup integration for uploading custom CVs directly to your Seven20 environment.

How It Works

Seven20 requires a specific sequence of steps whenever a CV is uploaded via any method other than the built-in CV Viewer. PipeLaunch handles all of these automatically on your behalf:

Step 1: Upload the ContentVersion

PipeLaunch uploads the CV as a ContentVersion record with the following fields:

Field	Value	Notes
`Title`	`{ContactName}.pdf`	Generated from the contact's name
`PathOnClient`	`{ContactName}.pdf`	Same as Title
`VersionData`	`{base64}`	The CV file encoded in base64
`seven20__File_Type__c`	`CV`	Only set for Seven20 orgs
`FirstPublishLocationId`	`{ContactId}`	Set to the Contact record Id

Setting FirstPublishLocationId to the Contact Id causes Salesforce to automatically create a ContentDocumentLink between the resulting ContentDocument and the Contact record. There is no separate ContentDocumentLink insert step.

Step 2: Update the Contact record

After the ContentVersion is created, PipeLaunch updates the Contact with the following fields:

Field	Description	Example
`seven20__Cv_File_Id__c`	The unique ContentDocument ID for the uploaded CV file. If AWS is enabled, this is the Seven20 Document Id instead.	`0692x0000000Q7vAAE`
`seven20__CV_File_Name__c`	The title or filename of the CV document.	`John Smith - LinkedIn Resume`
`seven20__Most_Recent_CV_Date__c`	The timestamp indicating when the CV was uploaded.	`2026-06-15`
`seven20__Parser_Status__c`	Set to `"Partial Re-parse"` to initiate the Daxtra parsing process.	`Partial Re-parse`

Understanding "Partial Re-parse"

We specifically set seven20__Parser_Status__c to "Partial Re-parse" to protect your existing data. This tells the Seven20 parsing engine to process the new CV and fill in only the fields on the candidate record that are currently empty.

This approach is non-destructive: no data is ever lost or overwritten. If a field already contains information, it will be preserved. This ensures that manually entered or previously parsed data remains intact while new information from the CV is added to complete the candidate's profile.

Notes

The seven20__File_Type__c field on ContentVersion is only set when the org's installed namespaces include seven20 or seven20_gp1. It is skipped for all other orgs.
If AWS indexing is enabled, seven20__Cv_File_Id__c must reference the seven20__Document__c Id rather than the ContentDocument Id. PipeLaunch handles

this automatically based on org configuration.

Need custom logic? Use the AutoLaunched flow support to trigger additional processing after a CV upload.

Updated on: 15/06/2026