How to Properly Map Radio Button Fields to Text Fields: Setting Option Values

Introduction

When mapping radio button fields to text inputs, the "option value" determines what data is transferred. This article explains how to set correct option values to avoid user confusion using a "Preferred Contact Method" example.

Problem

Suppose you have a Workflow consisting of a Web Form with a multiple choice field asking "What is your preferred contact method?" with radio button options:

• Email
• Phone
• Text

Then, in the following step, you want to display the customer's choice in a Fill and Sign Document as a Text Field. 

However, instead of "Email," "Phone," or "Text," the text field shows "preferred_method_phone", "preferred_method_email", or "preferred_method_text":

Explanation

• Option Labels vs. Values: The options have a user-friendly label (what the user sees) and an internal option value (what the system stores).
• Data Transfer: When mapping radio button data, the system transfers the option value, not the label.
• Since the option values in this scenario are not user friendly (i.e. "contact_method_email,"), it can confuse end-users if displayed in a text field.

Solution

• Set User-Friendly Option Values: In the radio button field's settings, ensure the option values are set to the same values as the labels (e.g., "Email," "Phone," "Text").
• Go to the "Preferred Contact Method" field settings and change the option values to match the labels. Using the example:
  • For the "Email" option, set the option value to "Email."
  • For the "Phone" option, set the option value to "Phone."
  • For the "Text" option, set the option value to "Text."
  • 
• Publish and Run Workflow: Test the data mapping to checkthat the correct values are being transferred.