> 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/eximee-dashboard/filtrowanie-listy-zadan-i-spraw.md).
# Filtering the task list and case list
In the Eximee Dashboard, it is possible to filter data on the task list and case list.
## Basic filtering
The mechanism for filtering the task list and case list allows tasks to be searched by a process variable **SEARCH\_STRING**. Multiple fields combined into a single string (e.g. separated by commas) can be passed to the variable, which makes it possible to search for data by a fragment of the value. The filter works based on the `LIKE` operator known from SQL.
The variable value **SEARCH\_STRING** should contain all data by which the user should be able to search.
Example script setting a value for the variable **SEARCH\_STRING**:
```js
def submittedLeads = execution.getVariable("submittedLeads")
def rejectedLeads = execution.getVariable("rejectedLeads")
def businessKey = execution.getVariable("start.formInstanceNumber")
def lead = execution.getVariable("Lead")
def cif = execution.getVariable("CIF_Klienta")
def time = execution.getVariable("Czas_lokalny")
def modSkp = execution.getVariable("SKP_Wypełniającego")
def skp = execution.getVariable("SKP_doradcy_portfelowego")
def branchSkp = execution.getVariable("Oddział_zgłaszającego")
def dashboardParams = [
"Application number" : businessKey,
"Selected leads" : lead,
"Client CIF" : cif,
"Application submission time" : time,
"Filler's SKP" : modSkp,
"Portfolio advisor's SKP" : skp,
"Branch SKP" : branchSkp,
"Submitted leads" : submittedLeads,
"Rejected leads" : rejectedLeads
]
searchString = businessKey + "," +
cif + "," +
time + "," +
modSkp + "," +
kp + "," +
branchSkp
execution.setVariable("PROCESS_DASHBOARD_DESCRIPTION", "Lead generation process")
execution.setVariable("PROCESS_DASHBOARD", dashboardParams)
execution.setVariable("SEARCH_STRING", searchString)
```
In the above example, searching will be possible, among others, by:
* application number,
* client CIF,
* submission time,
* SKP identifiers.
The basic search filter is located in the upper left corner (the field with a "magnifying glass"). Example of filtering the case list by branch SKP number:
Figure 1. Filtering the case list
For the filter to work correctly, the variable **SEARCH\_STRING** must be added to the process variables.
Filters are saved in the URL, which makes it possible to share a link with the set filters with other users and to change filters from the URL.
## Advanced filtering
The advanced filtering functionality is marked with the symbol: 
### Task list
Available filtering parameters:
* **Case status**
* Filtering by the businessStatus variable.
* Multiple-choice field.
* The list of available values is controlled by the variable **FILTER\_TASK\_STATUSES**.
* **Person assigned to the task**
Available options:
* all tasks,
* only my tasks,
* only unassigned tasks,
* tasks of selected users (search by a minimum of 3 characters, multiple users can be selected).
* **Task creation date**
* Ability to specify a date range (from – to).
* **Case type**
* Filtering by the variable **processDefinitionKey**.
* Multiple-choice field.
* The list of values is controlled by the variable **FILTER\_PROCESS\_TYPES**.
* **Case ID**
* Filtering by the businessKey variable.
* Searching works on the basis of the `LIKE`.
Figure 2. Advanced filter of the task list
### Case list
Available filtering parameters:
* **Case status**
* Filtering by the variable **businessStatus**.
* Multiple-choice field.
* The list of values is controlled by the variable **FILTER\_PROCESS\_STATUSES**.
* **Case type**
* Filtering by the variable **processDefinitionKey**.
* Multiple-choice field.
* The list of values is controlled by the variable **FILTER\_PROCESS\_TYPES**.
* **Case ID**
* Filtering by the variable **businessKey**.
* Searching works on the basis of the `LIKE`.
Figure 3. Advanced filter of the case list
---
# 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/eximee-dashboard/filtrowanie-listy-zadan-i-spraw.md?ask=&goal=
```
`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.