# Eximee Case Repository **Eximee Case Repository** is the central repository of the bank’s customer cases, serving as a common point of reference for all channels and applications supporting customer processes.\ Its main task is **to store, share, and track the history of contacts and case statuses** regardless of the system in which they were initiated or carried out. ## Role and purpose Eximee Case Repository serves as a **integration and archiving layer**, enabling a consistent view of case statuses and data from multiple sources.\ The repository collects data on all customer interactions with the bank — both those handled automatically by systems and those carried out by employees.\ This makes it possible to: * preserve the full history of the customer’s cases, * build a consolidated “360°” customer view, * present current statuses and activities regardless of the service channel. ## Functional scope ### Main functions of Case Repository * **Storing customer cases** — persisting case data from various banking applications, regardless of technology and channel. * **Activity history log** — recording all actions performed by users and systems in the context of a specific case. * **Data aggregation** — combining information from Eximee BPMS processes, forms, API, and external systems. * **Unified data model** — every case object complies with the common data schema (data model) used across the entire Eximee platform. * **Publishing case data** — exposing case information for display in various channels, e.g. CRM, electronic banking, or back-office applications. ## Operating principles and data integration Any applications supporting customer processes — both those built in **Eximee Low-Code Platform**, and the bank’s independent systems — can feed the **Case Repository** with data.\ To do this, they must: 1. create an object compliant with the common data model, 2. publish it to the repository using an event mechanism (e.g. **Apache Kafka**). The repository operates based on an **event-driven architecture**, which means that status and event updates are processed in real time and propagated to all interested systems. ## Presentation and use of data The customer case list, together with its business statuses, can be: * displayed as a **microfrontend** in customer applications (e.g. internet and mobile banking), * embedded in bank employee applications (e.g. CRM, Contact Center, Back-Office), * made available to external systems via Eximee API. This approach ensures a consistent user experience and centralized access to information about all customer processes. ## Architecture and information flow **Eximee Case Repository** is a central element of the platform’s information architecture.\ Case data: 1. **are created** in various components (BPMS, Forms, API, Customer Panel, Service Zone), 2. **are aggregated** and published in the Case Repository, 3. **made available** to other modules and external systems in the form of a structured “Case” object. The repository can be used both in **online** mode (presentation of active cases), and in **archival** mode (history of completed cases). ## Data model Each record in **Eximee Case Repository** has a unified data model containing, among others: * case identifier (Case ID), * customer data and product context, * status and process stage, * metadata (creation, update, and closure dates), * a list of events and actions, * links to documents and processes (BPMN, Forms). The model is consistent with the definitions of data stored in **Eximee Data Model Runtime**, which enables seamless integration between components. ## Security and access * **Authorization:** based on domain roles and organizational context. * **Availability:** control of case visibility with respect to the user and channel. * **Integration with Eximee Security Framework:** inheritance of authorization rules from the platform. * **Audit:** every publishing and read operation is logged. * **Encryption of sensitive data:** TLS 1.2+ and integration with the bank’s KeyVault. ## Key features of Eximee Case Repository * Central repository of all customer cases. * Support for data from multiple sources – Eximee processes and external systems. * Unified data model (Case Data Model). * Event-driven architecture. * Support for microfrontends and multichannel integration. * Full security and audit. * Scalability and high availability. * Compliance with the Omnichannel approach. ## Summary **Eximee Case Repository** is a key integration element of the Eximee ecosystem.\ It provides a central source of truth about all customer cases, regardless of the system or channel in which they were created.\ As a result, it enables the creation of consistent customer views, process automation, and improved service efficiency.\ It is the foundation for reporting, analytics, and communication between channels in the architecture **Omnichannel Banking**. --- # 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/wprowadzenie/architektura-platformy/rozszerzenia-platformy/eximee-case-repository.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.