Description:

A single checkbox is useful when a form needs to capture a simple yes/no, selected/not selected, acknowledged/not acknowledged, or similar binary user choice.

This control can be used for:

• User acknowledgements
• Confirmation options
• Yes/no selections
• Agreement or acceptance indicators
• Optional selections
• Form completion confirmations
• Workflow decision inputs
• Terms and policy acknowledgments
• Capturing a single Boolean-style choice

Design: 

The Single Checkbox is typically placed on a FlowWright form when the user needs to make a single selectable choice.

For example, a form may contain:

☐ I confirm that the information provided is accurate.

A common form-to-workflow pattern is:

Form → User selects checkbox → Workflow processes form submission

The actual mechanism for exposing the checkbox value to workflow processing is not specified in the supplied XML and should be configured per the FlowWright form implementation.

Typical Workflow Suggestions:

User Confirmation

Use a Single Checkbox when a workflow requires the user to explicitly confirm an action.

Example:

☐ I confirm that I have reviewed this request.

Terms and Conditions Acceptance

A checkbox can provide a simple acceptance mechanism for terms or policies.

Example:

☐ I agree to the applicable terms and conditions.

Information Accuracy Confirmation

Use the control when users need to confirm that information entered on a form is accurate.

Example:

☐ I confirm that the information provided is correct.

A form can include a checkbox to capture explicit confirmation for an approval activity.

Example:

☐ I approve the requested change.

Completion Checklist

A Single Checkbox can represent completion of an individual requirement.

Example:

☐ Required documents have been reviewed.

Customer Request Confirmation

Use a checkbox to allow a customer or requester to confirm a submitted request.

Example:

☐ I confirm that I want to submit this request.

Compliance Acknowledgement

Use the control to capture an acknowledgment that a user has reviewed a required instruction or policy.

Example:

☐ I acknowledge that I have read and understood the policy.

A checkbox can provide a simple user-selected value that participates in subsequent workflow processing.

For example:

Form → Checkbox Selection → Workflow Processing → Decision/Route

The specific way the checkbox value is consumed by the workflow is not defined in the supplied widget XML.

Optional User Preference

Use a checkbox for an optional preference.

For example:

☐ Send me a notification when the request is completed.

Confirmation Before Submission

A Single Checkbox can be placed near the end of a form to require or encourage an explicit confirmation before submission.

For example:

☐ I have reviewed all information above before submitting this form.

Example: 

Let’s build and execute the “SingleCheckboxDef” example.  

• Create a Form Definition called “SingleCheckboxDef.”
• Drag a “BootstrapGrid, Label, TextArea, Datepicker, Single Checkbox, and Submit” control onto the canvas and position them as shown below.

• Double-click the “TextArea” widget to configure its “Settings” properties. Enter the default value text. Select “Enable Voice Input” to accept voice input at runtime. Select “Required” to require input. Select “Hide” to hide the control at runtime. Select “Read-Only” to view the content without making changes. Use the “Maximum Allowed Characters” or “Maximum Allowed Words” buttons to limit user input. Click “Lock Widget” to prevent changes. Click “Save.” 

• Double-click the “Date Picker” widget to configure its “Settings” properties. Select “Use Default Date” to consider the current system date. Select “Use Time” to consider the current system time. Select “Required” to require input. Select “Hide” to hide the control at runtime. Select “Read-Only” to view the content without making changes. Click “Lock Widget” to prevent changes. Click “Save.” 

• Double-click the “Single Checkbox” widget to configure the “Settings” properties. Enter the “checkbox” text. Enter the default value. Note: The default value must be either the Checked value or the Unchecked value. Select “Required” to require input. Select “Hide” to hide the control at runtime. Select “Read-Only” to view the content without making changes. Click “Lock Widget” to prevent changes. Click “Save.” 

• Navigate to the “Conditions” tab. Use the plus sign to add multiple display conditions. Enter the control field value to show or hide the form field. Select the form field to show or hide. Note: You can map multiple form fields to the same control field value. Click “Lock Widget” to prevent changes. Click “Save.” 

• Navigate to the “Styling” tab. Select the boxes to apply bold, italics, and underlining to the display value. Customize the foreground and background colors using the color palette. Select the font size from the drop-down list. Enter the CSS syntax to change the styles. Select the drop-down to apply CSS style classes (if available). Click “Lock Widget” to prevent changes. Click “Save.” 

• Navigate to the “Other” tab. Enter the tooltip text.  Click “Lock Widget” to prevent changes. Click “Save.” 

• Navigate to the “Globalize” tab. Select the culture from the drop-down list, then click “Translate” to globalize the display. A confirmation message appears in the top-right corner. Click “Lock Widget” to prevent changes, then click “Save.” 

• Save the Form Definition. Select Actions > Create Form Instance from the menu. Generate a new form instance, then check the box to edit it. 

• The Form is displayed as shown in the image below. 

• Click the “single checkbox,” and the “date” form field is shown as configured. Click the “Submit” button to complete the Form. 

Tips:

• Use clear, concise wording next to the checkbox.
• Phrase the checkbox text so that the meaning of selecting it is unambiguous.
• Use affirmative statements where possible, such as “I confirm…” or “I agree…”.
• Avoid ambiguous labels such as “Confirm” without explaining what is being confirmed.
• Use separate checkbox controls when users need to make several independent selections.
• Consider whether a checkbox is appropriate when the user must choose exactly one option from several alternatives; a radio-button-style control may be more appropriate for that requirement.
• Test the form with both the checkbox selected and cleared.
• Verify how the checkbox value is made available to the associated workflow.
• If selection is mandatory, verify the form's validation configuration rather than assuming that the widget definition itself provides validation.
• Keep acknowledgment text close to the checkbox so the relationship is obvious.
• Use meaningful field names when the form designer provides a field-name or data-binding option.
• Test the submitted value in the actual workflow before deploying the form.
• Do not assume that the XML-defined widget automatically creates workflow routing or validation behavior.
• Do not assume event behavior unless it is explicitly configured or documented by the FlowWright form implementation.

Notes:

The Single Checkbox is defined as a form widget, not a Process step. It belongs to the Standard Controls category and is implemented by FlowWright.Forms.SingleCheckbox in FlowWright.Forms.dll.

The internal widget name is:

singlecheckbox

Single Checkbox

Definition Sample:

A sample definition can be created by adding the Single Checkbox widget to a FlowWright Form Definition.

When importing or reusing a form definition, verify the form-specific configuration, including:

• Checkbox placement.
• Associated field/data binding, where applicable.
• Display text.
• Default state, where supported.
• Validation requirements, where applicable.
• Workflow integration.
• Environment-specific form configuration.

After verifying the configuration, save the Form Definition before using it in a workflow.

Click here to download the sample file.