Question Type: Card List

A Card List question makes it easy for field technicians to find and select an option based on an image. For example, a technician can select a piece of equipment based on how it looks rather than on a detailed serial number. This topic describes how to add a Card List question to your form.

Available on the Advanced and Enterprise tiers:

Essentials
Advanced
Enterprise

Supported on app versions:

iOS 14.4 or later
Android 14.3 or later
Windows 14.3 or later

Contents

What is a Card List question?

A Card List question contains between two and ten response options called Cards. Each Card contains a Resource Image resource, a brief description, and an associated server value. A technician can work more efficiently and accurately because they can compare the images to objects in front of them. When the technician submits the form, the system records the associated value as the answer to the Card List question.

Tip:You can configure Conditional Logic rules with Card List questions to create a more dynamic workflow.

Example of a Card List question

A technician might service multiple different smoke detector models during their shift. These smoke detectors have long serial numbers that look very similar to each other at a glance. Normally, the technician compares each unit’s serial number to the list on their form, which can be a slow and error-prone process.

A Card List enables the technician to glance at an image instead of a serial number to find the correct unit. If two items look similar, then the technician can compare serial numbers from the Card description to select the correct unit.

When the technician finds their answer to the Card List question, their selection is indicated by a blue outline and check mark. The technician can easily select another Card to change their answer before they submit the form.

A sample Card List question in the iOS app with six options. The selected option has a blue outline and a checkmark in the top right corner of the Card.

Note:The Card List tile sizes adjust to fit the largest Resource Image in the question. This makes smaller images harder to see. To make all Card images clearly visible, upload Resource Images with the same dimensions for all images.

When to use a Card List question

A Card List behaves like a Button Group or Radio Button question combined with a Resource Image question. As with these options-based questions, a user can select only one response from the presented options. A Card List, however, provides a visual aid as the focus for each question option.

The following table can help you decide if you need a Card List, Button Group, Radio Button, or Resource Image question:

Question Type Number of Options/Attachments Visual Aid Type
Card List
  • Minimum: Two

  • Maximum: Ten

Card List options include both an image and text to help users quickly identify their selection.

Tip:The server receives only the value of the submitted answer. This means that the linked Resource Images don’t contribute to the overall submission size limit.

Button Group
  • Minimum: Two

  • Maximum: Five

You can apply a color to a Button Group response, but it only shows after the user selects it.
Radio Button
  • Minimum: One

  • Maximum: No limit for manual lists

There is no visual aid—Radio Button answers contain only text.
Resource Image
  • Minimum: One

  • Maximum: Ten

Resource Image questions serve as read-only reference material for the user.
Note:Forms have a limit on the number of Resource Image resources they can contain. The images in both Card List and Resource Image questions contribute to this limit. The Resource Image limitations are:
  • 10 images per question

  • 100 images per page

  • 100 images per form

Create or edit a Card List question

Prerequisites

Steps to create or edit a Card List question

  1. Select the form you want to work on:

    Forms & Integrations > List Forms > FormName

  2. Select Edit Form.

    Result: The system opens the form in edit mode.

  3. Do you want to create a new Card List question?

    • If yes, add a new question.

      You have two options when adding a new question:

      • Hover between two questions, and select the plus sign [+].

        The plus icon. Selecting this option allows you to insert a question between two existing questions.

      • Scroll to the bottom of a section and select ADD A QUESTION.

        The Add a Question Button. This button appears the bottom of every section on the Form Builder.

      To move a question, drag it to one of the separators between questions or to an empty section. You can also move a question to another page by dragging it to the Form Index.

    • If no, select the existing Card List question you want to edit, and then go to step 5.

  4. On the Question Type page, select the Options-Based tab, and then select Card List from the list.

    On the Question Type page, you can find Card List easily on the Options-Based tab or by typing in the search bar. The Card List icon displays a list of two media squares with text lines.

    Tip: To filter the list, start typing the name of the question type and then select an option.

    Result: The system displays the configuration page for the Card List question.

  5. Enter the Question Text and Unique IDClosed A Unique ID refers to the specific identifier of a question, form page, form section, or Data Destination. Unique IDs are used as reference points when pulling data for conditional logic, Analytics projects, Data Destinations, and Documents., set the Data Type, and apply Restrictions.

    The following Data Types are available for Card List:

    • Free Text

    • Email Address

    • URL

    • Phone Number

    • Integer

    • Decimal

    • Currency

  6. On the Options tab, configure the options fields:

    • Value submitted to server: Enter the response that the server receives and displays after a user submits the form. This field has a maximum of forty characters.

      Tip:The server receives only the value of the submitted answer. This means that the linked Resource Images don’t contribute to the overall submission size limit.

    • Text displayed on device (Optional): Enter a short description, such as a product name or code, for the user to see on the Card. This field has a maximum of forty characters. If you want to use the same text as the server value, leave this field blank.

      Tip:For any Documents that you link to the form, you can choose whether to show the display or server value.

      You can also use the DREL [display] property to reference the display value instead of the server value:

      %a[QuestionUniqueID][display]

      Info:If your team has the Multi-Language Forms add-on, you can translate the display value (but not the server value). When a field user selects a language, they see the translated display value.

      To show the translated display value in a Repeatable SectionClosed A Repeatable Section is a subform that contains a set of related questions. The data captured is “repeating”, because the field user can complete the same subform more than once, which creates multiple entries. Summary Table, edit the column settings and set the Answer value to display to Display Value.

    • Image displayed on device: Select an image for the user to see on the Card. Images do not display on the form submission details page or in documents.

      Note:The image file must be in your FormSpace Resource Images before you can select it.

  7. The Card List "Options" tab enables you to add up to ten answer options. The two mandatory fields for an option are the Server Value and Resource Image.

  8. Repeat step 6 for up to ten options.

  9. Configure the question’s Properties (optional), including Answer Exceptions, Additional Comments, and Help Options.

  10. Select Save.

    Result: The system saves your changes to the new or edited question.

    The Card List display in the Form Builder shows a Card tile for each option. For smaller displays, additional tiles are included in a "+ (number) more items" message.

  11. Tip:Remember to Save and Deploy the form when you’re ready to make it available to your field users.