Table Header Detector

Can be one of the following types:

Assign a Value Extractor to this property to identify header rows based on specific patterns or text content. This is useful for tables where headers follow a predictable format, such as a regular expression or keyword list.

If not set, header detection will fall back to using label sets (if available) or column header extractors.

Example:
To detect a header row containing "Qty", "Description", and "Price", use a regular expression extractor with a pattern like Qty\s+Description\s+Price.

Use this property when label sets are not available or when you need to match headers based on content rather than position.

This property specifies how many distinct header cells must be present in a row for it to be considered a valid table header. Increasing this value can help prevent false positives in documents with extraneous or partial header lines.

Example:
If set to 3, at least three header cells (such as "Qty", "Description", "Price") must be detected for the row to qualify as a header.

Adjust this value based on the expected number of columns in your table to improve detection accuracy.

Controls the vertical distance permitted between lines in a multi-line header. A value of 1.0 allows spacing up to the average line height, while higher values permit more separation.

Use this property to accommodate headers with extra spacing or to restrict detection to tightly grouped header lines.

Example:
For headers with double-spaced lines, set this value to 2.0.

Determines how aggressively the detector attempts to fill in missing or incomplete header cells by inferring their presence. A value of 0 disables repair, while 1 disables all repair attempts.

Use this property to improve header detection in documents with inconsistent or partially missing header cells.

Example:
Set to 0.25 to allow up to 25% of header cells to be inferred or repaired.

• Set this property to true if your table headers are consistent and shared across the entire document, such as in standardized forms or reports.
• Set to false to detect headers separately for each table region, which is useful for documents with multiple or variable table layouts.
• This property is only relevant when the table is inside a multi-instance Data Section.
• Enable 'Run Global' to optimize header detection for documents where headers do not change between tables, improving consistency and consistency.
• Use 'Run Global' to capture table headers which occur outside the bound of the containing Section Instance.