---
schema_version: "1"
id: 6b2d1ed427bbe2369500c2542daa3509ee770e27b4d89b272fdc39bf2e16de40
title: Collect Information from Users in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_fields_and_forms.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_and_forms.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8954960ecbce4702618eea6facf7e4894131fad39046703f1bed098ac190c8c1
description: Use fields and forms to request, collect, and pass information through tasks and workflows in Agentforce Operations.
products:
  - Cross Cloud
release: "264"
---
# Collect Information from Users in Agentforce Operations

Use fields and forms to request, collect, and pass information through tasks and workflows in Agentforce Operations.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d21818e37">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d21818e37 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table>

## How Fields Work

Fields are the building blocks for data collection in your workflows. Create custom fields one time and reuse them across multiple blueprints, or use Agentforce Operations system fields that are available in every workspace.

Add fields to the **Request information** section to collect data from assignees. After the assignee enters values, those values flow forward automatically to downstream tasks where you can reference them in other fields, conditions, or AI agent prompts.

Fields support a range of data types so you can collect exactly the information your process requires. Select the field type that matches your data: Text for open-ended responses, dates for scheduling, people fields for assignments, and so on.

To learn about how fields relate to blueprints, workflows, and tasks, see [How Blueprints, Workflows, and Tasks Connect in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_workflows_tasks.htm&release=264.0.0&type=5 "In Agentforce Operations, blueprints, workflows, stages, tasks, and fields each play a specific role and work together in a clear hierarchy to automate business processes. Understanding how they connect helps you plan your processes before you start building blueprints and running workflows.").

## System Fields

Agentforce Operations includes system fields that are available in every workspace without any setup. System fields capture workflow metadata and information from workflows automatically. You don't create or configure these fields. They show in your workspace automatically.

To see the list of system fields, go to the **Home** page and then click **Columns**. The list of system fields are in the System information section. To see the field's description, hover over the "i" icon next to the field.

## Custom Fields

Create custom fields to collect information specific to your processes. Custom fields support different data types to match what you're collecting. For example, use currency fields to capture pricing or budget amounts, number fields to track quantities or percentages, or signature fields to collect electronic approvals. Select fields collect an option from a list, and data source fields can collect information from external systems like CRM or ERP platforms.

For a complete list of available field types and their capabilities, see [Field Types in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_types.htm&release=264.0.0&type=5 "Review the field types available for collecting information in tasks in Agentforce Operations."). To learn how to create and add fields, see [Create Custom Fields in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_create.htm&release=264.0.0&type=5 "Create custom fields to collect information from users. You can create custom fields from the Fields page, a task, or the Form Builder.").

## Using Fields to Split Tasks

Use multi-value fields to split tasks into multiple parallel instances at run time. When you configure a task to split based on a multi-select, people, role, document, or data source field, Agentforce Operations creates a separate task instance for each value in that field. You can process multiple tasks in parallel without manually duplicating the same task for each item.

For example, if an upstream task collects a list of suppliers in a multi-select field, you can split a subsequent review task to create one task per supplier. If you split on a people or role field, each person automatically receives their own task assigned to them. Split tasks work with standard tasks, approval tasks, and even AI agent tasks.

To learn more, see [Split a Task into Duplicate Tasks in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_tasks_split.htm&release=264.0.0&type=5 "Spawn multiple run-time instances of a single task based on a multi-value field in Agentforce Operations.").

## Forms

When you want to collect information from assignees, build a form in the **Request information** section of standard and approval tasks. Forms organize fields into a structured layout with sections, instructional text, 2-column layouts, and fields. This structured approach makes it easier for assignees to understand what information they must provide and why.

All form data must exist inside sections, so you start by adding a section. Then add instruction text, 2-column layouts, or fields to the section. For example, create a form to collect customer contact information, gather order details, or request project specifications. To learn more, see [Build a Form to Request Information in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_create_forms.htm&release=264.0.0&type=5 "Build a form inline in a task’s Request information section to collect structured information from task assignees in Agentforce Operations.").

## Smart Rules for Forms

Use smart rules to show, hide, or require sections, fields, and instructional text in a form, based on conditions. Smart rules evaluate conditions based on values from fields earlier in the form. For example, show a section only when an assignee selects a specific approval type, hide instruction text that doesn't apply to a particular scenario, or require a field only when specific criteria are met.

Smart rules create dynamic forms that adapt to the information task assignees provide, which reduces clutter and prevents errors. To learn more, see [Configure Smart Rules in Forms in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_request_information_smart_rules.htm&release=264.0.0&type=5 "Use smart rules to show, hide, or require sections, fields, and instruction text in a form based on conditions in Agentforce Operations.").

## Field Versioning

When you edit a field, Agentforce Operations creates a new version of the field. Field versions make sure that running workflows continue to use the original field definition while new workflows pick up the updated version. Versioning prevents changes from breaking workflows that are in progress.

Field versions apply to select and multi-select fields when you add, remove, or rename options. Other field types create new versions only when you change fundamental properties like data type or validation rules. To learn more, see [Manage Field Versions in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_versions.htm&release=264.0.0&type=5 "Update fields, view version history, and apply the latest field versions to blueprints in Agentforce Operations.").

To learn more, explore these links.

- **[Field Types in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_types.htm&release=264.0.0&type=5)**  
    Review the field types available for collecting information in tasks in Agentforce Operations.
- **[Create Custom Fields in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_create.htm&release=264.0.0&type=5)**  
    Create custom fields to collect information from users. You can create custom fields from the Fields page, a task, or the Form Builder.
- **[Manage Field Versions in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_versions.htm&release=264.0.0&type=5)**  
    Update fields, view version history, and apply the latest field versions to blueprints in Agentforce Operations.
- **[Build a Form to Request Information in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_fields_create_forms.htm&release=264.0.0&type=5)**  
    Build a form inline in a task’s Request information section to collect structured information from task assignees in Agentforce Operations.
- **[Configure Smart Rules in Forms in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_request_information_smart_rules.htm&release=264.0.0&type=5)**  
    Use smart rules to show, hide, or require sections, fields, and instruction text in a form based on conditions in Agentforce Operations.