Skip to content

Tenant Wizard Flows

Create flow

sequenceDiagram
    participant U as User
    participant W as Wizard
    participant API as Core API
    participant DB as Config tables
    U->>W: Fill steps and review
    W->>W: Normalize source map, defaults, and passwords
    W->>API: POST /api/core/config/
    API->>DB: Create cConfig and cConfigExt rows
    API-->>W: Return id

Edge-hybrid validation flow

sequenceDiagram
    participant W as Wizard
    participant API as Core API
    participant DB as Existing configs
    W->>API: Submit edge_hybrid tenant
    API->>DB: Check referenced parent config
    API->>DB: Reject edge_hybrid parent
    API-->>W: Accept or return validation error

This guard is important because an Edge tenant must point to an existing CPI tenant and must not form a recursive hybrid chain.

Connection test flow

At wizard time, users can validate connectivity before the tenant is persisted fully. That makes the wizard both a creation UI and a first integration checkpoint.

Post-create follow-up

After a tenant is created successfully:

  • the main config snapshot exists
  • worker loops can pick up the tenant
  • later settings screens can refine intervals and connectivity
  • monitoring views can start returning data once worker sync has populated runtime tables