> 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/wprowadzenie/architektura-platformy/moduly-wykonawcze/eximee-case-management.md). # Eximee Case Management **Eximee Case Management** This is the Eximee platform module responsible for managing cases, tasks, and the users' work context.\ It enables full case lifecycle handling – from case initiation, through execution and progress monitoring, all the way to archiving the history of activities.\ This module integrates data coming from EximeeBPMS processes, data models, and external applications, creating a central place for managing business cases. ## Module role and architecture ### **General description** `Eximee Case Management` It serves as an intermediary layer between business processes (EximeeBPMS), user forms (Eximee Forms), and operational applications (e.g., Eximee Dashboard, BackOffice).\ It provides a set of tools for displaying and executing tasks, browsing cases, and interacting with the user context. ### **Module goals** * Consolidation of case and task data from multiple sources. * Providing users with a unified interface for completing tasks. * Relieving the BPMS process engine from storing and presenting operational data. * Model support *Case-Oriented Processing* – focused on the customer or case context, rather than on the process itself. ### **Logical architecture** The module consists of the following layers: 1. **Presentation layer** – user interface (usually embedded in Eximee Dashboard). 2. **Application layer** – Case Management logic (task handling, lists, business actions). 3. **Integration layer** – communication with EximeeBPMS, Data Model Runtime and Forms. 4. **Data layer** – repository of case states and event history (independent of BPMS). ## Functionality ### **User task handling** * List of tasks assigned to the user or team. * Filtering, sorting, and searching tasks. * Configurable columns and list layouts. * Handling priorities, deadlines, and statuses. * Executing subsequent tasks in sequential mode (*Next Best Task*). * Group task handling (batch operations). * Ability to execute automatic tasks in the background (automation engine). * Integration with forms **Eximee Forms** as the user interface. ### **Case handling (Case View)** * Overview of cases and their statuses. * Filtering and sorting the case list by business context (e.g., customer, product, process). * Detailed case view with information about: * activity and decision history, * attached documents, * related tasks, * contextual data (from the data model). * Ability to launch forms and micro-applications in the context of a given case. * Creating new cases by the user (e.g., in FrontOffice or BackOffice). ### **History and event handling** * Recording case history independently of the workflow engine (EximeeBPMS). * Using events from business processes and applications (Event-Based Architecture). * Recording user actions and status changes. * Support for auditing in compliance with regulatory requirements (e.g., KNF). ### **Business actions** * Definable actions available to the user in the context of a case or task (e.g., “Approve”, “Reject”, “Forward”). * Parameterization of available actions at the low-code application level. * Support for system and custom actions (custom handlers). ### **Customer context handling** * Presentation of customer data related to the case. * Integration with CRM, KYC, scoring systems, etc. * Dynamic loading of contextual data. ## Integrations ### **Integration with EximeeBPMS** * Passive use of the BPMS engine – Case Management does not execute processes, but monitors them. * Subscription to process events (task created, task completed, incident occurred). * Reading process data via the BPMS API. ### **Integration with Eximee Forms** * Forms provide the user interface for tasks in Case Management. * Each task can launch the assigned low-code form. * Shared data context (case ↔ form ↔ process). ### **Integration with Eximee Model Runtime** * Fetching contextual data for the case and customer. * Updating data during task execution. ### **Integration with Eximee Dashboard** * Case Management is one of the key modules of Eximee Dashboard. * It provides screens for case, task, and history lists. * It enables embedding micro-applications that support work (e.g., notes, calendar, document list). ## Technical features * Microfrontend architecture with the ability to expand with extension applications. * Built-in filtering, sorting, and pagination mechanisms. * Scalability and separation of user contexts. ## Example usage scenarios ### **FrontOffice / BackOffice** * An advisor opens a customer's case and sees a list of all related tasks. * Performs successive process steps (e.g., “Data Verification”, “Contract Approval”) by launching a form. * The case history is automatically updated based on BPMS events. ### **Operations manager** * Reviews the team task list and prioritizes it. * Performs batch operations, e.g., task assignment or status changes. * Analyzes employee workload based on metrics from Case Management. ### **External partner** * Receives a view of their cases and tasks within a shared partner channel. * Handles selected process stages, e.g., verification of customer documents. ## Common features and deployment parameters * **Configuration flexibility:** list, detail, and action views defined low-code in Case Management Designer. * **Reusability:** one Case Management component can serve many applications. * **Security:** full access control to data and operations based on domain roles. * **Customization:** ability to adapt layout, filters, and actions to the specifics of the implementation. * **Scalability:** separation of presentation logic from process data enables independent scaling. --- # 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/wprowadzenie/architektura-platformy/moduly-wykonawcze/eximee-case-management.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.