- 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
- ExtractorAsyncCodeActivity Class
- ExtractorCodeActivity Class
- ExtractorDocumentType Class
- ExtractorDocumentTypeCapabilities Class
- ExtractorFieldCapability Class
- ExtractorNativeActivity Class
- ExtractorResult 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
- 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
- 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 Process - Studio Template
- Document Understanding
- Release notes
- About the Document Understanding activity package
- Project compatibility
- Document Data
- 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
- Intelligent OCR
- Release notes
- About the IntelligentOCR activity package
- Project compatibility
- Load Taxonomy
- Digitize Document
- Classify Document Scope
- Keyword Based Classifier
- Intelligent Keyword Classifier
- Present Classification Station
- Create Document Classification Action
- Wait for Document Classification Action and Resume
- Train Classifiers Scope
- Keyword Based Classifier Trainer
- Intelligent Keyword Classifier Trainer
- Data Extraction Scope
- RegEx Based Extractor
- Form Extractor
- Intelligent Form Extractor
- Present Validation Station
- 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
Intelligent Keyword Classifier
UiPath.IntelligentOCR.Activities.DocumentClassification.IntelligentKeywordClassifier
This activity enables any user to classify and split document packages into individual document types.
It can only be used together with the Classify Document Scope activity.
Common
- DisplayName - The display name of the activity.
Input
- ApiKey - Specifies the API key of the account. The API Key field is automatically pre-populated if defined in local project settings or in the Document Understanding framework.
- Endpoint - The URL to UiPath® server. By default, the endpoint is
https://du.uipath.com/svc/intelligentkeywords
. For more information, see Document Understanding Public Endpoints. - LearningData - The string containing the serialized classifier data. This field supports only strings and String variables.
- LearningFilePath - The
full path to the file containing the classifier data. This field supports only
strings and
String
variables.Note:Only one of the above parameters can be set at a time. You can use either the LearningData string or the LearningFilePath string.
The LearningFilePath specifies the locations from where to retrieve the classifier data.
The LearningData contains the actual information of that classifier.
- Send documents - Send documents for better support, troubleshooting, and performance improvements.
Misc
- Private - If selected, the
values of variables and arguments are no longer logged at Verbose level.
Note: The best practice is to create an empty
.json
file at that location, then use its name in the LearningFilePath field.
Splitting
- PerformDocumentSplitting - If left unchecked, the model will not perform document splitting, only classification.
- UsePageNumbers - If checked, the mode will use the page numbers feature to decide where to split documents. Use it in case page numbers might improve splitting results.
Access the Manage Learning wizard to configure the Intelligent Keyword Classifier activity. The same wizard can be used for reviewing data collected during the document classification training phase, by opening the same wizard with an updated learning file path.
This wizard allows you to configure and manage the training data used by the Intelligent Keyword Classifier activity for identifying the document type and classifying the documents. It was created to suit the need for editing a file path. If a Learning Data option with a variable is used instead, then you are asked if you either want to edit a specific file path or to abort this operation.
- Add an Intelligent Keyword Classifier/Intelligent Keyword Classifier Trainer activity to your workflow.
- Configure your Intelligent
Keyword Classifier activity by adding the path of a
.json
file.- If no path is provided and the Manage Learning option is clicked, then a popup is displayed, asking for a Learning File Path input. Once the path is provided, the wizard opens.
- A variable can be added
instead of a
.json
file, but, because the wizard cannot apply the learning pattern to a LearningData variable, it asks for a specific file path that can be edited.
-
Click on the Manage Learning option.
- The Wizard window opens.
- The Wizard window opens.
- If no path is provided and the Manage Learning option is clicked, then a popup is displayed, asking for a Learning File Path. Once the path is provided, the wizard opens.
.json
file is available, you can add the name of a new
.json
file straight into the activity and the
.json
file is automatically created inside the specified
folder.
The below screenshot presents a document type that has been trained, one that hasn't, and one that has been trained and accessed to be viewed or deleted.
For document types that have not been trained yet, design-time training can be performed using the Start Training option. For document types that already have some training, you can either delete it to start over, by using this option, or perform extra training (cumulative to the already existing one) using the edit option.
Once a new training has been initiated, a new screen is displayed asking for the training files and the OCR engine that should be used. The default OCR engine is UiPath® Document OCR.
Each OCR engine comes with its own set of custom options.
The following OCR engines do not support rotated documents and should not be used to process such documents:
- Microsoft OCR
- Tesseract OCR
The Apply OCR on PDF option establishes if the OCR process should be applied or not to PDF documents. Three options are available in the dropdown list: True, False, and Auto.
If set to True, the OCR is applied to all PDF pages of the document. If set to False, only digitally typed text is extracted. The default value is Auto, determining if the document requires to apply the OCR algorithm depending on the input document.
If the UiPath.IntelligentOCR.Activities package has been updated to v5.1.0, then the ForceApplyOCR parameter has been replaced with the ApplyOcrOnPDF. Here is the compatibility between the old and new parameters:
• ForceApplyOCR = True is being replaced by ApplyOcrOnPDF = Yes
• ForceApplyOCR = False is being replaced by ApplyOcrOnPDF = Auto
• ForceApplyOCR = Empty is being replaced by ApplyOcrOnPDF = Auto
• ForceApplyOCR = <user-defined variable> is being replaced by ApplyOcrOnPDF = Auto
Only training data from document types that have been trained is eligible for export. Document types that have not been trained cannot be selected.
Exporting training data
You can export training data following these steps:
- Select document types that have been trained.
- Click the Export button.
- If you have unsaved changes, the
following message is displayed.
- Click Yes.
- Save the training data archive with the desired name.
- A message is displayed stating
how many document type training data sets were exported. For example:
- Click OK to return to the main screen of the wizard.
Importing training data
You can import training data following these steps:
- Click the Import button.
- Select the training data archive and click Open.
- Select the document types you want.
- Click the Import button.
- The training data is imported.
The below table explains each message displayed when importing training data:
Import Type |
Message displayed |
---|---|
New Document Type and Word Vectors |
This document type will be added to the taxonomy |
New Word Vector (none was previously defined) |
N/A |
Identical Document Type and Word Vector |
The word vector for this document type will be overwritten |
Document Understanding Integration
The Intelligent Keyword Classifier activity is part of the Document Understanding Solutions. Visit the Document Understanding Guide for more information.