Release 2026.10.18-1

Catalogs become Lookup Tables, Hosting Options becomes a six-step wizard, and reviewers can edit nested tables in the viewer.

Cloud, United States
Cloud, Australia
Self-hosted image
ghcr.io/docaifabric/docaifabric:2026.10.18-1

Improved

  • Catalogs are now Lookup Tables, and Repositories are Knowledge, in the app, in rule code and for AI agents. The old names keep working. See Table Lookup Rule.
  • The Deployment page is now Hosting Options (Preview), a six-step wizard: models per task, the license apart from hosting, what this installation allows today, and the whole estimate on paper. See Hosting Options.
  • Reviewers can edit nested tables in the viewer. A table can no longer be added inside a table.
  • A transaction rule’s changes to fields are applied, checked by the changed field’s rules and saved, in the Validate step, in Revalidate and on edits. A passing transaction validation rule set to confirm confirms its fields in the Validate step and removes their low-confidence review issues.
  • Rules no longer take a confirmation back: a field can show as confirmed with an error beside it. Rules no longer replace the reviewer’s name on a field the reviewer confirmed, and a transaction rule that reports a problem on a document no longer confirms its fields.
  • Rules that chain on one field always read the value the rules before them left, so results can change where they did not before.
  • Rule Studio warns when code would fail in strict mode (an undeclared variable, a global write). It never blocks a save.
  • Faster rule execution, and Monitoring loads faster.

Fixed

  • Extraction policies apply in projects whose fields all belong to a class; they were not applied there since 2026-10-04. Re-extract matches policies on the extracted values.
  • The Validate step writes and confirms nested-table cells in place.
  • A lookup table that cannot be read fails, instead of reading as empty.
  • Project export, import and Library copy carry the records of large lookup tables.
  • Revalidate loads the transaction from its own project.

API

  • One-step processing takes source files only: documentText and ocrData are no longer accepted (they were never processed), and a request without a source file is refused. See Process documents.
  • Business rules and Data Transform scripts: the lookup table API is lookup_table. catalog, its old name, still works. See Custom rules.

Upgrade notes

  • Rules written with lookup_table do not run on an image older than this one. If you roll back, replace lookup_table with catalog in those rules.

All releases