> For the complete documentation index, see [llms.txt](https://docs.flexikanban.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexikanban.ai/components/forms/tools/additional-fields.md).
# Additional Fields
You can use context object lookup values in the various form setting such as condition styles, option groups, related list actions using additional fields data. Using additional fields you can get lookup values up to 3rd level of dependency.
Below is example setup demonstrating adding of field and displaying it on the form. Form in the example is tied to Account object.
Open menu "Tools"(1) and select "Fields" option (2)
On "Fields" popup choose lookup field (3):
Choose one of the lookup fields (4) from the picklist containing Parent Account ID fields:
Choose field (5) from the next picklist containing User fields. Click "Add field" button (6):
Click 'Save' button (7).
{% hint style="info" %}
This field (8) stores email of a user who was last modifying Parent Account record linked to the Account.
{% endhint %}
Add [Static Text](x-screensteps-link://screensteps.com) component to the form:
* Expand "Options" section (9)
* Drag "Static Text" element (10) to the form
Select new field from the Context menu:
* Expand "Contex" section (11)
* Choose new field (12) from the "Context Fields" picklist
* Copy merge field (13)
Update text value of "Static Text" field:
* Expand "Setting" section (14)
* Paste merge field (13) into the "Text" field (15) of "Static Text" component
* Set "Title" field (16)
Save (17) the form and run (18) [Form preview](x-screensteps-link://screensteps.com):
Email (19) is displayed on the form preview:
---
# 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.flexikanban.ai/components/forms/tools/additional-fields.md?ask=&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.