Preview: this language version was translated with machine assistance and has not been reviewed by a native speaker. Search engines are asked not to index it.

Operation record (manifest.json)

Short answer: The operation record is the "filename.manifest.json" written next to the output file each time you save. It records the input and output fingerprints and the check results for that run, but not the replaced or deleted text itself.

Last updated:

What it contains

FieldContent
type, version, kindRecord type, format version, operation type (replacement or redaction)
created, appCreation time, software version, and engine and recognition model versions
source, outputFile names and SHA-256 of the original and output files
rules, countsNumber of rules and various counts
readbackRead-back verification: number checked, passed, needs review, failed
residueResidue check results for redaction, item by item
riskRisk decision
hitsFor redaction, the category, page and position of each hit (no text)

Uses

  • Deliver it with the file, so the recipient can confirm the file is the output produced at that time.
  • Keep it in the project or case file as a record of what processing was done.
  • In batch processing, it is summarized in the processing report.

You can check it in your browser with the operation record verifier. In windowless mode, turn it off with PDF_MANIFEST=0.