Skip to content

Tenant Wizard Modules

Primary frontend module

  • frontend/src/pages/components/config/AddConfigWizard.jsx Owns the full multi-step tenant creation UI, the stepper, local form state, normalization helpers, connection checks, and the final create action.

Embedded helper modules

  • frontend/src/pages/components/config/wizard/WizardHelpPopover.jsx Inline contextual help entry.
  • frontend/src/pages/components/config/wizard/WizardDocumentationModal.jsx Larger chapter-oriented help entry linked into product documentation.
  • frontend/src/pages/components/config/wizard/wizardHelpContent.js Central short-help registry used by the wizard UI.

Backend counterpart

  • backend/src/core/views.py Receives the create request, validates scope and edge references, creates cConfig, then fans nested sections into cConfigExt.

Data touched during create

  • cConfig Root tenant record with company and product assignment.
  • cConfigExt Split persistence for connection, global, jobs.*, and periodic.

Wizard-specific helper responsibilities

Inside the wizard module, several helpers shape the outgoing payload:

  • source normalization for CPI-only vs edge-hybrid setups
  • transport-safe password encoding
  • hot-window defaults for message retrieval
  • field visibility derived from setup mode and auth mode

Why this separation matters

The wizard does not need the full operational data stack yet. It focuses on producing a valid persisted starting point. Message logs, alerts, packages, archives, and keystore records only become relevant after the created tenant is picked up by runtime jobs.