Skip to content

Data Lifecycle & Storage

EntryLayer manages two related but different kinds of data: customer source data that remains in Snowflake source objects, and app-managed state that supports forms, permissions, workflow, audit history, and billing.

When this matters

Use this page when you need to understand:

why project creation does not copy an entire source table
how draft form design becomes published user-visible layout
when a virtual source row becomes a materialized submission
where audit and billing records live
how SQL API build operations relate to runtime user behavior

Lifecycle map

Source object metadata
  -> project
  -> draft form version
  -> published form version
  -> virtual source rows
  -> materialized submissions when workflow/local state is needed
  -> workflow history, field history, access history, audit log

Storage by concept

Concept	Stored by EntryLayer?	Storage location	Notes
Source table/view rows	No, not up front	Customer-owned Snowflake objects	Read through customer-approved source access.
Semantic view metadata	Metadata only	Used during source validation/layout	No semantic result row sampling during validation.
Project metadata	Yes	Hybrid Tables	Includes name, source binding, status, folder, and settings.
Form drafts and published versions	Yes	Hybrid Tables	Draft changes require publish before users see them.
Field registry	Yes	Hybrid Tables/form version state	Stable ids support automation and layout changes.
Project access	Yes	Hybrid Tables	Separate from seat type and Snowflake source grants.
Virtual submissions	Not as full local records	Source-backed until materialized	Visible in work queues before local submission state exists.
Materialized submissions	Yes	Hybrid Tables	Created when workflow, local edits, or app-managed state are needed.
Audit and history	Yes	Hybrid Tables	Tracks app-managed workflow and record history.
Billing ledger	Yes	Hybrid Tables	Supports seat-oriented billing operations.

There is no PostgreSQL sidecar in the current package.

Project and form lifecycle

Stage	What happens
Source validation	EntryLayer describes source metadata through the documented source access path.
Project creation	Project metadata and an initial layout are created.
Draft editing	Builders or Cortex modify sections, rows, fields, validations, rules, workflow, or settings.
Publish	The draft becomes the user-visible published form.
Archive/restore	Archived objects stop appearing in normal active workflows until restored where supported.

Draft operations are powerful because they can change the user experience. Use targeted SQL API procedures for small edits, and publish only after validating the draft.

Submission lifecycle

Stage	Behavior
Source-backed row	Row exists only in the customer’s source object.
Virtual submission	Row appears in EntryLayer lists without a full local submission record.
Materialized submission	EntryLayer creates app-managed state for workflow, local field values, and audit history.
Workflow history	Status changes and review actions are tracked in app-managed history.
Extract/report	Customers can use documented SQL extract surfaces for downstream Snowflake workflows.