Skip to content

Form data sources on the task form

Use the Demo Projects HQ task form to see how App Connect and Server Connect data sources feed projects, contacts, and tag choices into real form controls.

Real form controls depend on live data sources

Section titled “Real form controls depend on live data sources”

The new-task page is not driven by static markup alone. Projects, contacts, and tag suggestions all arrive through data components first, then feed the controls users actually interact with. This tour stays on that page so the data-to-field relationship stays concrete.

Server Connect components load the option data.
App Connect bindings feed that data into form controls.
The field stays readable because source data and displayed choice are kept separate.

The task form pulls several datasets into one page

Section titled “The task form pulls several datasets into one page”

The task form is useful because it depends on multiple upstream datasets at once. Projects, contacts, and tag suggestions are all loaded before their controls can behave properly, so the page becomes a good map of data-source responsibilities.

#task_project depends on the projects dataset, not on hard-coded option rows. That is what lets the same field stay useful as projects change over time without rewriting the control itself.

#task_assignee is a separate control, but the same principle applies: the form stays flexible because the contact options come from data that already belongs to the page, not from a duplicated static list inside the markup.

#task_tags shows that richer widgets still follow the same source-data rule. Tagify only feels guided because the suggestions are loaded first and then mapped into the control, rather than being invented at interaction time.

The task form becomes much easier to reason about when you separate where option data comes from from how the control presents it. That is the bridge from ordinary form markup into practical App Connect form work.

Load option data before expecting controls to use it.
Keep source datasets readable and reusable.
Treat field chrome and backing data as related but different concerns.