- Overview
- Document Processing Contracts
- Release notes
- About the Document Processing Contracts
- Box Class
- IPersistedActivity interface
- PrettyBoxConverter Class
- IClassifierActivity Interface
- IClassifierCapabilitiesProvider Interface
- ClassifierDocumentType Class
- ClassifierResult Class
- ClassifierCodeActivity Class
- ClassifierNativeActivity Class
- ClassifierAsyncCodeActivity Class
- ClassifierDocumentTypeCapability Class
- ContentValidationData Class
- EvaluatedBusinessRulesForFieldValue Class
- EvaluatedBusinessRuleDetails Class
- ExtractorAsyncCodeActivity Class
- ExtractorCodeActivity Class
- ExtractorDocumentType Class
- ExtractorDocumentTypeCapabilities Class
- ExtractorFieldCapability Class
- ExtractorNativeActivity Class
- ExtractorResult Class
- FieldValue Class
- FieldValueResult Class
- ICapabilitiesProvider Interface
- IExtractorActivity Interface
- ExtractorPayload Class
- DocumentActionPriority Enum
- DocumentActionData Class
- DocumentActionStatus Enum
- DocumentActionType Enum
- DocumentClassificationActionData Class
- DocumentValidationActionData Class
- UserData Class
- Document Class
- DocumentSplittingResult Class
- DomExtensions Class
- Page Class
- PageSection Class
- Polygon Class
- PolygonConverter Class
- Metadata Class
- WordGroup Class
- Word Class
- ProcessingSource Enum
- ResultsTableCell Class
- ResultsTableValue Class
- ResultsTableColumnInfo Class
- ResultsTable Class
- Rotation Enum
- Rule Class
- RuleResult Class
- RuleSet Class
- RuleSetResult Class
- SectionType Enum
- WordGroupType Enum
- IDocumentTextProjection Interface
- ClassificationResult Class
- ExtractionResult Class
- ResultsDocument Class
- ResultsDocumentBounds Class
- ResultsDataPoint Class
- ResultsValue Class
- ResultsContentReference Class
- ResultsValueTokens Class
- ResultsDerivedField Class
- ResultsDataSource Enum
- ResultConstants Class
- SimpleFieldValue Class
- TableFieldValue Class
- DocumentGroup Class
- DocumentTaxonomy Class
- DocumentType Class
- Field Class
- FieldType Enum
- FieldValueDetails Class
- LanguageInfo Class
- MetadataEntry Class
- TextType Enum
- TypeField Class
- ITrackingActivity Interface
- ITrainableActivity Interface
- ITrainableClassifierActivity Interface
- ITrainableExtractorActivity Interface
- TrainableClassifierAsyncCodeActivity Class
- TrainableClassifierCodeActivity Class
- TrainableClassifierNativeActivity Class
- TrainableExtractorAsyncCodeActivity Class
- TrainableExtractorCodeActivity Class
- TrainableExtractorNativeActivity Class
- Document Understanding Digitizer
- Document Understanding ML
- Document Understanding OCR Local Server
- Document Understanding
- Release notes
- About the Document Understanding activity package
- Project compatibility
- Configuring external connection
- Set PDF Password
- Merge PDFs
- Get PDF Page Count
- Extract PDF Text
- Extract PDF Images
- Extract PDF Page Range
- Extract Document Data
- Create Validation Task and Wait
- Wait for Validation Task and Resume
- Create Validation Task
- Classify Document
- Create Classification Validation Task
- Create Classification Validation Task and Wait
- Wait for Classification Validation Task and Resume
- Create Pre-Hire in Workday Based on CV
- Generative extractor - Good practices
- Generative classifier - Good practices
- Intelligent OCR
- Release notes
- About the IntelligentOCR activity package
- Project compatibility
- Configuring Authentication
- Load Taxonomy
- Digitize Document
- Classify Document Scope
- Keyword Based Classifier
- Document Understanding Project Classifier
- Intelligent Keyword Classifier
- Create Document Classification Action
- Create Document Validation Artifacts
- Retrieve Document Validation Artifacts
- Wait For Document Classification Action And Resume
- Train Classifiers Scope
- Keyword Based Classifier Trainer
- Intelligent Keyword Classifier Trainer
- Data Extraction Scope
- Document Understanding Project Extractor
- Document Understanding Project Extractor Trainer
- RegEx Based Extractor
- Form Extractor
- Intelligent Form Extractor
- Redact Document
- Create Document Validation Action
- Wait For Document Validation Action And Resume
- Train Extractors Scope
- Export Extraction Results
- ML Services
- OCR
- OCR Contracts
- Release notes
- About the OCR Contracts
- Project compatibility
- IOCRActivity Interface
- OCRAsyncCodeActivity Class
- OCRCodeActivity Class
- OCRNativeActivity Class
- Character Class
- OCRResult Class
- Word Class
- FontStyles Enum
- OCRRotation Enum
- OCRCapabilities Class
- OCRScrapeBase Class
- OCRScrapeFactory Class
- ScrapeControlBase Class
- ScrapeEngineUsages Enum
- ScrapeEngineBase
- ScrapeEngineFactory Class
- ScrapeEngineProvider Class
- OmniPage
- PDF
- [Unlisted] Abbyy
- [Unlisted] Abbyy Embedded

