Skip to main content

Data Export

Export capabilities help teams move from execution visibility to external reporting and audit workflows.

What this means​

Data export turns internal execution history into reusable external outputs for review, reporting, and analysis.

Why it matters​

Teams need to move evidence and traces beyond in-product dashboards:

  • compliance/internal review packets
  • BI and operational analysis
  • incident investigation workflows

How Subbasis handles it​

Export strategy is tied to governed execution entities:

  • workflow execution records
  • evidence events
  • trace data
  • approval history
  • connector outcome snapshots

Export planning​

  • Define export cadence
  • Keep evidence schema stable
  • Align export scope with plan limits

Example scenario​

Monthly operating review:

  • export workflow outcomes
  • aggregate approval timings
  • analyze retry/failure clusters
  • validate policy adherence trends

What to configure​

  • export format and destination
  • field mapping and redaction rules
  • cadence and retention policy
  • access controls for exported datasets

Limits and deployment notes​

  • Export depth and volume depend on plan and deployment profile.
  • Sensitive fields should be governed by policy and role boundaries before export.

See Reference API.