> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/data-initialisation-step.md).

# Data Initialisation Step

The **Data Initialisation** block is a crucial first step in every workflow template. Its purpose is to configure the necessary [fields](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/global-settings.md#fields-tab) and values that the workflow requires before any process steps can be executed. 

The Data Initialisation step:

* Assigns **initial or default values** for [Fields](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/global-settings.md#fields-tab). 
* Ensure fields required by later steps are populated.

The Input form configuration panel consists of the below configuration tabs. Details about configuring commonly used tabs are included in the [Common Steps Configuration](/knowledge-hub/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](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#general-tab) 
* [Data Setup tab ](#data-setup-tab)

And in the Advanced mode, additionally:

* [Fields tab](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/input-step.md#input-fields-tab)
* [Pre-Actions tab](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#pre-actions-tab)
* [Actions tab](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#actions-tab)

## Data Setup tab 

Data Setup tab makes use of the [fields](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/global-settings.md) defined in the Global Settings. The configuration of the fields in the step facilitates workflow customization.

The workflows require references or identifiers to enable working with a particular AccessNow and Command Centre set up. Using the Data Setup tab you can link a specific field to e.g.   

* The list containing the Command Centre Access Groups. 
* PDF ID that uniquely identifies the cardholder in Command Centre. 
* PDF ID that indicates the cardholder's department in Command Centre. 
* Approver Group that should action an approval in the workflow, etc.
* Notification email template that should be used when a request is completed. 

These are examples of workflow customizations that vary among different AccessNow customers. All of these values can be set in the Data Setup step, including: 

* Default [Approver Groups](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/approver-groups.md)
* Command Centre cardholder lookup fields ([PDF reference IDs](broken://pages/Q8ZBe78gUpYN1tmHXtbV))
* [Access Groups list](broken://pages/SoiSzajIsGHCsghZJ4zN) used in the workflow. 
* [Email Templates](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/email-templates.md) to be used in the workflow.  
* And any other field that needs a known input before a workflow can run. 

<div data-with-frame="true"><figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2FmMvhz8pDN5WlO4xodaAi%2Fimage.png?alt=media&amp;token=989910ea-3477-4387-a4e5-c320688c1d99" alt="" width="546"><figcaption></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/data-initialisation-step.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.