# Case list
## Visibility configuration of cases on the case list
For a case to be visible on the list, permissions must be configured for the role [user](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/eximee-dashboard/konfiguracja/uprawnienia.md) (PROCESS\_DEFINITION\_KEY\_MAPPING parameter).
Additionally, case visibility on the list is controlled by the mechanism: Dynamic definition of access to the case list (setAccessGroups).
{% hint style="warning" %}
This mechanism grants only \*\*additional\*\* permissions. The functionality does not allow removal of case permissions granted through PROCESS\_DEFINITION\_KEY\_MAPPING.
{% endhint %}
## Case label configuration
It is possible to configure the label for a case in the left part of the tile on the Eximee Dashboard page, available e.g. at the address:
```
ROUTER_HOST:8083/router-ui/#/processes
```
To configure the label, a new task of type should be created in the BPMN process *ScriptTask* and attached to the process:
Figure 1. "ScriptTask" task configuration
In the configuration [of the script task](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/zadania-automatyczne/zadanie-skryptowe-bpms-scripttask.md) set:
* **Script Format**: groovy
* **Script Type**: Inline Script
* **eScript**: Here is Groovy code that will set in the variable **PROCESS\_DASHBOARD\_DESCRIPTION** the value of the label as a text type, e.g.
```
execution.setVariable("PROCESS_DASHBOARD_DESCRIPTION", "Foreign currency loan application");
```
Figure 2. Case list
When the process is completed (has status *COMPLETED*), the text is displayed: *Case completed*.
When the process is not completed and the variable is not filled in **PROCESS\_DASHBOARD\_DESCRIPTION** then we do not display the label.
In other cases, we display the text specified in **PROCESS\_DASHBOARD\_DESCRIPTION**, in the example it is "Process start" and "Form".
## Data display configuration
It is possible to configure the data displayed in the middle part of the tile on the Eximee Dashboard page, available e.g. at the address:
```
ROUTER_HOST:8083/router-ui/#/processes
```
To configure which data we want to display in the middle part of the tile, a new task of type should be created in the BPMN process *ScriptTask* and attached to the process:
Figure 3. "ScriptTask" task configuration
In the configuration [of the script task](/documentation/documentation-en/budowanie-aplikacji/proces-biznesowy/zadania-automatyczne/zadanie-skryptowe-bpms-scripttask.md) set:
* **Script Format**: groovy
* **Script Type**: Inline Script
* **Script**: Here is Groovy code that will set in the variable **PROCESS\_DASHBOARD** the configuration map of the right side of the tile.
We can add configuration in the form of label-value pairs, which will be displayed on the case list in Eximee Dashboard.
Remember that values in the key must be unique.
Literals or process variables can be passed to the map values using:
```
execution.getVariable("VARIABLE_NAME");
```
Sample code completing the configuration:
```js
execution.setVariable("PROCESS_DASHBOARD", [
"Label1": "Value1",
"Label2": execution.getVariable("variable1")
]);
```
We can also specify the order of displayed variables by placing a number in square brackets at the beginning of the key, based on which the variables will be sorted, e.g. "\[1]Label". Such a number will not be displayed, and variables without a number will go to the very end. For example, a map:
```js
execution.setVariable("PROCESS_DASHBOARD", [
"[3]A": "A",
"B": "B",
"[1]C": "C"
]);
```
will be displayed as key-value pairs in the order of labels C, A, B.
---
# 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/eximee-dashboard/konfiguracja/lista-spraw.md?ask=
```
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.