simulator-smart-forms-runtime

Yes, you can drive server-driven UI state machines end-to-end by orchestrating data collection, validation, and navigation through the CDU protocol. It reads attachments, maps inputs to form fields, and follows flow progression with deterministic actions via appGetPage/appSendForm tools.

Smart Form flows handle irreversible actions during conversational data collection by enforcing explicit confirmation gates. This ensures that critical side effects or final form submissions only occur after deliberate user approval within the multi-page interaction flow.

Yes, you can use attached documents to populate form fields in a Corezoid workflow. The runtime reads attachments, maps the extracted input data to the appropriate form fields, and enables document-driven batch runs for complex flows.

You need an existing Smart Form flow and a production environment to run Smart Form flows. The runtime drives existing flows to completion via the appGetPage/appSendForm protocol but does not build or edit the Smart Forms themselves.

Building Smart Forms involves creating and editing the server-driven UI forms, whereas running Smart Forms means driving an existing flow to completion within a conversation. This runtime skill focuses solely on executing the flow, gathering inputs, and submitting forms with side effects.