These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Form Builder Platform
- Features
- Form definitions
Form definitions
Keep a form revision ready for publication.
OverviewMy form definitions×
Form Builder Platform · Form definitions
New
My form definitions
Form definitions
| Number | Name | Revision | Status | Owner | |
|---|---|---|---|---|---|
| FD-93618 | Definition 803 | 810 | Draft | ||
| FD-60866 | Definition 624 | 750 | Validated | ||
| FD-19393 | Definition 621 | 250 | Published | ||
| FD-81318 | Definition 550 | 100 | Retired | ||
| FD-17004 | Definition 808 | 100 | Archived |
6 of 6 records
Definition 803Form definitions · FD-93618
DraftRevision810
What you can do
Keep a form revision ready for publication
A Form Owner starts with the organization and a named form. The definition carries its number, revision, schema version, owner and state. The owner records the required setting, condition expression and validation rule before asking an Independent Reviewer to inspect the revision. A validated revision is the candidate for publication. A published revision is the parent for submitted lines; changing the working design starts another revision rather than obscuring the earlier decision.
The form number identifies the working form, while the revision and schema version identify what was reviewed. Keep the earlier published definition available when a correction creates a successor Draft. A later submission remains linked to the definition that governed it, so the owner can explain why the earlier decision was valid.
How the work is organized
- Own the draft. The Form Owner records the organization, owner, field definition and schema rule on the revision.
- Validate before review. Check both sides of each condition, then move the Draft to Validated.
- Publish the reviewed revision. The Independent Reviewer records a decision for that source revision; the Operator publishes the Validated form and checks its operation trail.
What to agree during setup
The owner checks that the form name and number identify the right operating use, that the field policy belongs to the same organization, and that the schema version shown to operators is the one reviewed. A condition should be tried with both a response that activates it and one that does not. The reviewer records a decision against the exact revision, so later corrections have their own decision trail.
Agree which form number and schema version operators will recognize. A correction uses a successor revision and a lineage number, so an older definition stays identifiable. The Form Owner and Independent Reviewer should inspect the same revision before the Operator publishes it.
Check the handoff on an actual case
Choose a form used for a real intake. Record one required answer and one conditional answer, then compare the validated definition with the decision. After publication, submit a line and confirm that its parent points to the intended revision. For a correction, retain the earlier definition and make the successor Draft. The previous result and state change should remain explainable.
After the pilot publication, compare the decision source revision with the published definition and the state history. Attach a Pending submission to that published parent. If the owner later changes a rule, start a successor Draft and leave the original parent on the earlier line.
What your team sees
- Definitions in progress — Find Draft and Validated revisions awaiting checks or a decision.
- Published form board — Compare published revisions with the versions awaiting publication or retirement.
Follow the work through
See definition and publication and submission review for the decisions that connect this module to the next one.
What it keeps track of
Data model- Form definitions
- Versioned published form schemas with conditional logic and validation rules.
- Field definitions
- Versioned field and policy definitions used to compile form schemas.
- Review decisions
- Independent review decisions recorded against an exact source revision.
- State history
- Immutable state transitions recorded for each form definition revision.
Who uses it
Permissions- Form Owner
- , Independent Reviewer and Operator handle definition, decision and publication.
- Admin
- Maintains access.
Set up Form Builder Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.