publish offhistory off
Live on save
A change is live as soon as it is saved. There is no release step, and earlier versions are not kept.
← All capabilities
Available now
Platform capability · Structured Records
Choose publishing and version history for each record type
Define a record type once, then choose publishing and history for it
Describe each kind of business record as a record type with typed fields, and get the working admin features around it: validated create and edit forms, searchable tables, import and export, and stable APIs. Each record type chooses how its entries behave. Turn publishing on when working entries need a separate published state. Turn version history on when earlier versions must be kept and restored. Turn on both, or keep the simple model in which a change is live when it is saved.
Two independent controls
Pick the combination for each record type
Publishing controls when changes become visible. History controls whether earlier revisions can be recovered. Turn on exactly what each record type needs.
publish onhistory off
Controlled release
Editors prepare changes privately, and readers keep seeing the last published version.
publish offhistory on
Restorable history
A change is live as soon as it is saved, and earlier versions stay available to view and restore.
publish onhistory on
Governed lifecycle
Working and published states stay separate, with a complete history of versions that can be restored.
Built in
What you get
- Record types with typed fields, and validated APIs to create, read, change and delete records
- Generated forms, searchable tables and columns you can configure
- Optional publishing of entries, set for each record type
- Optional version history of entries, set separately
- A published version stays unchanged while the working entry continues to change
- Version history with the current, published and restorable versions
- Each version of a record type has an explicit version number
- Bulk import, export and sample files use the same record type definition
Under the hood
How it works
A record type produces forms, tables and APIs
Declare the fields, types, validation, search and list behaviour once. The platform turns that definition into validated APIs, forms and tables, so a new kind of business record does not need its own forms and API code. Each record type has versions, which gives integrations a fixed version to rely on while the next one is prepared separately.
Publishing is a choice for each record type
Some records can be live as soon as they are saved. Others need a working entry that changes privately while the last approved version stays published to outside readers. Turn on publishing only for those record types. The others stay live on save and have no extra publish step.
History is a separate choice
Publishing and version history are independent. A record type can keep earlier versions of entries without a publish step, publish entries without a long history, turn on both, or use neither. When history is on, users can view and restore earlier versions, and other record types are not affected.
Pairs well with
Related capabilities
Admin Data Tables
Tables with paging, filters and saved layouts, included
Data Import & Export
Reusable CSV and JSON import and export for your record types
API Governance
The same access levels, errors, paging and health checks on every service
Audit
An audit trail that can only be added to, where tampering shows
Want a deeper walkthrough of Structured Records?
A solution architect will demo the live service against your domain model.