# Process Step

The **Process Step** is a crucial component within the workflow system, designed for executing predefined processes like *Find cardholder* or *Create credential*. It operates in the background and is not usually visible to end users, handling automated backend actions and facilitating integration with external or internal services.&#x20;

{% hint style="info" %}
Example processes include: *Find Cardholder*, *Create Credential*, *Log Command Centre Event*, *Send email*, *Setup Approval*.
{% endhint %}

The step configuration side 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 Process 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)&#x20;
* [Process tab ](#process-tab)
* [Actions](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#actions-tab)&#x20;

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)&#x20;
* [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)

## Process tab&#x20;

Below are instructions explaining the role and use of the configuration options within the Process tab of the process step.

#### Process&#x20;

The Process configuration dropdown in the tab links the step to one of the processes defined in the [Global Settings](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/global-settings.md#processes-tab). This means the step executeson of the predefined processes e.g. Command Centre cardholder lookup. &#x20;

#### Render As Loading Page, Loading Message &#x20;

Enable this option to display the step as a loading page with a predefined message, allowing users to access it in the interface while the task is in progress.

#### Parameter Map, Output Map&#x20;

Configurations for a Process Step involve setting up parameter maps for inputs and output maps for results. They define which workflow fields are passed into the process and which outputs are returned.&#x20;

Each process type, e.g., *Find Cardholder*, has fixed parameters that cannot be altered. If a different process is chosen from the process configuration dropdown, the parameters are updated. The interface dynamically adjusts to show relevant fields based on the chosen process, ensuring ease of configuration and integration.

Outputs represent the data produced after a step executes the process. Outputs are not always present, but are common in process where data is returned. Output mapping is utilized for capturing process outputs, such as e.g. values returned from Command Centre. These outputs may include information like the cardholder's *Name*, *Last name*, *Department*, *Phone*, *Role*, and other requested data.

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

## **Send Email Process**&#x20;

Email notifications can be sent through both the Process step and the [Process Task step](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/process-task-step.md). However, the Process Task step is primarily used to notify approvers of new approval tasks. Most email notifications within the workflow are sent via the Process step.

### Email notifications sent by Process step&#x20;

Sending an email notification based on a template is also executed by the Process Step. Notifications are emails or alerts sent to users or groups during the workflow, often in response to specific events (like approval or failure).

**Details:**

* **Notify**: Sends notifications during a step.
* **NotifyOnProcessResponse**: Sends notifications based on the outcome of a process (e.g., only if activation succeeds).
* **Templates**: Predefined email templates for consistent communication.
* **Recipients**: Can be set to specific users, groups, or roles.

**Example:**

* After a card is activated, the workflow sends a confirmation email to the requester.
* If activation fails, it sends an error notification with instructions.


---

# 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/process-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.
