Form controls

Ready-made controls for your forms.

13 official web components — charts, saved reports, address search, maps, signatures, ratings, tables and more. Install one and it appears in the form designer's Custom palette. Each runs in a sandboxed frame, follows your form theme in light and dark mode, works with a keyboard and a screen reader, and shows its value as text on completed tasks and on mobile.

Show
Uses

14 controls and bundles

Security

Sandboxed by default, host services by permission

A control runs in an iframe with an opaque origin and a strict Content-Security-Policy: no cookies, no access to the page, no network. It talks to the form through a typed postMessage bridge that checks every message. Anything more is a capability the manifest declares and the host grants:

Lookups lookup
Suggestions come from the field's lookup source — a data table, or an API reference the UserTasks server calls with credentials stored on the server. The control only sees the suggestions.
Saved reports reports
Rows of the saved report the designer chose (the field's report_id, read by the server from the stored form), run as the person filling in the form: only reports they can open, with their permissions.
Files files
Uploads go through the Attachments pipeline (the same checks and storage). Reads are limited to files the form already gives the control: its own value, or an Attachments field the designer maps.
Network network
Fetches only from the hosts in its manifest, and only after an administrator approves them in Extensibility → Form controls. Until then the frame's CSP blocks every request. Map tiles come through the UserTasks server (public tile servers refuse the sandboxed frame's referrer-less requests), only once the tile host is approved.

Google Places: the address control never holds an API key. It asks the UserTasks server for suggestions; the server calls Places API (New) through an API reference whose key is stored encrypted in an integration. A key in the browser would be exposed — and a sandboxed frame sends no referrer, so referrer-restricted keys could not work there anyway.

Install

From the gallery to your form in a minute

  1. Step 1

    Install

    In the app: Extensibility → Form controls → Browse gallery (or Automations → Packages → Browse gallery → Form controls). Or download the .utpkg here and import it.

  2. Step 2

    Set up

    Most controls need nothing. The address control asks for a Google Places API key (stored on the server); the map needs an admin to approve its tile hosts.

  3. Step 3

    Use

    Drag the control from the designer's Custom palette onto a form, set its properties and map its context fields. Its value flows into the workflow like any field.