PRING Help

Audit log of output files (File Log app)

Created: Updated:

Press Create File Log app on the Audit log tab. PRING creates a PRING File Log app in your kintone (20 fields, 3 views, view and add only) and records every output, attachment, replacement and deletion with time, version, file name and SHA-256. Nothing is stored on PRING's servers. Per template, PDFs can carry the document ID and the pre-stamp SHA-256.

Steps

  1. 1. Open the Audit log tab

    Press the Audit log tab in the settings screen. If there is no File Log app yet, the tab says that recording starts once the app is created.

  2. 2. Press Create File Log app

    An app named PRING File Log is created with 20 fields, 3 views (newest first, by source record, match by hash) and permissions (everyone: view and add only; nobody can edit or delete), and it is set as the log destination. If you lack the permission to create apps, ask a kintone administrator to press the button on this screen, or enter the ID of an app the administrator created.

  3. 3. Check Change history on the log app

    As the confirmation message says, open the log app's settings, General settings, and make sure Record change history is enabled. Then kintone keeps its own history even if a log row is later edited.

  4. 4. Choose Embed hash in PDF on each template

    In the template editor, set Embed hash in PDF to none, metadata or footer. With footer, each PDF page carries the document ID and the pre-stamp SHA-256 at the bottom, so anyone holding the PDF can look it up in the File Log app.

  5. 5. Map the search fields for electronic bookkeeping

    Also in the template editor, choose the fields that hold the transaction date, amount and counterparty under the electronic bookkeeping search items. Each output copies those values into the log row, so the log app views can be searched by date, amount and counterparty.

  6. 6. Read the log

    Every output, attachment, replacement, deletion and download adds one row: operation (add, update, delete, download, duplicate version, ingest, evidence bundle), route (export, bulk export, record edit, record delete, AI reading, evidence bundle), version, file name, SHA-256 and document ID (request ID). Paste a file's SHA-256 into the Match by hash view to find its row.

Frequently asked questions

Is the log sent to PRING?

No. The audit log lives only in the File Log app inside your kintone. PRING's server computes the SHA-256 of each generated file and returns it; its own operational log keeps one line per file (app, template and record numbers plus the hash, never file names or values) and no file bodies.

The SHA-256 printed inside the PDF differs from the SHA-256 of the downloaded file

That is expected. A file cannot contain its own hash, so the PDF carries the SHA-256 of the PDF before the stamp was added. The final file's SHA-256 is stored as a separate value in the log row. Look up the document ID in the File Log app to see both.

Are scheduled outputs logged?

Scheduled output does not pass through the plugin, so it is not logged at generation time. Files attached to records are logged when someone opens that record in a screen with the plugin loaded.

We deleted the log app

Press Create File Log app again on the Audit log tab, or enter the ID of a remaining app. Rows of the deleted app cannot be recovered. The app's permissions forbid deleting rows, but the app itself can be deleted by kintone administrators, so keep app administration rights narrow.