> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/pomoc-kontekstowa.md).

# Contextual help

Most components in Eximee Designer can have context help defined. Exceptions are components **QR code generator** and **Page**.

<figure><img src="/files/09bc3292950e6927e9c760cf88090fed30a8b25d" alt=""><figcaption><p align="center"><em><strong>Figure 1.</strong> Appearance of the property that provides access to the context help editor</em></p></figcaption></figure>

When entering the context help editor, a drawer slides out. If the component has no context help added, the drawer contents look as shown in the illustration below.

<figure><img src="/files/ac002e6fd89fd2aae02ec7625c88ba2c44d7d68b" alt=""><figcaption><p align="center"><em><strong>Figure 2.</strong> Appearance of the editor drawer with no context helps added</em></p></figcaption></figure>

Clicking the button located at the bottom of the drawer **Add context help** adds an item to the drawer. It represents a new context help.

<figure><img src="/files/1df34569e574d9be888b5d217dcc1fcdc52b61b9" alt=""><figcaption><p align="center"><em><strong>Figure 3.</strong> Appearance of the newly added and unconfigured context help</em><br></p></figcaption></figure>

The basic editable properties are the context help key name and its display condition.

Before adding a key with the help content, the key and its content should be added in the tab **Translations**. Editing is done by clicking in the field **Enter key name**.

In the field **Add condition** you can define dynamic context help with content depending on conditions:

* session variable values,
* values of other components.

If several context helps are defined, only the first context help whose condition is met will be displayed. To change the order of the help content, drag & drop functionality can be used.

<figure><img src="/files/1bbbd8887737e66a404d4fe000aed3cfd17928d6" alt=""><figcaption><p align="center"><em><strong>Figure 4.</strong> Example of two different context helps defined and displayed conditionally</em></p></figcaption></figure>

Clicking in **Show details** expands the tile and allows access to additional options, visible in the illustration below:

<figure><img src="/files/d365e83ea336bf2a1a5a112a1545c16debf81de1" alt=""><figcaption><p align="center"><em><strong>Figure 5.</strong> Appearance of the expanded context help editing window</em></p></figcaption></figure>

In the detailed view, the following properties can be defined:

* **Style name** - name of the style to be applied to the context help,
* **Help icon** - determine whether a context help icon should be displayed,
* **Visible on field focus** - determine whether context help should be displayed during selection,
* **Interactive context help** - determine whether it will be possible to interact with the context help content,
* **Width/Height** context help tooltip,
* **Position** of the context help relative to the component it applies to.

In the context help editor drawer, multiple tooltips can be defined. They are then considered from top to bottom. Each context help tile has a handle on the left side that allows you to grab it and then move it to the desired position. In this way the entire list can be sorted and the order of the items changed.

**Context help visibility**

In the detailed view, one of two ways of presenting context help must be specified:

* Help icon,
* Visible on field focus.

Context help visibility is also controlled by an optional condition.

<figure><img src="/files/25dd094cc096a5dc1e62b7059dc77013618ba07c" alt=""><figcaption><p align="center"><em><strong>Figure 6.</strong> Example appearance of the tooltip in the application</em></p></figcaption></figure>

<figure><img src="/files/87859fec546f7503a9bd9999f8ced1b2bbf7e773" alt=""><figcaption><p align="center"><em><strong>Figure 7.</strong> Example appearance of the tooltip in the application</em></p></figcaption></figure>

{% hint style="info" %}
Demo application: demoTooltips
{% endhint %}

{% hint style="info" %}
♿WCAG: [Good WCAG practices for low-code dev](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/tworzenie-procesu-biznesowego-w-bpmn-2.0/dobre-praktyki.md)
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/pomoc-kontekstowa.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.