Eximee Case Management

Eximee Case Management this is the Eximee platform module responsible for managing cases, tasks and users' work context. It enables full support for the case lifecycle – from its initiation, through execution and progress monitoring, to archiving the history of actions. This module integrates data coming from EximeeBPMS processes, data models and external applications, creating a central place for managing business cases.

Role and architecture of the module

General description

Eximee Case Management 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 presenting and performing tasks, browsing cases and interacting with the user context.

Module objectives

• Consolidation of case and task data from multiple sources.

• Providing users with a unified interface for task execution.

• Offloading the BPMS process engine from storing and presenting operational data.

• Support for the Case-Oriented Processing – focused on the customer or case context, not on the process itself.

Logical architecture

The module consists of the following layers:

1. Presentation layer – user interface (typically embedded in Eximee Dashboard).

2. Application layer – Case Management logic (handling tasks, 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 a user or team.

• Filtering, sorting and searching tasks.

• Configurable columns and list layouts.

• Support for priorities, deadlines and statuses.

• Performing subsequent tasks in sequential mode (Next Best Task).

• Group handling of tasks (batch operations).

• Ability to execute automatic background tasks (automation engine).

• Integration with forms Eximee Forms in the role of the user interface.

Case handling (Case View)

• Overview of cases and their statuses.

• Filtering and sorting the case list by business context (e.g. client, product, process).

• Detailed case view with information about:

  • history of actions and decisions,

  • attached documents,

  • related tasks,

  • contextual data (from the data model).

• Ability to launch forms and micro-apps in the context of a given case.

• Creating new cases by the user (e.g. in FrontOffice or BackOffice).

History and events handling

• Recording case history independently of the workflow engine (EximeeBPMS).

• Using events from processes and business 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 act as the user interface for tasks in Case Management.

• Each task can launch an assigned low-code form.

• Shared data context (case ↔ form ↔ process).

Integration with Eximee Model Runtime

• Fetching contextual data of the case and customer.

• Updating data during task execution.

Integration with Eximee Dashboard

• Case Management is one of the key modules of Eximee Dashboard.

• Provides screens for lists of cases, tasks and history.

• Allows embedding micro-applications that support work (e.g. notes, calendar, document list).

Technical characteristics

• Microfrontend architecture with the possibility of extending with additional applications.

• Built-in filtering, sorting and pagination mechanisms.

• Scalability and separation of user contexts.

Example use scenarios

FrontOffice / BackOffice

• The advisor opens the client's case and sees a list of all related tasks.

• Performs subsequent steps of the process (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's task list and prioritizes them.

• Performs group operations, e.g. assigning tasks or changing statuses.

• Analyzes employee workload based on metrics from Case Management.

External partner

• Receives a view of their cases and tasks within the shared partner channel.

• Handles selected stages of the process, e.g. verification of the client's documents.

Common features and deployment parameters

• Configuration flexibility: list, detail and action views defined low-code in the Case Management Designer.

• Reusability: one Case Management component can support multiple applications.

• Security: full control of access to data and operations based on domain roles.

• Customization: ability to tailor layout, filters and actions to the specifics of the deployment.

• Scalability: separating presentation logic from process data enables independent scaling.