Appearance
Connected-data and payment fields
These fields depend on data collections, workflows, or payment configuration. Build and test their dependencies first; adding the field alone is not enough to make the feature work.
Detailed setup guides:
Big Data Dropdown
Use BigData Dropdown to populate a list from a Big Data Collection instead of typing every choice into the form.
Settings
| Setting | What it does | Guidance |
|---|---|---|
| First choice text | Shows the empty prompt at the top of the list. | Use a clear instruction such as Select a supplier. |
| Configure BigData query | Opens the configuration for the collection, collection field, and lookup/filter query. | Use only a collection and field that the form is allowed to expose. |
| Collection | Defines the Big Data Collection that provides choices. | Select the smallest appropriate data source. |
| Collection field | Defines the field used as the choice value/label. | Use a stable, human-readable field. |
| Lookup/filter query | Limits which collection records become choices. | Test the query with expected and unexpected input. |
The dropdown needs a collection, a collection field, and its generated public endpoint in order to fetch choices. If configuration is incomplete, no data is loaded.
Do not use this field to expose a collection containing confidential, personal, or cross-company data. Test the public respondent experience, not just the editor view.
Current User
Use Current User when a workflow-aware form should automatically populate the current user’s email address. It is not intended for a public form where no authenticated current user exists.
The field provides an auto-populated email placeholder and standard email validation. Test it in the actual workflow context so you can confirm which user is resolved and what happens when no user is available.
Big Data Row Viewer
Use Big Data Row Viewer when a form must display or work with fields from one selected row in a Big Data Collection.
Configure the collection
- Add Big Data Row Viewer from the Fields tab.
- Select it, then choose Configure BigData collection in the Edit tab.
- Choose the collection.
- Define a filter that selects exactly one row.
- Select OK.
- In the viewer’s editing toolbar, use Add to include appropriate scalar collection fields or Remove to remove an included field.
The collection must be selected and the filter must be valid. The viewer supports scalar string, Boolean, integer, and floating-point fields; collection arrays and the internal _id field are not offered as regular mapped fields.
Use a filter that reliably selects one record. If it can select zero or multiple rows, the result will be ambiguous or unavailable. Changes to a collection’s schema may require you to remove or remap fields in the viewer.
Product
Use Product to offer an item for purchase and add it to the form’s shopping cart.
Settings
| Setting | What it does |
|---|---|
| Product picture | Uploads or selects the product image. |
| Picture layout | Places picture left/description right, picture top/description bottom, or picture right/description left. |
| Price | Sets the price of one unit; its currency follows the Payments currency setting. |
| Unit name | Describes the item unit, such as seat, hour, or piece. |
| Product description | Describes what the respondent is buying. |
| Product choices | Adds selectable variants where configured. |
| Add to Cart button text | Sets the button label seen by respondents. |
| Button colors | Sets the add-to-cart text and background colors. |
Do not rely on a Product field until payment processor, currency, tax/discount rules, cart behavior, and confirmation flows have been tested end to end with non-production payment data.
Shopping Cart
Use Shopping Cart to show products, calendar items, shipping, discounts, taxes, subtotals, and totals added during form completion.
Settings
| Setting | What it does |
|---|---|
| Show counter | Shows the row index in the cart listing. |
| Show pictures | Shows product pictures when available. |
| Show unit type | Shows the unit name for each product row. |
| Show unit price | Shows the per-unit price for each product row. |
| Empty-state text | Sets the message displayed when no cart items have been added. |
Keep the cart visible near the product-selection flow. A respondent should be able to understand what they added, the price, and how to remove an item before submitting.
Payment Processor
Use Payment Processor to let respondents select among active payment gateways for the form. It shows an empty-state message if no gateway is active.
Before adding it to a production form:
- Configure at least one gateway in the Payments area.
- Confirm which gateway is the default.
- Test a payment and failure/cancellation path in the provider’s safe test mode where available.
- Confirm receipts, notification recipients, and unpaid-submission behavior.
Do not place a payment form into production based only on a successful editor preview. The real payment journey must be tested with the configured gateway.