Default Field Mappings

Most API action types interact with standard fields — status, approved_by, approved_at, archived. Default field mappings tell the platform which column on each datastore maps to which semantic concept, so generic actions work without per-datastore code.

Standard Semantic Fields

• status — workflow state (e.g. draft, submitted, approved, rejected).
• archived — boolean; if true the record is hidden from default views.
• locked — boolean; if true edits are blocked.
• approved_by, approved_at — audit trail for the approval action.
• archived_by, archived_at — audit trail for archival.
• owner_user_id, owner_tenant_id — for ownership transfer.

Why Override the Defaults

If your datastore predates the platform conventions, its columns may have different names. Override the mapping so actions work against your existing schema. For example, an old datastore may have state instead of status, or deleted instead of archived.

How to Override

1. Open Architect Panel → Datastores → (table) → Field Mappings.
2. For each semantic field, pick the actual column from a dropdown.
3. Save.

Worked Examples

• Legacy orders table: The state column maps to status; the deleted column maps to archived. Generic Approve / Archive actions now work.
• Custom field names: An app uses doc_owner instead of owner_user_id — map accordingly; Transfer Ownership works against it.
• Multi-tenant override: One tenant has historical schema with different column names; override per-tenant in Per-Tenant Configuration.