Packages Architecture

The packages view is the tenant-scoped inventory over CPI packages and their immediate deployment context. It is optimized for fast operational inspection rather than deep artifact editing.

Related pages

• Modules
• Flows
• Operations
• Artifacts
• Tenant Settings

Functional role

The packages popup answers questions such as:

• which packages exist in this tenant
• how many iFlows belong to each package
• which package items are deployed or not deployed
• how labels and package grouping currently look from the monitoring perspective

Runtime boundary

The packages view is opened inside ConfigOverview.jsx and rendered through ConfigPackage.jsx. It reads backend-prepared package rows, then performs search, sorting, and some grouping locally in the frontend.

Primary APIs

• GET /api/cpi/configPackagesGet/<configId>/?include_names=true
• GET /api/core/tag/
• PATCH /api/cpi/package/config/<configId>/<rowId>/

Design consequence

Package review is intentionally lightweight. There is no separate full page or complex action matrix. The popup is designed to support quick operational context and label maintenance.

When package-level findings are not specific enough, the next diagnostic layer is usually Artifacts.