Using Packages in Daily Work
Typical use of the package view
The package view is best for orientation and narrowing down scope before looking deeper elsewhere.
Typical activities:
- search for a package
- filter by label
- open details
- compare contained iFlows
- decide whether the next step belongs in Artifacts
Recommended working pattern
- search or filter the package list
- open the package details
- review version, owner, and contained flows
- switch to Artifacts if flow-level analysis is needed
This keeps the package view focused on overview rather than overloading it with deep diagnostics.
When to use labels
Labels are especially useful when:
- many packages exist in one tenant
- teams need a shared grouping scheme
- productive and non-productive packages should be distinguished quickly
Useful day-to-day cases
Quick validation after sync
Check whether an expected package appears and whether the iFlow count looks plausible.
Governance review
Use labels and package ownership hints to identify packages that still need classification.
Preparation for deeper analysis
Open the package first, then continue with Artifacts if a specific iFlow or deployment state must be checked.
Common mistakes
- trying to do all technical analysis inside the package list
- skipping labels although the list keeps growing
- comparing packages without also checking contained artifacts where needed