Single Select Responses
Single select responses allow reviewers to choose exactly one option from a predefined list, making them perfect for clear decision workflows, approval processes, and structured categorization where mutual exclusivity is important.When to Use Single Select
Single select responses are ideal for:Approval Workflows
Simple approve/reject decisions, or approval with conditions like “Approve”, “Reject”, “Needs Changes”
Content Classification
Categorizing content into mutually exclusive categories like content type, priority level, or department
Quality Assessment
Rating content quality with discrete levels like “Excellent”, “Good”, “Fair”, “Poor”
Status Assignment
Setting request status, priority levels, or routing decisions where only one choice makes sense
Configuration Options
Single select responses require an options array and support visual customization:Required Parameters
Array of SelectOption objects (1-20 options maximum)
Optional Parameters
Whether a selection is mandatory for completion
Implementation Examples
Basic Approval Workflow
Simple approve/reject decision with visual indicators:Content Classification
Categorizing content into specific types:Quality Assessment
Rating content quality with discrete levels:Response Format
When a reviewer selects an option, you’ll receive both the internal value and the display label:Use Case Examples
1. Content Moderation
- Configuration
- Processing Logic
2. Support Ticket Routing
- Configuration
- Processing Logic
3. Document Approval Workflow
- Configuration
- Processing Logic
Validation and Error Handling
Automatic Validation
The mobile app automatically validates single select responses:- Option validation: Ensures selected value exists in the options array
- Required validation: Prevents submission when required=true and no selection made
- Single selection: Enforces exactly one choice (radio button behavior)
Processing Validation
Your application should validate received responses:Best Practices
Option Design
Clear and Distinct Labels
Clear and Distinct Labels
- Use descriptive labels that clearly communicate the choice
- Avoid ambiguous or similar-sounding options
- Include emoji or icons for visual differentiation
- Keep labels concise but informative (under 50 characters ideal)
Logical Ordering
Logical Ordering
- Put most common/expected choices first
- Order by severity (mild to severe) or progression (low to high)
- Group related options together
- Consider alphabetical ordering for long lists
Helpful Descriptions
Helpful Descriptions
- Provide context for options that might be unclear
- Explain consequences or next steps for each choice
- Include examples when helpful
- Keep descriptions brief but informative
Strategic Color Usage
Strategic Color Usage
- Use green (#22c55e) for positive/approval actions
- Use red (#ef4444) for negative/rejection actions
- Use yellow/orange (#f59e0b) for warnings or caution
- Use blue (#3b82f6) for neutral/informational options
- Use purple (#8b5cf6) for escalation or special handling
Processing Best Practices
Switch Statement Logic
Switch Statement Logic
Audit Trail
Audit Trail
Decision Analytics
Decision Analytics