Skip to content

Tool

Forms Recognition template library analyzer

Review WFR project inventory using mapped CSV columns, a parsing preview, author distribution and date checks. Validate findings against processing results.

What this tells you

A template list can help inventory supplier-specific configurations in a Forms Recognition project. This tool reports recorded authors, dates to review and supplier-name matches. It does not inspect recognition logic, learned data or business rules. Paste a template list and, optionally, an active supplier list. The tool processes these inputs in the page; it does not upload or save them.

The template library

Comma, tab or semicolon separated. Quote fields containing the delimiter or a line break; double any quote inside a quoted field. Dates: YYYY-MM-DD.

One per line, from the ERP supplier master. Names are matched after case and whitespace normalization; aliases are not inferred.

Age is a review prompt, not evidence that a template is defective.

Set to the browser’s current UTC date after the page loads. You can choose a different review date; analysis requires a valid date.

How to read the result

  1. Recorded authors are not current owners

    Concentrated authorship is a prompt to identify current maintainers and documentation. Blank authors are reported separately; a historical author field does not establish present ownership.
  2. Older dates prompt review

    A stable template can remain correct for years. Check real usage, retention obligations and historical-document needs before retiring a template, even when its supplier is absent from the active list.
  3. Name matching does not measure extraction coverage

    Supplier aliases are not reconciled automatically. An unmatched supplier may work well with a generic model. Measure document-level accuracy and review rates before inferring manual work or benefits from a replacement.
  4. Several templates for one supplier deserve a look

    Header and line templates are normal. Several variants can be legitimate. Compare their purpose and use before identifying duplicates or retirement candidates.

The full project analysis

A project assessment maps configured recognition methods, field definitions, learned examples where used, confidence thresholds, validation scripts and ERP business rules. Representative documents and observed processing results are needed to measure extraction accuracy and verifier review load. Assess which rules can be retained, adapted or rebuilt for the exact target release or extraction approach, then validate the result against the same document set.

Background: Forms Recognition explained · Forms Recognition options at the 12c boundary · WFR versus OCI Document Understanding

Questions

What do I paste?

Use four columns: template, supplier, author and last modified. Commas, tabs and semicolons are supported, including quoted delimiters, escaped quotes and quoted line breaks. Headers are recognized only when all four mappings are unambiguous; otherwise choose the header mode and map the columns. Dates must be YYYY-MM-DD. The active supplier list is one literal name per line.

Does anything leave the browser?

No. The lists are parsed in the page and nothing is stored or transmitted. The analysis of a full project export, described below, is a separate request handled under a written engagement.

What counts as a stale template?

One whose last-modified date is older than the threshold you set, three years by default. Stale is a prompt to check, not a verdict: a template for a supplier whose invoice layout has not changed can be old and correct. Check actual use and retention needs before deciding to retire it.

What does the full analysis add?

The project export itself is read: field definitions, confidence thresholds, validation rules and sample-document references per template. That gives a field coverage matrix, a review of verifier requirements, and an assessment of how cleanly each template’s rules carry forward into either a supported Forms Recognition estate or a different extraction approach. Actual review load needs representative document-level evidence. The analysis is available by request; use the contact form and mention Forms Recognition.

Turn the result into the next question.

Describe what you need to understand from the tool. Keep raw inventories, credentials and customer information out of the inquiry; any evidence collection is agreed separately.