Document Understanding Activities
Create Pre-Hire in Workday Based on CV
linkAbout
linkSummary: Create a pre-hire in Workday using the data provided in the CV.
Applications: Workday
Description: After identifying appropriate candidates using Document Understanding to extract experience information from CVs, create a pre-hire in workday using the data provided in the CV.
This example presents Document Understanding activities such as Classify Document, Extract Document Data, and Create Validation Task.
Workflow
link- Open Studio Web and create a new project.
-
Add a File Created activity to your workflow. Set up the location of the
CV you want to use in the workflow, and the location of the output file. In the
activity, perform the following configurations:
- Set up your Google Drive connection.
- In the In location field, choose the folder where the CV is located.
- If needed, add additional filters (such as created by, file extension, and name) in the Additional filters field.
- In the Created file field, reference the created file to be used in the workflow.
Figure 1. Configuring the Google Drive connection properties
-
Next, add a Classify Document activity, to classify the documents.
- In the Project field, select your Document Understanding project from the dropdown list.
- In the Classifier field, select Generative Classifier from the dropdown list.
-
In the Prompt field, configure three document types:
- CV: The document used before employment, containing candidates skills and work experience.
- ID: The identification document of the candidate.
- W-9 Form: The tax form for the candidate.
You can configure more document types, as needed.
Figure 2. Configuring three document types in the Prompt builder, using the Generative Classifier
-
In the Input field, add the file created at step two.
Figure 3. Adding the previously created file in the Input field of the Classify Document activity
-
Next, add an If activity. This activity is used to extract candidate
information if a document type is defined as CV, or display a message if not.
Configure the activity as follows:
- In the Condition field, select the Plus icon to select Condition builder.
- In the Condition builder select Add condition.
- In the Click to use variable field, select the Document Type Name property of the Classify Document activity.
- From the dropdown select equals.
- In the Enter text or press Ctrl+Space field, enter CV.
- Select Save to save your condition.
Figure 4. Creating and configuring the condition inside the Condition builder
-
Next, add a Write Line activity in the Then branch of the
activity. Configure the activity as follows:
- In the Text field, select the Plus icon to select Text builder.
- In the Text builder, enter "Found CV to process:".
- For the Insert variable dropdown list, select the Created file variable from the File Created activity.
- Select Save to save your changes.
Figure 5. Configure the Write Line activity, using the Text builder, to output a certain value
-
Next, add an Extract Document Data activity. This activity is used to extract data from the
classified document. In the activity, perform the following steps:
- In the Project field, select your Document Understanding project from the dropdown list.
- In the Extractor field, select Generative from the dropdown list.
-
In the Prompt field, configure seven fields:
- First name: First name of the candidate.
- Email: Email address of the candidate.
- Experience: Previous experience of the candidate.
- SalesSkills: Does the candidate have Sales skills?
- Employer: What is the current employer of the candidate?
- Last name: Last name of the candidate.
- Country: What's the country of residence for the candidate?
You can configure more fields, as needed.
Figure 6. Configuring the Generative Extractor Prompt builder with the CV fields
-
In the Input field, add the document data resulted from the
Classify Document activity.
Figure 7. Entering the document data resulted from the Classify Document activity in the Input field of the Extract Document Data activity
-
Next, add an If activity. This activity is used to create pre-hire in
Workday if a suitable candidate is found, or display a message if not. Configure
the activity as follows:
- In the Condition field, select the Plus icon to select Condition builder.
- In the Click to use variable field, select the SalesSkills property of the Extract Document Data activity.
- From the dropdown select equals.
- In the Enter text or press Ctrl+Space field, enter Yes.
- Select Save to save your condition.
Figure 8. Creating and configuring the condition inside the Condition builder
-
Next, add a Write Line activity in the Then branch of the second
If activity. Configure the activity as follows:
- In the Text field, select the Plus icon to select Text builder.
-
In the Text builder, add a message containing information from
the First Name, Last Name, Employer, and
email fields configured using the Prompt builder of
the Extract Document Data activity.
Example:
Received CV applications from Sales Manager with name: First Name | Last Name, currently working at Employer - creating pre-hire profile. Email at email.
Figure 9. The text that the Write Line activity should show in the output
- Next, add a Workday Create Pre-Hire activity and set up your Workday connection.
-
Next, add a Write Line activity in the Else branch of the second
If activity. This activity will display a message if a candidate does
not meet the required criteria (in our example, Sales experience). Configure the
activity as follows:
- In the Text field, select the Plus icon to select Text builder.
- In the Text builder, add a message containing information from the First Name and Last Name fields configured using the Prompt builder of the Extract Document Data activity.
Example:Candidate First Name Last Name, does not have Sales experience, sending the CV for validation.
Figure 10. Creating the expression for the Write Line activity in the Text builder
-
Add a Create Validation Task
activity after the Write Line activity. This activity is used to create a
document validation action in Action Center when a CV does not meet the required
criteria. Configure the activity as follows:
- In the Extracted data field, provide the output of the Extract Document Data activity.
- In the Action title, provide a title of the action that needs to be created in Action Center. In our example, you can add "Validate CV".
- In the Action properties section, choose a priority of the action from the Action priority dropdown list.
- Specify the Orchestrator folder where the resources will be stored in the Orchestrator folder field.
- In the Action catalog field, specify the catalog where the action is created in Action Center.
Figure 11. Configuring the properties of the Create Validation Task activity
-
Finally, add a Write Line activity in the Else branch of the
first If activity. This activity will display a message if the processed
document is not a CV. Configure the activity as follows:
- In the Text field, select the Plus icon to select Text builder.
- In the Text builder, add a message containing the Created File property of the File Created activity and the Document Type property of the Extract Document Data activity.
Example:Document Created file is not a CV, but a Document Type, so there is nothing to process.
Figure 12. Creating the expression for the Write Line activity in the Text builder