Skip to content

[#6106] Adapt admin form designer to the new type form field#6117

Draft
vaszig wants to merge 14 commits intofeature/6098-introduce-a-single-page-formfrom
feature/6106-adapt-form-designer-according-to-the-new-form-type-field
Draft

[#6106] Adapt admin form designer to the new type form field#6117
vaszig wants to merge 14 commits intofeature/6098-introduce-a-single-page-formfrom
feature/6106-adapt-form-designer-according-to-the-new-form-type-field

Conversation

@vaszig
Copy link
Copy Markdown
Contributor

@vaszig vaszig commented Mar 25, 2026

Closes #6106

Changes

  • disable introduction page (see comment [OF#6144] Load the correct variant according to the form type open-forms-sdk#962 (comment))
  • reset and hide login options
  • ensure only one step can be added/configured
  • prevent login requires on the single step
  • allow registration
  • allow logic (only the registration backends action for now)
  • allow confirmation templates
  • disable prefill (backend from submission and frontend in the variables tab, it's also disabled in the form builder)
  • disable/hide progress indicator display
  • disable submit options (always submit without overview)
  • disable new form renderer (default to true)
  • disable advanced configuration

Checklist

Check off the items that are completed or not relevant.

  • Impact on features

    • Checked copying a form
    • Checked import/export of a form
    • Config checks in the configuration overview admin page
    • Checked new model fields are usable in the admin
    • Problem detection in the admin email digest is handled
  • Dockerfile/scripts

    • Updated the Dockerfile with the necessary scripts from the ./bin folder
  • Commit hygiene

    • Commit messages refer to the relevant Github issue
    • Commit messages explain the "why" of change, not the how
  • Documentation

    • Added documentation which describes the changes

@vaszig vaszig marked this pull request as draft March 25, 2026 16:13
@vaszig vaszig changed the base branch from main to feature/6098-introduce-a-single-page-form March 25, 2026 16:15
@vaszig
Copy link
Copy Markdown
Contributor Author

vaszig commented Mar 25, 2026

Do NOT merge until 3.5 is released.
Requires #6102

@vaszig vaszig force-pushed the feature/6098-introduce-a-single-page-form branch 2 times, most recently from 25c6aa1 to 8dd7649 Compare March 27, 2026 07:18
@vaszig vaszig force-pushed the feature/6106-adapt-form-designer-according-to-the-new-form-type-field branch from 70f63cd to 3b35ebc Compare March 27, 2026 07:22
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 27, 2026

Codecov Report

❌ Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 97.07%. Comparing base (3b1326c) to head (038ed83).

Files with missing lines Patch % Lines
src/openforms/submissions/api/viewsets.py 66.66% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@                              Coverage Diff                              @@
##           feature/6098-introduce-a-single-page-form    #6117      +/-   ##
=============================================================================
- Coverage                                      97.08%   97.07%   -0.01%     
=============================================================================
  Files                                            884      884              
  Lines                                          33393    33394       +1     
  Branches                                        2997     2998       +1     
=============================================================================
  Hits                                           32418    32418              
  Misses                                           658      658              
- Partials                                         317      318       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@vaszig vaszig force-pushed the feature/6106-adapt-form-designer-according-to-the-new-form-type-field branch from cc58adc to 4537640 Compare March 30, 2026 07:38
@vaszig vaszig force-pushed the feature/6098-introduce-a-single-page-form branch 4 times, most recently from d1af4c9 to e6f635d Compare April 1, 2026 06:46
@vaszig vaszig force-pushed the feature/6106-adapt-form-designer-according-to-the-new-form-type-field branch 2 times, most recently from 6e150dd to 016b228 Compare April 1, 2026 07:21
@vaszig vaszig force-pushed the feature/6098-introduce-a-single-page-form branch 2 times, most recently from 8847858 to 4b1681f Compare April 3, 2026 10:42
@vaszig vaszig force-pushed the feature/6106-adapt-form-designer-according-to-the-new-form-type-field branch from 7665496 to c10a232 Compare April 3, 2026 10:44
vaszig added 8 commits April 7, 2026 11:57
- New form type field (regular, appointment and single page)
- Migrations for the new field and the removed one (is_appointment)
- Data migration for the existing forms (update the form type)
- added regular form to metrics
- fixed form serializer in v3 and added tests
- fixed broken css in admin radio fields
- made help texts a bit better
@vaszig vaszig force-pushed the feature/6098-introduce-a-single-page-form branch from 4b1681f to 49e8a25 Compare April 7, 2026 10:10
@vaszig vaszig force-pushed the feature/6106-adapt-form-designer-according-to-the-new-form-type-field branch from c10a232 to c6e8543 Compare April 8, 2026 13:14
@vaszig vaszig force-pushed the feature/6106-adapt-form-designer-according-to-the-new-form-type-field branch from c6e8543 to 038ed83 Compare April 8, 2026 17:00
@vaszig vaszig force-pushed the feature/6098-introduce-a-single-page-form branch 2 times, most recently from 399bb70 to 92736f6 Compare April 20, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adapt the form designer UI based on the new form type field

1 participant