Builder
Define your own record types once and get storage, lists, permissions, numbering and an audit trail from the same definition.
Builder is the metadata engine of Tosven. You describe a record type once, with its fields, links, lifecycle and permissions, and Tosven treats it like one of its own. This page explains what a definition contains and what you can use in the pilot today.
What a record type is
Every company has records no vendor planned for: site visits, permits, loan equipment, handover inspections. A record type is the description of one such record. It is configuration, not code. Builder runs no scripts. It offers a closed set of field kinds, lifecycle models, filters and permissions, so everything you configure can be validated, secured, audited and carried through an upgrade.
Customers runs on the same engine. Company, person and opportunity are built-in record types maintained by Tosven. Your own types share the same database, permissions and audit trail, and can link to the built-in ones.
How types are published in the pilot
The engine is live. The type editor screen is not released yet. In the pilot, you define a record type together with the Tosven team, and the team publishes it.
What a definition contains
- Fields. Text, number, money, date, select and link fields, plus child tables for lines. A link points to a real record, such as a customer or an order, never to a copied name.
- Lifecycle. A type is simple or documentary. A documentary record moves from draft to submitted to cancelled. A submitted record changes only in the fields the definition allows.
- Numbering. A unique id or a series such as
SV-{YYYY}-{####}, assigned in the same step that creates the record. See Record numbers. - Permissions. Read, write, delete and approve, granted per type.
- Sensitivity. Each field is public, internal, restricted or secret.
- Indexed and unique fields. A unique field refuses duplicates. Existing duplicates are reported before the rule applies.
Limits are set on purpose: a type holds up to 100 custom fields, of which 15 can be indexed.
What Tosven derives from it
The definition is the single source. Everything below is compiled from it and changes in the same step when the definition changes.
| Output | What you get |
|---|---|
| Records | Create, edit, submit and cancel, with validation and conflict detection |
| List | Filtering, sorting and paging with one filter language |
| Permissions | Row filters and field redaction applied to every reader |
| Audit and events | One log with the changed fields, the actor and the definition version |
| Agent tools | Search, read and propose tools for types whose fields are described |
These five are live in the pilot. Live in the pilot
An agent's proposal is a draft that a person submits. No generated tool deletes permanently, changes permissions or changes a definition. See Agents.
Record count and total over a money field are part of the Lens catalogue and drill to the records behind the figure. Lens measures for the types you define yourself are on the way. On the way So are form layouts generated for your own types. On the way
Permissions and sensitivity
Permissions are enforced where the data is read, not on each screen. The same row filter and the same redaction apply to a list, to an agent's tool output and to search results.
- Row filters. A type can limit which records a role sees.
- Field sensitivity. The class of a field decides who sees the value, whether it appears in default list columns, whether it may feed semantic search, and whether an agent tool may return it.
- Restricted and secret fields. Reading them needs an explicit permission. This also applies to totals.
- Secret values. In the audit log they appear only as a hash.
Roles are described in Companies and roles.
Changing a published type
Definitions are published as versions, and each record remembers the version it was written under.
Add a field
An additive change takes effect when the new version is published.
Tighten a rule
Making a field required first runs a scan of existing records. The scan lists the records that would break the rule.
Decide how to enforce it
Fix the listed records first, or apply the rule to new writes only, from a date you choose.
Publish
Existing records keep their version. The audit log records the change.
A type that is no longer needed is retired: no new records, and the existing ones stay readable.
Field keys are permanent
A field's key and type are fixed once the type is published. Renaming or retyping is an explicit operation, never a silent one.
What is on the way
On the way
- Type editor screen, so you can define and publish types yourself.
- Generated form layouts for your own types.
- Custom fields and sections on built-in types.
- Declarative states and transitions beyond draft, submitted and cancelled.
- Lens measures and Channels record cards for your own types.
- Public REST API, webhooks and CSV or Excel import.
Next steps
- Customers: the built-in record types your own types can link to.
- Lens: how record counts and totals become figures that drill to the record.
- What is live today: the list per module.