- Collect
- Validated form
- Exchange
- JSON submission
- Output
- Service-generated PDF
The page has collected structured answers.
Your Python page has fields, accepted Data and calculated results. The next step is to decide what completion means: a saved draft, an interchange file or a request to your application service.
A server endpoint can perform the authoritative checks and return a result. The application supplies its persistence and workflow. Portable offline delivery is a separate serverless bonus track; this tour does not require changing hosts.
A saved draft and an interchange file serve different purposes.
save and restore preserve a Bag’s typed values using TYTX. A JSON export is for another program: dates and decimals become textual representations. A file ending in .json is not necessarily an ordinary JSON export; the operation that wrote it determines the format.
Data in browser memory are lost when the page closes unless the person explicitly saves them or the application implements an approved persistence workflow.
The PDF belongs to the receiving service.
Your service could accept the submitted JSON, validate it, calculate the authoritative result and generate a PDF. Gramlot supplies the data handoff through sendHttp; the receiver, its authentication, PDF generation and presentation of the response are application integration work.
That makes a useful alternative to distributing a fillable PDF: an adaptive application collects the answers, while a PDF becomes the final output. It is an architecture you can build, not a bundled registration-to-PDF product.
The delivery boundary
Does a local calculation guarantee that a service will accept the submitted result?
Reveal the explanation
No. The receiving service applies its own validation, permissions and authoritative rules. A local estimate supplies feedback, not acceptance.
Try the working example and read the full contract
KEEP EXPLORING