Issue Bug Resolved

#107080Form prototype not selectable with blank form

Thorben Nissen 07/11/25, 14:19 updated 09/28/26, 12:35

Description

I’ve defined a prototype “modern”, which has its own set off template and removes some unused form field types. I registered the prototype according to the documentation.

However, when click on “Create new form” I get to see to new-templates from the standard prototype. When selecting “Blank form” I can’t select my “modern” prototype, but “standard” is automatically chosen. I need to choose the “Predefined form” template to get to choose both prototype and new-template in the next step.

This behaviour is quite illogical. As the available new-templates depend on the prototype, it would only be logical to have to choose the prototype first.

Reviews 4

History 37

  1. Josua Vogel commented <span data-processor="relativetime" data-value="2025-07-28T17:06:21+00:00" > 07/28/25, 17:06 </span>

    I have gained a rough overview. The current behavior is not optimal, as described above.

    Currently, no prototype select is rendered in form-manager/view-model.ts, if you select “empty form”. Creating an empty form always refers to the default prototype and the BlankForm.yaml template.

    I don’t think this template is necessary.

    I would therefore remove this fixed dependency.

    The question remains whether to structure the New Form Wizard differently. Should the first step be to select the prototype directly and then use a dropdown menu in the second step to decide whether to use an empty form (default) or one of the templates?

  2. Josua Vogel commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-28T12:35:12+00:00" > 09/28/26, 12:35 </span>

    Applied in changeset commit:ccab5942a3cfb7293104959b486abcc17a2641ff.