> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/product-tour/records/field-path.md).

# Field Path

Add a path for any field, grouping several values under custom stages.

GridMate provides a component to deal with paths. Unlike Salesforce Standard Path, **GM - Field Path** is not related to a specific path. The component can be used for many fields on the same object without any limitation. Also the stages can be customized to group different values under the same umbrella.

In this tutorial, we will setup a path for the case status. Below is a quick demo on how to configure the **GM - Field Path** component.

{% embed url="<https://youtu.be/ltq_J3IAjOs>" %}
GM - Field Path
{% endembed %}

{% hint style="info" %}
The [configuration wizard](https://docs.gridmate.io/advanced-guides/grid-setup/grid-configuration.md#kanban-stages-property) could be used to generate the **Path Stages** property. Below are the stages configured for the demo.
{% endhint %}

```coffeescript
[
   {
      "label": "New",
      "filter": {
         "Status": {
            "operator": "in",
            "value": "('New')"
         }
      }
   },
   {
      "label": "Working On",
      "filter": {
         "Status": {
            "operator": "in",
            "value": "('Escalated','Investigating')"
         }
      }
   },
   {
      "label": "On Hold",
      "filter": {
         "Status": {
            "operator": "in",
            "value": "('On Hold')"
         }
      }
   },
   {
      "label": "Closed",
      "filter": {
         "Status": {
            "operator": "in",
            "value": "('Closed')"
         }
      }
   }
]
```

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>GM - Field Path</strong></td><td>Every property of the component.</td><td><a href="https://docs.gridmate.io/package-reference/components-library/records/gm-field-path.md">GM - Field Path</a></td></tr><tr><td><strong>Grid - Advanced Configuration</strong></td><td>Generate property values step by step with the Config Wiz.</td><td><a href="https://docs.gridmate.io/advanced-guides/grid-setup/grid-configuration.md">Grid - Advanced Configuration</a></td></tr></tbody></table>


---

# 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://docs.gridmate.io/product-tour/records/field-path.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.
