> 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-dashboard.md). # Eximee Dashboard **Eximee Dashboard** This is the Eximee platform application module, serving as the central work interface for internal users, intermediaries, and the bank's partners.\ It serves as **an application container** (in English *application shell*), integrating various Eximee microapplications in one environment, such as **Case Management**, **Forms**, **Document Viewer** or dedicated operational extensions. Thanks to its modular architecture and support for microfrontends, Eximee Dashboard enables flexible composition of the user work environment, tailored to the user's role, competencies, and the processes carried out in a given implementation. ## Module role and architecture ### **General description** `Eximee Dashboard` is a browser application that serves as the main entry point to the Eximee environment for bank employees, intermediaries, and partners.\ Its primary task is to integrate Eximee modules and present data and tasks in a consistent, configurable interface. ### **Module goals** * Provide the user with a single point of access to all Eximee applications and processes. * Enable work in multiple contexts (tasks, cases, documents, forms). * Integration with identity, permissions, and competency systems (AD, LDAP). * Flexible expansion with microapplications and low-code components. * Increase user ergonomics and productivity by consolidating tools. ## System architecture `Eximee Dashboard` is based on a **microfrontend**, in which individual modules (e.g., Case Management, Forms, Notes, Calendar) operate as independent components, loaded dynamically in the context of the main container. ### **Architecture layers** 1. **Presentation layer** – user interface (SPA – Single Page Application). 2. **Microfrontend layer** – dynamically attached applications (e.g., task lists, case history, form view). 3. **Integration layer** – communication with Eximee modules (BPMS, Model Runtime, Repository). 4. **Security layer** – integration with authentication and authorization systems (LDAP, SSO, OAuth). ## Functionality ### **Microapplication management** * Adding and configuring microapplications within the Dashboard (e.g., notes, meeting scheduling, documents). * Launching low-code microapplications defined in Eximee Repository. * Support for microfrontends written in different technologies (React, Angular, Vue). * Isolation of microapplication contexts (session, data, permissions). * Communication between microfrontends using events and application context. ### **Integration with Eximee Case Management** * Built-in task and case lists. * Presentation of case details and activity history. * Launching Eximee Forms in the context of a task or case. * Configurable business actions and operational shortcuts. ### **Integration with Eximee Forms** * Ability to launch low-code forms in modal windows or Dashboard tabs. * Passing contextual parameters (e.g., case ID, customer data). * Support for multiple form sessions in parallel (e.g., several open applications). ### **User and role management** * Integration with Active Directory or LDAP for authentication and authorization. * Mapping of business roles (e.g., Advisor, Analyst, Manager). * Support for domain permissions within microapplications. * Support for regionalization and competency assignment. ### **Work context management** * Dynamic switching of the user context (e.g., „employee mode”, „manager mode”). * Presentation of data from various modules in one view (e.g., customer data, case history, attachments). * Remembering the state of the user interface (layout, filters, open tabs). ### **Additional functionality** * Ability to integrate with the bank's external systems (CRM, DMS, Contact Center). * Customization of the interface appearance (bank Design Guide). * Support for multiple languages. * Full compliance with WCAG 2.1. * Logging of user events (activity log). ## Integrations ### **Eximee Case Management** * Displaying task and case lists in the user's context. * Handling business actions directly from the Dashboard. * Sharing customer and case context between microapplications. ### **Eximee Forms** * Launching forms within the Dashboard (integrated mode). * Synchronization of the form state with the task context. * Ability to continue interrupted applications (draft copy). ### **Eximee Repository** * Downloading microapplication definitions, layouts, and screen configurations. * Migrating configuration between environments (DEV, UAT, PROD). ### **Eximee Model Runtime** * Reading contextual data for presentation in microapplications. * Updating data while user tasks are being performed. ### **External bank systems** * Integration with CRM, analytical systems, DMS, and internal communication tools. ## Technical features * Architecture based on SPA (Single Page Application) and microfrontends. * Modular structure enabling easy addition of new components. * Communication API between microapplications (inter-component messaging). * Support for federated authorization (OAuth 2.0, SAML, OpenID Connect). * Can be deployed as a standalone or embedded application (e.g., in the bank's intranet). * Support for session cache and storing user settings in the browser. * Horizontal scalability (stateless module). ## Example usage scenarios ### **BackOffice employee** * Logs in to Eximee Dashboard via AD. * On the main screen, sees a list of their tasks from Case Management. * Opens the Eximee Forms form assigned to the task. * After completing the task, sees the list state refreshed automatically. ### **Team manager** * Uses the microapplications „Team Tasks” and „Statistics”. * Can assign tasks, filter cases, analyze employee workload. ### **External partner** * Opens the Dashboard in partner mode (OAuth authorization). * Has access only to the microapplications assigned to their role. * Carries out their own tasks and transfers data to the bank system. ## Common features and deployment parameters * **Deployment flexibility:** can support different user groups within a single instance. * **Reusability:** microfrontends shared between applications. * **Security:** integration with identity systems and access control. * **Customization:** configurable layouts, microapplications, colors, and branding. * **Scalability:** support for a large number of users and microapplications in one environment. * **Availability:** full compliance with WCAG 2.1 and support for multiple languages. --- # 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-dashboard.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.