# Input Step

The Input step is used to collect data from users at a specific point in the workflow. It allows for the creation of a custom input form, typically utilised by requesters to enter their request details. These forms are specifically built for each request type and workflow, providing flexibility to address various customer needs. This approach enables each request to have a unique form rather than adhering to a standard template, ensuring better alignment with customer requirements.

The Input form configuration panel consists of the below configuration tabs. Details about configuring commonly used tabs are included in the [Common Steps Configuration](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md) section. The configuration unique to the Input step is explained below.

* [General tab](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#general-tab) 
* [Form Fields ](#input-fields-tab)
* [Actions](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#actions-tab) 

And in the Advanced mode, additionally:

* [Pre-Actions](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#pre-actions-tab) 
* [Data Setup](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#data-setup-tab)
* [Advanced tab](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#advance-tab)

## Form Fields tab (aka Input Fields)

The Input Fields tab is the core element of the Input step, enabling the definition of the form's content displayed to end users. See and example of an access request input form below.

<div data-with-frame="true"><figure><img src="/files/pKm9fs1BkzFlEzdBXO6t" alt=""><figcaption></figcaption></figure></div>

All the fields shown above are added and configured in the Input Fields tab:

<div data-with-frame="true"><figure><img src="/files/3HhF4xDKZ9iEW20ih22q" alt="" width="563"><figcaption></figcaption></figure></div>

### A Form Field / Input Filed Configuration

#### Filed &#x20;

Identifies which [global field](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/global-settings.md) is used to save and store the specific user input data captured by this form field.  &#x20;

#### Control Type&#x20;

Each individual field on the input form is called a *UI Control* and can take the form of e.g. a text entry field, label, drop-down, checkbox, file uploader, etc., similar to typical online forms. The available UI controls include, for example:

* **Text Box**: For entering text or numbers.
* **Dropdown, List, SearchMultiSelect**: For selecting from predefined lists of options.
* **Date Picker**: For choosing dates.
* **File, ImageUploader**: For attaching documents or pictures.
* **Checkbox**: For true/false choices.
* **Label, Message**: For displaying information or instructions.

In the example above, *Areas you need access to* is a search drop-down list containing the available Command Centre Access Groups for user access requests.

#### Required Filed&#x20;

Specifies whether the user must complete the field to proceed with the workflow and submit the form.

#### **Input Value: Autofill**&#x20;

Fields can be automatically filled with data from the system (e.g., user’s name, department) and set as read-only if needed.&#x20;

#### **Display:** Hide and Read Only&#x20;

Input fields can either be visible for user interaction or hidden and used only for background processing.

#### **Display:** Read Only&#x20;

The fields can be set to read only e.g. e.g. The *RequesterName* field can be autofilled with the logged-in user’s name and set as read-only, so the user doesn’t have to type it in.

#### Properties&#x20;

*UI Controls* may have various properties that can be leveraged in the input forms. For example, the search drop-down list below allows for selecting multiple options.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/input-step.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.