Packages Reference
This page is the short working reference for people who review CPI packages in the product.
What the packages view helps you answer
- Which packages are known for this configuration?
- How many iFlows belong to each package?
- Which package looks incomplete or unexpectedly empty?
- Which labels help group or identify the package?
Package view matrix
| Area | What it shows | What users usually do next |
|---|---|---|
| Package list | all stored packages for the current configuration | search, sort, or open a row |
| Detail block | package metadata and deployment context | inspect names, counts, and labels |
| Labels or tags | operational grouping and classification | adjust labels or compare related packages |
| Artifact count | how many iFlows belong to the package | jump into Artifacts for deeper analysis |
Practical value guide
| Signal | What it usually means |
|---|---|
| package has many artifacts | the package is a broad integration bundle |
| package has zero or very few artifacts | data may still be syncing or the package is limited in scope |
| labels are present | someone classified the package for operations |
| package exists but expected artifact is missing | continue in Artifacts or review sync timing |
Typical daily actions
| Goal | Fastest product action |
|---|---|
| find one package | search by package name |
| review grouped integrations | inspect labels and artifact count |
| check whether a package looks complete | compare expected and visible artifact count |
| continue into technical detail | open the related artifact inventory |
Quick operator checks
- Is the package present at all for the current tenant?
- Does the artifact count roughly match expectation?
- Are the maintained labels still useful and correct?
- Is the real question package-level, or already artifact-level?
Need the deep technical view?
See: