This article explains how the Yes/No field works in the Sintel Apps Designer and how to configure its available options.

The Yes/No field is used when a user must make a simple binary decision. When added to a form, it creates a corresponding Yes/No column in the underlying SharePoint list.

What Is a Yes/No Field?

A Yes/No field allows users to select one of two values: Yes or No

It is commonly used for:

• Confirmation questions
• Compliance checks
• Eligibility validation
• Risk indicators
• Approval prerequisites

Because it only stores two possible values, it is ideal for logic-driven forms.

Properties

When selecting the Yes/No field in the Layout tab, the following properties are available:

Title – The label displayed on the form.

Required – If enabled, the user must make a selection before saving or submitting.

Display As – The Yes/No field can be displayed in two ways: Text or Icon. Choose the style that best matches your form design and audience.

Default Value –  Controls what value is pre-selected when the form loads.

Available options:

• From SharePoint – Uses the default configured at list level

• None – No default selection

• Custom – Manually set Yes or No

• Query Parameter – Pre-populate from a URL parameter, i.e. ?form_ParameterName=123

  Note that a ‘form_’ prefix is required in URL.

Behaviour Settings – The State setting controls how the field behaves.

Available options:

• Inherit from section – Follows the section’s behaviour

• Mandatory – Always required

• Optional – Not required

• Read-only – Cannot be edited by users

State can also be modified dynamically using Logic rules.

Label Settings – You can configure: Label text / Label position / Tooltip

Tooltips are useful when users need clarification about what “Yes” or “No” means in context.

Using Yes/No in Logic

Yes/No fields are frequently used to:

• Show or hide sections

• Trigger workflow approvals

• Make additional fields mandatory

• Display validation messages

Example:

If Requires Legal Review = Yes, show the “Legal Details” section.

Because the field has only two values, it is highly reliable for logic conditions.

Best Practices

• Clearly word the question to avoid ambiguity.

• Use Text display for compliance-driven forms. Use Icon display for simpler, modern layouts.

• Combine with Logic to enforce additional requirements.

• Test logic triggered by Yes/No conditions.

➡️ Next article: Hyperlink and Picture Fields – Configuration and Use Cases