Partial configuration check on a separate test installation; see the checked controls and limits below.
What it does and when to use it
Creates a configurable form and its submission actions. Use it for the specific job described below. If a simpler native element can deliver the same outcome, prefer the simpler structure and fewer competing styles.
Before you start
This is a Breakdance catalogue recipe for use with a compatible Breakdance Elements for Oxygen extension. It is not a guarantee of availability in your version. Check the installed element list and official reference before following the steps. Exact control labels can differ; this recipe has not been executed on this site. Oxygen also requires the dedicated Breakdance Forms extension for this form workflow.
Worked example: A project enquiry form with actionable submissions
Scenario: A project enquiry form with actionable submissions. The goal is a useful result on a real project, not a claim that this scenario was a completed client project.
- Choose only necessary fields, such as name, email and project summary.
- Configure the supported submission action, recipient and clear success message in a staging setup.
- Test required fields, invalid email and a successful submission before using it publicly.
Checked controls and test limits
Checked on 4 October 2026 with Oxygen 6.2.0-beta.9, Breakdance Elements 1.1.0-beta.5 and Forms 1.1.0.beta.1 on a separate test installation.
The test form used Name, Email and Project summary, all required, plus a clear submit label and success/error messages. Actions stored the submission and prepared an email. Anonymous submissions with a missing CSRF token, missing name or invalid email were rejected; a valid submission was stored. The email action was intercepted in the private test, so inbox delivery is still unverified. Configure the sender and recipient explicitly and verify delivery separately before launch.
This is a partial configuration and frontend check, not verification of every setting, integration or accessibility requirement. Use Oxygen’s interface for these settings.
Expected result
You should have a project enquiry form with actionable submissions. Verify the result on the frontend using the same content or object described in the steps. A correct builder preview alone does not establish that links, data or interactions work for visitors.
Troubleshooting
If the success message appears but no enquiry arrives, inspect the action and delivery configuration. In Oxygen this element also depends on the dedicated Breakdance Forms extension.
Checks before publishing
Use real text and assets rather than a perfect placeholder. Check a long label, narrow screen and empty-data state before publishing.
- Compare desktop and narrow-screen layouts using actual content.
- Follow every destination and operate interactive controls with a keyboard where applicable.
- Check an empty or unavailable-data state when the element depends on a provider.
Official reference and version notes
Official Form Builder reference provides the current provider information. This is independent, AI-assisted documentation on Benjamin Olsen’s website; examples are clearly identified as practice recipes.
Check extension element visibility in Oxygen. An element may be hidden where a native equivalent exists.