> 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/eksploatacja-aplikacji/obsluga-procesow/eximee-dashboard/rejestracja-zdarzen-procesu/zakladka-historia-sprawy.md). # "Case history" tab Tab **Case history** is available in Eximee Dashboard for logged-in users with the permission "case\_history\_process\_history".

Figure 1. List of cases with the action window open

Parameter **CASE\_HISTORY\_STATUSES\_BLACKLIST** allows defining a list of business process statuses for which the tab is not displayed **Case history**. ## Case History View Tab **Case history** is available: * in the task list, * in the case list in the Tasks menu, * directly in the case view – as a dedicated tab, * directly in the task view – as a dedicated tab.

Figure 2. "Case History" tab

On the left side, a list of events related to processing the selected case is shown, displaying the following data: * **Event type** - event\_code, * **User** - username, first\_name, last\_name (the user assigned to the task at the time of the event; if no user was assigned, "SYSTEM" is shown here), * **Event description** - event\_description, * **Date and time of event** - data\_time. When an item is selected from the list, event details are shown on the right side, and (in the case of business events) additional event data. The data source for the view is the table **case\_history\_process\_history** provided as part of the platform. ## Filtering Case History Navigating through entries **of the case history** is facilitated by the filtering option.

Figure 3. Event filters in the "Case History" tab

The view can be narrowed down according to the following criteria: * Event type * Business - business events are shown, * System - system events are shown, * Event type, * Username, * Start date / End date. If a filter field has no value, it means no narrowing according to the criterion associated with that field (the checkboxes regarding event type are treated jointly). Drop-down lists in the filter fields are populated from current values in the history database.

Figure 4. List of entries in the database

Figure 5.Selection lists in filters

--- # 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/eksploatacja-aplikacji/obsluga-procesow/eximee-dashboard/rejestracja-zdarzen-procesu/zakladka-historia-sprawy.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.