Packages

The Packages area shows the packages of one configuration in a searchable popup view.

It matters because it makes visible:

• which packages were loaded for a configuration
• how many iFlows a package contains
• which labels or tags are maintained
• which technical details are available in the expanded detail block

In the current UI, packages act as the grouping layer around contained artifacts. Deeper analysis of individual iFlows still happens in the Artifacts area.

As in the other large modules, there are two help levels:

1. small inline help at important columns and detail fields
2. full documentation through the Book icon in the packages header

Structure

• Package fields, details, and labels
• Using packages in daily work
• Reference for package counts, labels, and grouping context
• Troubleshooting common package inventory issues

Need the technical deep dive?

For sync boundaries, storage, and the relation to artifact inventory, continue with:

• System Documentation: Packages