https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/index.html Recent content in Flow steps on Instabase Platform Documentation Hugo -- gohugo.io en-us https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-checkpoint/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-checkpoint/index.html Table of Contents Straight-through processing Handling repeat execution in UDF The apply checkpoint step verifies details identified in a previous step according to validation formulas, and triggers a review for failed validations. Rules are specified in validations and connected as modules to the apply checkpoint step in a flow. When validation fails and a review is triggered, the flow job is paused at the checkpoint until a reviewer confirms or corrects data in Flow Review and resumes the flow. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-classifier/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-classifier/index.html The apply classifier step identifies record type, or class, based on a classification model. For common document types, you might be able to use an existing Marketplace model for classification. Otherwise, you can train classification models in ML Studio. Classification models are connected as modules to the apply classifier step in a flow. Split PDFs and TIFs The Split PDF and TIF source files option, if enabled, splits and groups pages in PDF, TIF, and TIFF files into separate records according to their class. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-redactor-refined-fields/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-redactor-refined-fields/index.html Table of Contents Redactor configuration file The apply redactor to refined fields step redacts extracted data in output PDFs and optionally replaces redacted text with specified strings. You can redact fields only after an apply refiner step, because redactor configuration depends on field names specified in Refiner. Redactor configuration file A configuration file, redactor_config.json, defines which fields to redact. If no configuration file is provided, all extracted fields are redacted. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-refiner/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-refiner/index.html The apply refiner step reformats extracted data according to your specifications. Rules are specified in Refiner and connected as modules to the apply refiner step in a flow. Input file type The input file type option specifies source file format for the data you’re refining. The default, IBOCR, is a JSON file that represents the output for most flow steps. In typical Instabase flows, IBOCR is the appropriate choice. If you’re refining data that you’ve exported to CSV files, select CSV. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/doc-gen/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/doc-gen/index.html The document generation step generates Word documents that report extracted data. Generated documents are based on templates that uses a jinja script. Template files are Word Documents (.docx) that rely on a specific directory structure: The template files must reside in the _resources folder. The _resources folder must reside at the same directory level as the .ibflow file. You can generate documents only after an apply refiner step, because document generation configuration depends on field names specified in Refiner. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/map-records/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/map-records/index.html Table of Contents Parameters and settings Input file type Mapping type Custom Formula Scripts directory Clear metadata Page matcher config Input variables The map records step specifies how multipage documents are parsed. If required in a flow, this step always follows the process files step. Parameters and settings Use these parameters and settings to control how the map records step operates. Input file type The input file type is always IBOCR, the default file format for scanned documents. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/process-files/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/process-files/index.html Table of Contents Parameters and settings Use Reader module Processing functions OCR model type Scripts directory Layout scope Layout algorithm Page range Encryption config OCR config Custom image filters Implementing a custom image filter Passing parameters Registering a custom image filter Example: Background removal The process files step converts various document formats into machine-readable text. Most flows begin with this step, but you can place the step anywhere in a flow. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/run-extraction-model/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/run-extraction-model/index.html The run extraction model step extracts data from records based on an extraction model. For common document types, you might be able to use an existing Marketplace model for extraction. Otherwise, you can train extraction models in ML Studio. Extraction models are connected as modules to the run extraction model step in a flow. Rename fields to resolve conflicts If your flow includes multiple extraction steps, it’s possible to produce duplicate field names for common data points, like name or address. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-nlp/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-nlp/index.html Table of Contents How to use NLP program Input format Output format An NLP program specifies analysis types and options for each step. The Apply NLP step works on IBOCR files that are usually the result of a custom Apply Fetcher step. How to use In Flow Editor, add the Apply NLP step in a Flow after a custom Apply Fetcher step. Leave the default input and output folders. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-udf/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/apply-udf/index.html Table of Contents Input File Extension Output File Extension Input Folder Output Folder Formula Special input variables Logging Extra settings Scripts directory Configuration options for the Apply UDF step. Input File Extension The filename extension that identifies the file type to process. Output File Extension The filename extension that identifies the file type to generate as output of this step. Input Folder Select the input folder that contains the files. https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/fetch-files/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://platform.instabase.com/docs/26.04/automate-workflows/step-config-reference/fetch-files/index.html Table of Contents How to use Required settings Input File Document Input Folder Output Folder Extra settings Open Params Scripts Directory Sample custom fetcher InputPayloadDict OutFileDict OutFilesPerQueryDict FetcherBase class Fetch files utilities Common search terms API requests HTML processing The Fetch Files step is the first step of a Flow. How to use In Flow Editor, add the Fetch-Files step in a Flow as the first step. Configure the required settings: