Building a task form has always involved a second, invisible job: wherever the form needed a piece of data that already existed — a workflow step's output, a row from a connected table, a global variable — someone had to manually recreate a field for it and wire up the binding by hand. That's slow, and it's easy to mistype a path or pick the wrong component type for the data.
Field Explorer turns that into a drag: browse the data you already have, and drop it straight onto the form.
It's a tab in the Form Builder's left sidebar, alongside the component palette. Opening it gives you a searchable panel of everything the form could plausibly pull data from, organized into three sources.
Drag a field from any of the three sources onto the canvas, and Field Explorer does two things at once: it creates a form component of the right type for that data (a date field for a date column, a number field for a currency value, and so on), and it binds that component to the field's data path automatically. There's no separate step to open a binding picker and find the same field again — the drag is the binding.
Fields that are already placed somewhere on the form show a small usage badge in the Field Explorer panel. Click the badge and the builder jumps to that component on the canvas — useful for checking whether a field you're about to drag in is already there under a different label, or for auditing a large form's data coverage at a glance.
