# Conditional dictionaries

{% hint style="info" %}
Availability of the functionality depends on the license and may not be available in all deployments.
{% endhint %}

Conditional dictionaries are an optional variant of regular dictionaries. Using data passed to the dictionary, it is possible to write JavaScript conditions that decide the visibility of selected values from the dictionary. For example, a subset of cities from the city dictionary based on a selected province.

## Dictionary definition

The conditional dictionary definition window, in addition to the standard elements, will have a filled-in section **Visibility conditions**, **Input parameters** and keys and values associated with display conditions.

## Condition definitions

We add conditions in the side panel **Visibility conditions**, which will slide out after clicking the button in the left bar ![](/files/86552ff9640c56b8d04bbec7e08a501c8d815afd).

Each row represents one condition; the index allows the condition to be linked to the keys and values of the dictionary. The condition should be described with a JavaScript expression using input data from the mapping.

![Figure 1. Example conditions defined for the dictionary](/files/da467ceeb7c77c9b5aaa5e62680815fdd0b21584)

## Mapping input fields

In the **Input parameters**, which will slide out after clicking the button in the left bar ![](/files/40029e046420d337bb563014befdc91928d6d7c2), we can specify input data for the dictionary. Column **Variable** means the name of the variable that we will be able to use in JavaScript expressions when defining conditions, and **Alias** means the name of the variable visible when attaching the dictionary as a data source.

![Figure 2. Panel with example input parameters](/files/3a1d1ae981d59448c5f2aa87b58a2eefea851fe9)

## Mapping conditions to keys

Each condition defined earlier is reflected in the table of keys and values as a column, according to the assigned index. Selecting the checkbox at the intersection of the row with the key and the column with the condition means that the value will be visible when the condition evaluates to true.

![Figure 3. Example dictionary rows with mapped conditions](/files/b3deaaef13d268a12069b341442ce87b67d0c443)

## Condition evaluation

Conditions are evaluated in the order resulting from the index (which translates to: from left to right in the keys table), with **the first condition that evaluates to true determines the set of displayed values**.

## Using the conditional dictionary

We attach the conditional dictionary in the same way as a regular dictionary (instructions: [Connecting a dictionary data source](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/zasilanie-wartosciami-z-zewnetrznych-zrodel/podpiecie-slownikowego-zrodla-danych.md)). The only difference is that you also need to indicate mappings of input parameters to components:

![Figure 4. Example of mapping dictionary input fields to form components](/files/49dc2957c4e5a55364bd31658a9ce3e328d05cc5)

{% hint style="info" %}
Forms demo: demoSlownikiWarunkowe, demoCombobox
{% endhint %}


---

# 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://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/slowniki/slowniki-warunkowe.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.