Skip to main content
Purpose: Comprehensive comparison of all data management features to help choose the right tool for each scenario. Last Updated: 2026-02-01
See Also: TERMINOLOGY.md for full glossary including wizards and templates.

Master Comparison Matrix


Feature Relationship Diagram


Master Decision Tree


Detailed Feature Comparisons

Picklists vs Lookups vs Form Options

Custom Fields vs Custom Objects

Forms vs Custom Objects

Field Configuration vs Form Builder


Common Scenarios Quick Reference

”I need a dropdown for employment status”

Picklist (PF-15) - Reusable across forms/entities

”I need a dropdown of departments”

Lookup (FW-15) - Dynamic from hr_departments table

”I need Yes/No in this form only”

Form Options (FW-01) - Form-specific static options

”I need to add badge number to employees”

Custom Fields (PF-16) - Extend hr_employees

”I need to track clinical licenses”

Custom Objects (PF-24) - New entity type

”I need to hide salary from non-admins”

Field Configuration (PF-17) - Role-based visibility

”I need to create an intake form”

Form Builder (FW-01) - Data capture with workflow

”I need to see all employees and export to CSV”

Raw Data Editor (PF-25) - Browse and export

”I need to find what objects exist”

Object Browser (PF-23) - Discover and categorize

Wizard Comparison

Form Wizard vs Module Wizard

When to Use Each Wizard

Use Form Wizard (FW-31) when:
  • You have a multi-page form that needs guided progression
  • Data should go to form submissions table
  • All steps are form fields (no custom components)
  • Example: Resident intake, satisfaction survey
Use Module Wizard (PF-41) when:
  • You’re building a business process (onboarding, payroll)
  • Data should go to module-specific tables
  • Steps need custom React components
  • Organizations need to customize the wizard flow
  • Example: Employee onboarding, resident admission

Template Comparison

Template Types

When to Use Each Template Type


Anti-Patterns to Avoid

❌ Using Picklists for Database Table Data

Problem: Creating picklist for departments when hr_departments exists
Solution: Use Lookups (FW-15)

❌ Using Custom Objects for Entity Extension

Problem: Creating custom object to add badge number to employees
Solution: Use Custom Fields (PF-16)

❌ Using Custom Objects for Forms

Problem: Creating custom object for intake form
Solution: Use Form Builder (FW-01)

❌ Using Custom Fields for New Entities

Problem: Adding “license_number” custom field when you need license tracking
Solution: Use Custom Objects (PF-24)

❌ Using Form Builder for Entity Extension

Problem: Creating form to capture employee badge number
Solution: Use Custom Fields (PF-16) + entity form

❌ Using Field Configuration to Add Fields

Problem: Trying to add new field via field configuration
Solution: Use Custom Fields (PF-16) first, then configure

❌ Using Form Wizard for Business Processes

Problem: Using FW-31 form wizard for employee onboarding
Solution: Use Module Wizard (PF-41) - data needs to go to HR tables

❌ Using Module Wizard for Data Capture

Problem: Using PF-41 wizard for a survey or intake form
Solution: Use Form Wizard (FW-31) - simpler, data goes to form submissions

❌ Using Workflow Template for Documents

Problem: Creating workflow template to generate PDF letters
Solution: Use Document Template (PF-64) for printable documents

❌ Using Document Template for Automation

Problem: Trying to automate approval flow with document template
Solution: Use Workflow Template (FW-28) for automation patterns

Integration Patterns

Pattern 1: Picklist → Custom Field → Field Config

Pattern 2: Custom Object → Form Reference

Pattern 3: Custom Fields → Raw Data Export


Use Case Guides

Terminology & Analysis

Specifications


Last Updated: 2026-02-01