Enabling and Disabling the Modeler

CIB seven Modeler can be fully enabled or disabled using a single configuration property. When disabled, no database connection is required and the modeler is hidden from the UI.

Configuration

Set the following property in cibseven-webclient’s application.yaml:

cibseven:
  webclient:
    modeler:
      enabled: false

Or via environment variable:

CIBSEVEN_WEBCLIENT_MODELER_ENABLED=false

What Happens When Disabled

When enabled: false:

• All modeler REST endpoints are removed from the application context
• JPA entities, repositories, and Flyway migrations are not activated
• No database connection is required — DataSource, Hibernate/JPA, and Flyway auto-configurations are excluded automatically
• The modeler card is hidden on the start page
• The modeler menu item is removed from the navigation

No additional frontend configuration is needed — disabling the backend property is sufficient to fully remove the modeler from both the server and the UI.

Frontend Permissions

In addition to the backend property, you can also control modeler visibility through the frontend config.json permissions. This allows hiding the modeler UI while keeping the backend active (e.g., for API-only access):

"permissions": {
  "modeler": {}
}

With an empty permissions object:

• The modeler card is hidden on the start page
• The modeler menu item is removed from the navigation
• Navigating to the /modeler route redirects to the no-permission page
• The backend REST endpoints remain active

Chat Feature (Enterprise Edition)

The real-time chat inside the modeler is controlled by a separate property:

cibseven:
  webclient:
    modeler:
      chat:
        enabled: false

Or via environment variable:

CIBSEVEN_WEBCLIENT_MODELER_CHAT_ENABLED=false

What Happens When Chat Is Disabled

When chat.enabled: false:

• The WebSocket endpoint (/ws/chat) is not registered
• Chat JPA entities and repositories are not activated — the chat_messages table is not required
• The Properties/Chat tab bar is hidden in the modeler UI — the properties panel shows in full single-panel mode

What Happens When Chat Is Enabled

When chat.enabled: true:

• The STOMP WebSocket endpoint and chat REST endpoints become active
• The chat_messages table must exist in the database (created by the SQL schema scripts)
• The modeler UI shows a Properties / Chat tab bar in the properties panel
• The Chat tab is disabled (greyed out with a tooltip) on unsaved diagrams — it becomes active once the diagram is saved

Summary