Skip to main content

Workflow, Query, and Security Behavior

Spreadsheet Forms can be used in workflows like other OSPROV form types, with additional behavior for named cells, spreadsheet snapshots, data protection, API submission, and mobile/PWA access.

Workflow Usage​

Spreadsheet Forms can be attached to workflows like other form types. They are supported in:

  • Initial workflow submissions
  • Public submissions
  • Draft edits
  • Submitted edit flows
  • Workflow action tasks
  • Bulk action tasks
  • Workflow prefill flows

Query Builder and Submission Lists​

Every named spreadsheet cell becomes available as a submission column. Spreadsheet field types are mapped for query behavior:

  • Number fields map to number-like query behavior
  • Date fields map to date/datetime-like query behavior
  • Dropdown fields map to select-like query behavior
  • Text fields map to text-like query behavior

Only named cells are extracted into submission data. Unbound cells remain part of the visual document snapshot but are not exposed as named report fields.

This is the same reason bindings are required during form creation: OSPROV needs an explicit field name, label, type, and cell address before it can treat a spreadsheet cell like a normal form field.

Data Protection​

OSPROV data protection can mask spreadsheet cells in snapshots. When a user is not allowed to see a protected field:

  • The protected cell is masked in the viewer
  • The protected cell is masked in XLSX export
  • Action flows preserve the original protected value instead of saving the mask text back into the real submission

API Behavior​

Spreadsheet Form API submission is currently blocked. API submission endpoints return an unsupported response for spreadsheet forms because the API path expects the standard form submission structure, not spreadsheet_submission snapshots.

PWA/Mobile Behavior​

Spreadsheet Forms are not yet supported in the mobile/PWA app. PWA pages show an unsupported message instead of mounting the spreadsheet editor.