Deployment Status
Compares what runs on the tenant with what exists in design time, and lists only what does not agree. Cloud Integration shows neither side as a list.
What it reports
Section titled “What it reports”- Deployed, but gone from design time. Nobody can change, redeploy or transport these. The page says when the design-time copy disappeared, and gives you its last recorded state as a zip.
- Not deployed. Deployable artifacts that do not run, with who last changed them and when: unfinished work, or a deployment forgotten after a transport.
- Another version. What runs in a different version than design time shows, including artifacts with unsaved changes. Useful before a transport or an audit.
- Not started. Deployed but in error, with the reason Cloud Integration gives, without opening each artifact in the monitor.
The whole report downloads as CSV.
How it works
Section titled “How it works”The report is built from the last artifact sync, so turn on the scheduled sync of the Artifacts tool, or press “Refresh from tenant”. Integration flows, value mappings, message mappings and script collections take part in the comparison.
Good to know
Section titled “Good to know”- For a draft, Cloud Integration does not say whether the deployed copy is the draft or the last saved version. Every deployed draft is therefore listed under “another version”.
- The same version number deployed with other values of its externalised parameters is not a difference here.
- “Not deployed” is a hint: templates and copies kept for reference are listed too.
- “Never seen by the companion” means the design-time copy was already gone at the first sync, so there is no date and nothing to download.
- The report covers one tenant. To compare the content of an artifact on two tenants, use Flow Diff.