Database Schema

When the modeler is enabled (cibseven.webclient.modeler.enabled: true), the webclient requires a database schema to store diagrams, forms, and user sessions. The required tables must be created before startup. The webclient can connect to and use the database, but it does not create, update, or validate the schema itself (ddl-auto: none).

When the modeler is disabled (cibseven.webclient.modeler.enabled: false), all modeler-related persistence components are disabled. No datasource configuration or database connection is required at all, as JPA is not initialized.

Schema creation is the responsibility of the parent application (e.g. cibseven-bpm-run). Refer to the parent application’s documentation for the DDL scripts and migration tooling it provides.

Database Tables

Table	Description
mod_processes_diagrams	Stores BPMN and DMN diagram metadata and the raw XML
mod_forms	Stores form schemas as JSON
mod_user_sessions	Tracks open editing sessions per user
mod_diagram_usage	Associates a user session with a specific diagram
mod_form_usage	Associates a user session with a specific form
mod_element_templates	Stores reusable element template definitions
chat_messages	Stores real-time chat messages per room. Deleted messages are soft-deleted (content cleared, row retained as a tombstone). Enterprise Edition only.
chat_presence	Tracks active users per chat room for the long-polling transport. Each row is a heartbeat record refreshed on every poll; stale entries are purged automatically. Enterprise Edition only.

Supported Databases

Refer to Prerequisites for supported database versions.