> 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/end-process-step.md).

# End Process Step

The End Process Step is a component used to signal that all actions in the workflow are complete. This step serves as a logical endpoint and does not require user input. It typically lacks configurable fields, serving primarily to mark the workflow's completion and can activate any final notifications or logic needed. Each workflow branch should conclude with the End Process step.

The step configuration side 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 End Process 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) 
* [Track Request Fields tab](#track-request-fields-tab)

And in the Advanced mode, additionally:

* [Data Setup](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#data-setup-tab)
* [Advanced tab](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/steps/common-steps-configuration.md#advance-tab)

## Track Request Fields tab 

Summary fields are a type of input field found in the Input Fields tab, specifically related to the final process step. They capture outcome information from the workflow, which can later be used in notifications, such as an email.


---

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