Preserve Form Content

Ask the Community
, ,
2

Hey @ggsmith842 !

Off the bat

Option 1 — Rebuild the form with Workshop primitives (no code)

Instead of using the action’s built-in form, wire everything manually:

  1. Drop individual input widgets (Text Input, Number Input, etc.) onto your canvas — one per parameter

  2. Each widget stores its value as a Workshop variable

  3. Configure your button’s action to reference those variables as the action parameters, rather than using the auto-generated form

  4. On failure, the variables retain their values because you own them — Workshop won’t reset them

  5. The one thing you take on: you need to handle reset logic yourself (e.g. a “Clear” button that resets all variables to null/default)

This is the fastest path and requires zero code.

Option 2 — Custom Widget or OSDK Component (full control)

If you need richer validation UX (inline field errors, partial highlights, etc.), build the form as a custom widget or an OSDK-backed component. You own the full state machine, you decide when to clear, what to surface on error, and how to re-invoke the function. More investment upfront, but the right call if the form is complex or user-facing polish matters.

Good Luck

Nico