Artifacts Architecture

Artifacts are the deeper runtime and design inventory underneath package-level review. The artifact popup combines metadata, history, tags, previews, and where-used context in one tenant-scoped inspection surface.

Related pages

• Modules
• Flows
• Operations
• Packages
• Alerting

Functional role

The artifact view supports questions such as:

• which artifacts exist for the tenant
• whether they are deployed or only present on the design side
• how tags and metadata currently look
• where an artifact is used
• how versions changed over time

Main APIs

• GET /api/cpi/configArtifactsGet/<configId>/
• POST /api/cpi/iflow/config/<configId>/<item.id>/content_check/
• GET /api/cpi/iflow/config/<configId>/<item.id>/download/
• GET /api/cpi/iflow/config/<configId>/<item.id>/download_svg/
• PUT /api/cpi/configs/<configId>/iflows/<item.id>/tags/

Scope model

The UI exposes All, Runtime, and Design scopes over the same underlying inventory:

• Runtime emphasizes deployed artifacts
• Design emphasizes undeployed or design-oriented artifacts
• All keeps the complete inventory visible