Issue Bug Closed

#102055Form runtime next/previous page ignores variants

Mathias Brodala 09/28/23, 08:06 updated 03/31/26, 09:00

Description

Given a form with conditional pages variants are not respected when the navigation is built. Example:

type: Form
prototypeName: standard
identifier: multi-step-form
label: Muli step form
renderables:
  -
    type: Page
    identifier: page-1
    label: First step
    renderables:
      -
        type: Checkbox
        identifier: checkbox-1
        label: Check this and the 2nd step will be skipped
  -
    type: Page
    identifier: page-2
    label: Second step
    renderingOptions:
      enabled: false
    variants:
      -
        identifier: variant-2
        condition: 'traverse(formValues, "checkbox-1") == 0'
        renderingOptions:
          enabled: true
  -
    type: Page
    identifier: page-3
    label: Third step
    renderingOptions:
      enabled: false
    variants:
      -
        identifier: variant-2
        condition: 'traverse(formValues, "checkbox-1") == 1'
        renderingOptions:
          enabled: true

Enabling the checkbox on the 1st page and going to the next page will show the 3rd page and a “Submit” button.

Not enabling the checkbox on the 1st page and going to the next page will show the 2nd page and a “Next Page” button. However, there is no next page here. In this case the button should also say “Submit”.

The example above generally disables all subsequent pages and conditionally enables them which is a logical approach IMO. Especially because it allows you to have conditions which match their page 1:1. The reverse logic as suggested by the docs also doesn’t work however:

type: Form
prototypeName: standard
identifier: multi-step-form
label: Muli step form
renderables:
  -
    type: Page
    identifier: page-1
    label: First step
    renderables:
      -
        type: Checkbox
        identifier: checkbox-1
        label: Check this and the 2nd step will be skipped
  -
    type: Page
    identifier: page-2
    label: Second step
    variants:
      -
        identifier: variant-2
        condition: 'traverse(formValues, "checkbox-1") == 1'
        renderingOptions:
          enabled: false
  -
    type: Page
    identifier: page-3
    label: Third step
    variants:
      -
        identifier: variant-2
        condition: 'traverse(formValues, "checkbox-1") == 0'
        renderingOptions:
          enabled: false

Reviews 2

History 818

  1. Mathias Brodala commented <span data-processor="relativetime" data-value="2023-11-01T10:30:01+00:00" > 11/01/23, 10:30 </span>

    Just noticed that the given example is bad since you always end up at the 3rd page with “Submit” then. Here is a better example:

    type: Form
    prototypeName: standard
    identifier: multi-step-form
    label: Muli step form
    renderables:
      -
        type: Page
        identifier: page-1
        label: First step
        renderables:
          -
            type: Checkbox
            identifier: checkbox-1
            label: Check this and the 3rd step will be skipped
      -
        type: Page
        identifier: page-2
        label: Second step
        variants:
          -
            identifier: variant-2
            condition: 'traverse(formValues, "checkbox-1") == 0'
            renderingOptions:
              enabled: false
      -
        type: Page
        identifier: page-3
        label: Third step
        variants:
          -
            identifier: variant-2
            condition: 'traverse(formValues, "checkbox-1") == 1'
            renderingOptions:
              enabled: false

    Without the fix, having the checkbox enabled will lead to “Next page” on the 2nd page as last step.

    With the fix it will say “Submit” on the 2nd page instead since there is no 3rd page.

  2. Mathias Brodala commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-03-12T07:00:09+00:00" > 03/12/26, 07:00 </span>

    Applied in changeset commit:d88a11d681bd83b5eea511c7890e4050d19770af.

  3. Gerrit Code Review pushed patch set 2 for 13.4 to change 93154 status Resolved Under Review <span data-processor="relativetime" data-value="2026-03-12T07:15:34+00:00" > 03/12/26, 07:15 </span>

  4. Mathias Brodala commented and changed status Under Review Resolved <span data-processor="relativetime" data-value="2026-03-12T08:00:08+00:00" > 03/12/26, 08:00 </span>

    Applied in changeset commit:698a713e219d5db40d1d362a7d239512c0cbf9aa.