Cabinee Integration Platform

Maven artifacts and repository modules still use historical unibpm-* names. That is the code identity; the product name is Cabinee.

Purpose

Cabinee Integration Platform is a dedicated service layer for external integrations and entry points into Cabinee.

The platform is used to:

receive data from external sources (landings, forms, third-party services);
integrate with external systems (CRM, electronic document management, logistics, ERP);
transform and route data into Cabinee and the process engine;
call the Cabinee REST API from service tasks.

The Integration Platform is isolated from the main Cabinee application and evolves independently.

unibpm-integration-runtime Base runtime service (Spring Boot) that hosts integration modules.
unibpm-api-client Client library (Spring Cloud / Feign) for the Cabinee REST API, including DTOs.
unibpm-integration-feedback Feedback form integration.
unibpm-integration-inbound Inbound connector that creates tickets from external systems.
unibpm-external-task-starter Handler for process-engine Service Tasks. Jobs arrive as Camunda 8 jobs and are delivered to connectors via Kafka.
unibpm-integration-onec-odata 1C Enterprise oData connector.
unibpm-integration-keycloak Keycloak connector.
unibpm-integration-unibpm Cabinee connector for internal platform actions.
unibpm-integration-ai AI connector.

Modularity Each integration is implemented as a separate module.
Isolation The Integration Platform does not contain Cabinee business logic.
Stateless All public APIs are stateless.
Explicit security Only /public/** is allowed without authentication. All other endpoints are closed.

The user submits a form on a landing page.
The request arrives at /public/feedback.
The service performs:
- payload validation,
- SmartCaptcha verification,
- form configuration checks.
A ticket is created in Cabinee via the Cabinee API.
The result is returned to the client.