multiple-choice-checklist mode = 'row'

General Q&A
1

When using this mode, do you have the ability to span this row across the whole view?

1 Like
2

Unfortunately not, but that may be something that we can expose as a future feature enhancement.

That said, we have seen several use cases where someone may want to split the contents of their multiple-choice across 2 or more columns and that you can do. Basically you use multiple multiple-choice-checklist components, each one bound to the same variable, but in each case you explicitly list which options to render to the user. So if you want your multi choices to be split across 3 different columns, then you would implement 3 different components each rendering a subset of all the potential options

Something like this…

<columns>
    <column>
        <multiple-choice-checklist bind="selected_object.transition_reasons" label="Reason(s)" required="true" mode="column">
            <option key="0">Well Control - Active or Potential</option>
            <option key="1">Mud Losses to open hole - Active ongoing or potential</option>
            <option key="2">Open Hole Exposed - Extented time exposure</option>
        </multiple-choice-checklist>
    </column>
    <column>
        <multiple-choice-checklist bind="selected_object.transition_reasons" label="Reason(s)" required="true" mode="column">
            <option key="3">Open Perforations Exposed - Extended time exposure</option>
            <option key="4">Hydrocarbon Under pressure production platforms - Extended time exposure</option>
            <option key="5">Equipment required for continuous safe offshore operations</option>
        </multiple-choice-checklist>
    </column>
    <column>
        <multiple-choice-checklist bind="selected_object.transition_reasons" label="Reason(s)" required="true" mode="column">
            <option key="6">Equipment to be returned to enable continuous safe offshore operations</option>
            <option key="99">Other</option>
        </multiple-choice-checklist>
    </column>
</columns>

where the Data Model looked like this …

<field name="transition_reasons" label="Transition Reasons" type="multiple-choice">
    <option key="0">Well Control - Active or Potential</option>
    <option key="1">Mud Losses to open hole - Active ongoing or potential</option>
    <option key="2">Open Hole Exposed - Extented time exposure</option>
    <option key="3">Open Perforations Exposed - Extended time exposure</option>
    <option key="4">Hydrocarbon Under pressure production platforms - Extended time exposure</option>
    <option key="5">Equipment required for continuous safe offshore operations</option>
    <option key="6">Equipment to be returned to enable continuous safe offshore operations</option>
    <option key="99">Other</option>
</field>