CV Parsing
CV parsing is the process of extracting, analyzing, and storing data from a CV or resume. This data is then used to create new Contact, and associated, records. This utilises Daxtra's CV parsing engine to extract the data from the CV and then uses the Seven20 CV parsing framework to create the records.
Parsing framework
The CV parsing framework is a unified way of parsing CVs into Contact records within Seven20. There are several different ways to access the CV parsing framework, each of which depends on the use case required and the level of automation desired. The following are the different ways to access the CV parser:
| Parser | Automation Level | Description |
|---|---|---|
| Utility Bar Parser | Manual | Allows a user to upload a CV and have a new Contact record form prepopulated with the details. Ideal for a consultant manually uploading a CV |
| Email Inbox Parser | Manual, some automation | Allows a user to upload a CV from within the email pane and edit key fields before saving the CV. Ideal for rapidly creating candidates from received emails |
| Inbound Email Parser | Fully automated | Allows a user to send a CV to a specific email address and have a new Contact record form prepopulated with the details. Useful when receiving emails from a third party source, without requiring an integration |
| Reparser | Fully automated, manual trigger | Allows an existing record to be updated with new CV data. |
The parser framework takes the parsed CV response from Daxtra and converts it into a Contact, seven20__Education_History__c and seven20__Employment_History__c records, and optionally extracts the skills and presents them as potential codes for the new Contact record. Each parser takes and outputs the same records, so results will be consistent regardless of the parser used.
Parsing skills to codes is only supported within the Utility Bar Parser.
Parser behaviour
Each parser has some specific functionality and configuration elements appropriate to it's use case, however there are some common elements that are shared across all parsers and occur as part of the parsing process. These are detailed below.
CV file
The CV file is uploaded to the Salesforce platform and saved as a ContentVersion record during the parsing process. After the CV has been parsed and the candidate record created, the CV file is attached to the candidate record, with the specifics depending on whether AWS is enabled.
- If AWS is enabled:
- ContentVersion is uploaded to AWS and a seven20__Document__c record is created to represent the CV file
- Document record is then attached to the candidate record via a seven20__Document_Link__c record
- Original ContentVersion record is then deleted
- If AWS is not enabled:
- A ContentDocumentLink record is created to attach the CV file to the candidate record
The attached CV file is flagged as the candidate's by populating the seven20__CV_File_Id__c field on the contact record with the appropriate Id. This enables indexing of the candidate.
Education and employment history
The parser will also parse the education and employment history from the CV. This information will be saved against the candidate record as a related list of seven20__Education_History__c and seven20__Employment_History__c records. These records are saved after the candidate record has been created and as such any issues in creating these records will not prevent the candidate record from being created.
These records will not be visible to the end user during parsing.
Errors
The CV parser returns standard HTTP status codes as its response, if an error is encountered, this is presented back to the user with the name of the status code (e.g. Bad Request). Most errors are transient and can be immediately retried by a user, if the error persists, Seven20 support should be contacted, providing the offending CV.
If a HTTP 422 error is returned, the CV cannot be processed and the user should not attempt to re-upload the CV. Seven20 cannot assist in these cases.