Webform Composite Settings

Webform's Custom composite element is a quick way to group a few fields together, but its builder only lets you set a handful of properties on each sub-element: key, type, title, description, help, placeholder, options and required. If a sub-element needs anything more than that, say a date range, a number minimum, a maximum length or a condition, there is no form for it. You have to write the property as YAML in the "Custom properties" box, which is hidden from anyone without the "Edit webform source" permission. The Webform maintainers have chosen to keep the builder minimal, so this is not something a future Webform release will add (#3008728).

This module solves this. It adds a "Sub-element settings" button to every row in the composite's Elements table. Clicking it opens the sub-element's full configuration form in a modal, the same form Webform shows for a normal element of that type, with its General, Conditions, Validation, Access and Custom properties tabs and anything else the element type offers. The only settings left out are the ones that do nothing inside a composite: Administration, Submission display, Cardinality and Flex.

The modal does not save anything on its own. When you apply it, the values go back into the row, and they are stored with the composite when you save the element, just as if you had typed them into the table. The element plugin validates the input, so the modal catches the same mistakes the regular element form would.

Features

• Every setting an element type supports, available on sub-elements without touching YAML.
• Conditions and access rules on individual sub-elements. Webform already honours them inside composites; it just had no way to set them.
• Edits that stay with the composite until you save it. Reopen a sub-element before saving and your pending changes are still there.
• The same alterations other modules make to the element form, including Webform Validation and Webform Simplify.
• A plain, JavaScript-free fallback that saves the sub-element directly. The modal needs JavaScript. If it is unavailable, the button opens the settings form as a normal page, and saving that page writes the sub-element straight to the webform instead of staging it in the table.
• Support for Drupal 10.3, 11 and 12.

Requirements

Webform 6.2 or later, with the Webform UI submodule enabled.

Things to know

• The button appears once a row has been saved. Add the sub-element, save the composite, then open its settings.
• Options can still be edited in the table, because Webform insists on them before it will save the row. The modal edits the same options, so use whichever is handier.
• Webform does not enforce the "view" access rule on sub-elements when it displays submissions. The module does not change that.