How to read the Analyze screen
The Analyze screen is meant to answer two things quickly: what kind of workflow you are looking at, and how safe the current conversion path is. If you can read that screen well, you can usually decide whether a workflow is ready for export or needs another review pass.
Start with the summary, then read the exceptions
The headline counts tell you how much of the workflow currently falls into supported, partial, and unsupported buckets. Use those numbers as a triage signal, then focus on the smaller set of exceptions rather than reading every supported step line by line.
For many workflows, the first useful question is not whether the product can export something. It is whether the uncovered or best-effort items are concentrated in one pattern, such as approvals, document generation, or external queries.
- Supported means the tool has a defined conversion path for that step type.
- Partial means the step has a recognized pattern but still needs review, a strategy choice, or a narrower mapping.
- Unsupported means there is no trustworthy path yet and you should expect manual work.
Why the trigger is shown first
The trigger is shown as the first row because that is how most users mentally walk a workflow: trigger first, then actions in execution order. Earlier designs separated trigger metadata from the action list, but that made the page look like it started at step two.
Seeing the trigger first also helps when you are validating whether the workflow shape is item-based, file-based, manual, scheduled, or something else entirely.
Read labels as routing hints, not marketing labels
The connector or pattern label on each row is there to tell you which conversion family the step belongs to. For example, a row labeled DB2 or HTTP is not just a visual tag. It is a clue about the export path, connector requirements, and whether premium licensing or manual review may still matter.
If a row note says best effort, take that literally. It usually means the shape is covered, but the final imported action should still be reviewed against your tenant, connection references, or template details.
- Use row notes to find the real blockers before export.
- Look for repeated partial patterns. Repetition often means one missing mapping slice, not many unrelated problems.
- Treat the step list as a validation surface, not just a pretty preview.