Skip to content

Artifacts Reference

This page is the short working reference for people who inspect iFlows and related artifacts in the product.

What the artifacts view helps you answer

  • Is the expected iFlow present for this tenant?
  • Which package, version, and deployment context belong to it?
  • Does metadata or where-used information explain the current issue?
  • Do hash or detail values suggest a change worth reviewing?

Artifact detail matrix

Area What it shows What users usually do next
Artifact list known iFlows and artifacts for the tenant search or filter by name and state
Expanded row package, metadata, hashes, and detail fields compare the visible technical context
Where-used or related details dependency hints for the artifact estimate impact before a change
Version and hash information change indicators between artifact revisions verify whether the right build is active

Practical value guide

Signal What it usually means
artifact is present and deployed the tenant knows the iFlow in active runtime context
expected artifact is missing sync is incomplete or the deployment does not exist as expected
metadata hash differs from content hash technical details changed and should be reviewed
where-used information is populated the artifact is part of a wider dependency chain

Typical daily actions

Goal Fastest product action
confirm one iFlow exists search by artifact or iFlow name
review whether a change reached the tenant inspect version, deploy state, and hash values
estimate technical impact open metadata and where-used details
move one layer higher return to Packages for grouping context

Quick operator checks

  • Are you looking at the right tenant and artifact name?
  • Is the question about deployment state, version, or dependency?
  • Do the visible details explain the incident already?
  • If not, do you need runtime message evidence from Message Popups or Alerts?

Need the deep technical view?

See: