JSON Form Fields in Action Steps

1. Overview

JSON Form Fields provide a quick and efficient way to create simple modal popup forms without designing a full screen. By defining form inputs using JSON configuration within action steps, you can rapidly build create and edit dialogs for your end users. This approach is ideal for straightforward data entry scenarios requiring only basic inputs in a single-column layout.

JSON Form Fields are typically used in action button configurations and table column menu features, allowing you to define popup forms directly within the action definition rather than creating separate screen designs.

When to Use JSON Form Fields: This approach is best suited for simple, single-record operations with a few basic inputs. For complex workflows, nested mutations, multi-step processes, or advanced layouts, use Screen Dialogues or dedicated form screens instead.

2. Prerequisites

• Access Type: App Admin or Developer
• Permissions: Screen design and deployment permissions
• Knowledge: Basic understanding of JSON syntax and Fuuz data models
• Resources: A screen with action buttons or table column menus configured

3. Choosing the Right Approach

Fuuz offers multiple ways to present forms to users. Understanding when to use each approach ensures optimal user experience and maintainability.

Comparison: JSON Form Fields vs. Screen Dialogues

Use JSON Form Fields When:

• You need only a few basic input fields (typically 1-6 fields)
• The operation is a simple single-record create, edit, or delete
• No complex validation logic or conditional field visibility is required
• You want rapid development without creating separate screen assets
• The form doesn't require charts, tables, or rich visualizations

Use Screen Dialogues When:

• You need multi-column layouts or complex formatting
• The workflow involves web flows or multi-step processes
• You require supervisor signoffs or approval chains
• The form includes nested mutations or mass record operations
• You need conditional field visibility or complex validation
• The modal requires charts, tables, or other visualizations
• The form will be reused across multiple screens or actions

Best Practice: When using web flows for complex workflows and modals (such as supervisor signoffs), always use Screen Dialogues or separate screen designs. This provides the flexibility needed for proper workflow orchestration and error handling.

4. Procedure Steps

Step 1: Navigate to the Screen Designer

1. Open the Screen Designer application
2. Open or create the screen where you want to add the popup form

Step 2: Add an Action Trigger

Select or add an element that will trigger the popup form:

1. Add an Action Button to your screen, or
2. Configure a Column Menu action in a table, or
3. Use an existing action element

Step 3: Configure the Form Action

1. Select the action element and open its properties panel
2. Add a new action step
3. Select the "Form" action type from the dropdown
4. Provide a Name for your form—this displays as the modal title to end users (e.g., "Create New Item", "Edit Record", "Add Comment")

Step 4: Define Form Fields Using JSON

1. Locate the Form Fields section in the action configuration
2. Click the four-way arrow icon above the Form Fields section to open the full-screen editor
3. Define your form fields using the JSON array structure

Basic Text Input Example:

[
  {
    "name": "name",
    "description": "Enter the item name",
    "label": "Name",
    "type": "text",
    "dataPath": "name",
    "disabled": false,
    "validation": {
      "required": true
    },
    "defaultValue": "",
    "query": {
      "fields": ["name"]
    }
  }
]

Step 5: Add Multiple Fields

Add additional field objects to the array, separated by commas:

[
  {
    "name": "name",
    "label": "Name",
    "type": "text",
    "dataPath": "name",
    "validation": { "required": true }
  },
  {
    "name": "description",
    "label": "Description",
    "type": "multiline",
    "dataPath": "description",
    "validation": { "required": false }
  },
  {
    "name": "quantity",
    "label": "Quantity",
    "type": "number",
    "dataPath": "quantity",
    "defaultValue": 1,
    "validation": { "required": true }
  },
  {
    "name": "dueDate",
    "label": "Due Date",
    "type": "date",
    "dataPath": "dueDate",
    "validation": { "required": false }
  }
]

Step 6: Save and Test

1. Close the full-screen editor
2. Save your screen design
3. Deploy to test environment
4. Test the action to verify the popup form displays correctly

5. Configuration Reference

Field Properties

Available Field Types

Color Input Example

The color input type provides a color wheel picker for users to select hex color values. This is useful for allowing end users to configure display colors for statuses, categories, or other UI elements.

{
  "name": "color",
  "description": "Color to be used in UI for display purposes",
  "label": "Color",
  "type": "color",
  "disabled": false,
  "dataPath": "color",
  "validation": {
    "required": false
  },
  "defaultValue": "#cccccc",
  "query": {
    "fields": ["color"]
  }
}

Tip: Color inputs store hex color codes (e.g., #FF5733). You can use these values directly in conditional formatting for table cells, status indicators, or any UI element that supports color styling. See the Table Column Conditional Formatting article for usage examples. Note: Additional field type examples and configurations will be provided in future article revisions. For complex input requirements, consider using Screen Dialogues with full canvas-based screen design.

Using Transforms in JSON Forms

You can incorporate dynamic behavior into JSON form fields using stringified transforms:

• Pre-transforms in the action: Apply transforms before the form displays to calculate default values or modify field configurations
• Embedded transforms in form elements: Include transforms directly within field properties for dynamic behavior based on context or access

6. Use Case Examples

Example 1: Quick Create Form (Use JSON Form Fields)

Scenario: Add a "Create New Task" button to a task list table that opens a simple form with name, description, and due date.

Why JSON Form: Only 3 fields, single record creation, no complex workflow, no conditional logic.

[
  {
    "name": "name",
    "label": "Task Name",
    "type": "text",
    "dataPath": "name",
    "validation": { "required": true }
  },
  {
    "name": "description",
    "label": "Description",
    "type": "multiline",
    "dataPath": "description"
  },
  {
    "name": "dueDate",
    "label": "Due Date",
    "type": "date",
    "dataPath": "dueDate"
  }
]

Example 2: Quick Edit from Table Row (Use JSON Form Fields)

Scenario: Column menu action to quickly edit a record's status and notes directly from the table.

Why JSON Form: Simple edit operation, 2 fields, no workflow integration needed.

Example 3: Supervisor Approval (Use Screen Dialogue)

Scenario: An approval workflow that requires supervisor signature, comments, displays related documents, and triggers notifications.

Why Screen Dialogue: Requires web flow integration, displays additional data (documents), has conditional logic based on approval outcome, involves multiple related records.

Example 4: Batch Record Creation (Use Screen Dialogue or Separate Screen)

Scenario: Import or create multiple inventory items at once with validation against existing records.

Why Screen Dialogue/Separate Screen: Mass create operations, nested mutations, complex validation requirements exceed modal scope.

Example 5: Multi-Step Order Entry (Use Separate Screen)

Scenario: Order entry requiring customer selection, multiple line items, shipping configuration, and payment processing.

Why Separate Screen: Complexity exceeds what a modal should handle; requires tables for line items, multiple sections, and extensive workflow logic.

7. Troubleshooting

8. Related Resources

• Screen Designer Overview
• Action Button Configuration
• Screen Dialogue Actions
• Web Flows and Workflow Integration
• Data Model Field Reference

9. Revision History