01 / The thing under test
ServiceNow Flow Designer, diagram view
Shipped in San Diego (2022) as a separately installed Store app, now folded into Workflow Studio. It is a toggle beside the flow description list, not the surface flows are authored on.
What it actually is
A rendered projection of an ordered, block-structured step list. Nodes carry a sequence number rather than a coordinate. Nothing in the documentation mentions moving, aligning, resizing or laying out a node, because there is no geometry to move.
It is editable: plus icons insert a component along a path, and a properties panel configures the selected node. But it supports an allow-list of flow logic and triggers, and Workflow Studio disables the view entirely when a flow contains anything outside it. An Error Handler is enough to grey out the toggle.
The run view is a different screen. Flow execution details lives on the Operations tab and renders as an expandable list, and reporting is off by default in production. Asked whether the diagram appears when you open a flow context, the community answer is that it does not: the diagram is for developers, at design time only.
02 / The field
Ten canvases, three families
The single most predictive question is whether a node has coordinates. It decides whether branches can be drawn to rejoin, whether a loop can be a visible back-edge, and whether the picture is the model or a report about the model.
Camunda
Web Modeler / bpmn-js
The reference implementation. One BPMN file with layout baked in, edited here, executed by the engine, re-rendered live in Operate, heat-mapped in Optimize.
- Canvas model
- Free placement, coordinates persisted as BPMN DI inside the XML. Align, distribute, grid snapping and bendpoints are default modules, not plugins.
- Branch and merge
- Full gateway set. Merging is a converging gateway you draw. Back-edges and arbitrary re-entry are legal.
- Sub-processes
- Drill into a collapsed sub-process, breadcrumb back out.
- Run data
- Operate overlays live instance counts and incident markers on the same geometry. Optimize paints frequency and duration heatmaps on it. Play executes the model against a real cluster from inside the modeller.
- Navigation
- Minimap, fullscreen, reset viewport, canvas search, keyboard-driven modelling, and an attention point that works as a laser pointer in your avatar colour.
- Collaboration
- Threaded comments anchored to an element with an always-visible blue overlay, at-mentions, email notification. Real-time co-editing was replaced by a canvas lock with takeover in 8.9, April 2026.
Only here
- The diagram is the executable artefact in an open standard. No export step, no proprietary intermediate, and since 8.9 you can copy BPMN elements to the clipboard and paste them into a different vendor's editor.
- Version diff rendered on the geometry: an added element is highlighted green with a plus symbol, alongside a changes list and an XML view.
- Element templates. A configured task becomes a versioned, shareable node type other modellers instantiate, authored from the properties panel.
GapEverything above rests on the diagram being the source of truth. ServiceNow's is a rendering of a list that can be switched off by its own contents.
UiPath
Maestro BPMN / Studio
Four canvas paradigms under one roof, and the only vendor that paints aggregate run statistics onto the design surface.
- Canvas model
- Maestro BPMN and Studio Flowchart are free graphs. Studio Sequence is a nested container. State Machine is free-placement states with labelled transitions. Maestro Flow is a node-and-edge graph backed by a TypeScript file.
- Branch and merge
- Exclusive, parallel and inclusive gateways used for both splitting and merging. Boundary events attach to a task's edge. Multi-instance markers render on the shape itself.
- Node anatomy
- Studio Web offers an explicit toggle between canvas view, where key properties render on the card, and panel view, where the card collapses and everything moves to the side.
- Run data
- The instance diagram colours each node green, blue or red, counts instances per step, gives average, min, max, P95 and P99 on hover, and lays a duration heatmap over the model from blue to red.
- Navigation
- Minimap, tidy up nodes, organise connections, validation panel counting errors against warnings, screenshot export, BPMN import and download.
- Debugging
- A real IDE debugger on a diagram: breakpoints, step into, over and out, run to this activity, slow step, execution trail and activity coverage.
Only here
- The model you sign off is the dashboard you monitor. Aggregate percentile durations and a heatmap sit on the authored diagram, then feed Process Mining.
- One artefact, three editors. A Maestro Flow is a single TypeScript file edited identically by the canvas, a VS Code extension and a coding agent, with no import step.
- Autopilot streams generated BPMN elements onto the canvas incrementally, so you can watch the structure form and correct it early, and it accepts a photographed flowchart as input.
GapServiceNow shows no execution data on the diagram at all. Not a status colour, not a count, not an error marker.
Appian
Process Modeler
The most drawing-tool-like canvas in the field, and the only one where a running production instance opens in the editor you built it in.
- Canvas model
- Free placement with a toggleable grid and snap, arrow-key nudging, and Ctrl plus arrow for sub-grid adjustment. Two connector styles, angled or straight. No auto-layout at all: layout is the modeller's job.
- Branch and merge
- BPMN gateways with a decision tab. Merging is an edge you draw into a join. Loops are ordinary back-edges.
- Node anatomy
- Enhanced view renders assignment markers on activity boundaries, including the assignee's profile photo. Exception and timer events render as boundary markers on the shape. Configuration opens in a modal, which is the dated part.
- Run data
- The instance list opens each process in a Monitor Process tab in the modeller, with live reload and an activity exceptions dialog. Node metrics overlay aggregate task completion across every process ever started from the model.
- Navigation
- Horizontal and vertical swimlanes, free-floating annotations with a font palette, print preview, generated documentation, and cut and paste of nodes across modeller tabs with variable mappings intact.
- Roles
- Analyst view and designer view of the same artefact. An analyst drafts the flowchart with configuration deliberately restricted; a developer switches views to attach data, forms and rules, and to publish.
Only here
- Swimlanes, in both orientations, on a free-placement canvas. Nobody else in this review ships a lane construct.
- In-flight modification: an authorised user can edit a running instance's diagram, change its variables and stop or pause it, from the same canvas.
- Drag a design object from the search bar onto the canvas and get the correct node pre-wired. An interface becomes a user input task with its forms tab already pointed at it.
GapTwo-role authoring. ServiceNow's diagram is developer-only, which the community has asked to change since at least 2024.
n8n
Workflow canvas
A genuine DAG with two connection layers, item counts printed on the wires, and a version diff that renders two canvases side by side.
- Canvas model
- Free placement on a 20px grid, built on Vue Flow. Tidy up is an opt-in auto-layout in the canvas controls and the command bar.
- Branch and merge
- Any node accepts multiple incoming edges and the Merge node takes N inputs, so branches rejoin freely. The Loop Over Items node wires its loop output backwards, making iteration a drawn cycle.
- Node anatomy
- Icon, name, optional subtitle, status badge and pinned-data summary. Configuration opens a full-screen three-pane view of input, parameters and output, with a docked focus panel now in preview.
- Run data
- Item counts render on the connections themselves. Pin a node's output and re-run only its descendants. Debug in editor loads a past execution back onto the live canvas with the first node's data pinned.
- Navigation
- Command bar on Cmd-K, marquee and directional multi-select, sticky notes with markdown, images and embeds, and canvas groups that collapse a connected chain behind one labelled block.
- Collaboration
- Presence pills, no cursors. Autosave to a draft that does not go live, versioned publishing, workflow-level conflict detection.
Only here
- Two-axis topology. The main data flow runs horizontally; an AI agent's brain, memory and tools hang vertically beneath it on a separate connection class the canvas manages as its own layer.
- Side-by-side canvas version diff, shipped 2.13.0 in March 2026: pick two versions and both render as canvases with the changed nodes highlighted.
- Quantity on the edges. You can read how many items travelled each wire, which turns a topology question into a data question.
GapLoops. ServiceNow draws For Each and Do Until as nested structure, never as an arrow that points back.
Make
Scenario builder
Conditions live on the edges rather than the nodes, and every module wears the number of bundles that passed through it.
- Canvas model
- Free placement of an implicitly ordered chain. Links auto-route as you drag. Auto-align relays the whole scenario and is all or nothing, which users report as destructive to hand-made layouts.
- Branch and merge
- Routers split and cannot be rejoined. If-else plus Merge, shipped March 2026 with nesting in May, splits and reconnects into a single flow. You create the join by dragging the merge icon onto each route.
- Node anatomy
- A circle with the app icon, an execution-order badge and a label beneath. Filters sit on the link between two modules as a labelled funnel, so routing logic reads off the edges.
- Run data
- Operation bubbles appear above each module after a run; click one to inspect the exact input and output bundles. Run replay and named runs went generally available in October 2025.
- Navigation
- Notes anchored to a module or a route, with a panel listing every note in the scenario. Device auto-detection, and a setting that swaps which mouse button pans and which marquee-selects.
- AI
- Maia sits as a chat panel on the left of the builder and creates or modifies scenarios. Agents are first-class modules in the same canvas, with a reasoning panel showing tool calls, counts and cost.
Only here
- Conditions attached to connections rather than nodes. You read the routing by following the wires, not by opening the branch.
- Data volume as a first-class visual. Bundle counts on the flow show you where the payload expanded and where it collapsed.
- Configurable pan and select button mapping with input-device detection, which is a rare thing to let a user change.
GapAnything on the connector. ServiceNow's condition lives inside the If node; the line between two nodes carries no information beyond direction.
Zapier
Canvas plus Zap editor
Two surfaces that do not overlap. A free-placement planning canvas with real multiplayer, and an execution editor whose branches never rejoin.
- Canvas model
- Canvas is a whiteboard: drag a step anywhere, hover to reveal connection dots on each side, drag dot to dot to make an edge. The Zap editor is a computed vertical outline where a step can only move to another sequential position.
- Branch and merge
- Paths render side by side, up to five, nested three deep, and collapse individually or all at once. They never rejoin. There is no merge step in Zapier.
- Node anatomy
- App icon, step number, event description, status icon. Configuration is a right sidebar with setup, configure and test tabs. Canvas steps additionally take colour, tags, links and notes.
- Run data
- Zap history renders a past run as three panes: run cards, the step outline with per-step status, and the selected step's data in, data out, AI troubleshoot and raw HTTP logs. A replay counter on the run card records re-execution attempts.
- Collaboration
- The strongest in the field, and Canvas-only. Liveblocks-backed real-time multiplayer editing, comment threads on individual steps, at-mentions of users and teams.
- AI
- Copilot proposes an entire cross-product system from one prompt, Zaps plus Tables plus Interfaces plus Chatbots plus Agents, with a preview before it builds.
Only here
- A planning canvas that stays coupled to the running automations. Drag a real Zap onto it and toggle Show steps to expand it into its internals, beside manual human steps no automation could execute.
- Comment threads and at-mentions anchored to a node, with live multiplayer cursors, in a mainstream automation product.
- Per-step forensics after the fact: data in, data out, an AI troubleshoot tab and seven days of raw HTTP logs.
GapAny collaboration at all. ServiceNow's model is optimistic locking with a modal telling you the flow has been modified since you opened it.
Salesforce Flow Builder
Auto-layout
The best argument that a computed tree is not a handicap. Branches re-converge automatically, and a named jump connector handles what a tree cannot express.
- Canvas model
- Auto-layout is the default and the only mode for Flow Orchestration. Free-form still exists, gets no new features, and every canvas improvement since 2025 is auto-layout only.
- Branch and merge
- A Decision fans into labelled outcome columns that automatically re-converge further down. End a branch with an explicit End if you do not want it to rejoin. Go To connectors let a branch jump to any element, drawn as a labelled reference so the tree stays planar.
- Loops
- The Loop element renders a For Each body and an After Last exit path, so iteration is a real drawn path rather than a container box.
- Run data
- Debug is a left panel beside a live canvas, not a modal. Results render as per-element cards with summaries, each carrying a View on Canvas action that jumps the canvas to that element. Debug inputs persist across the session, and rollback mode debugs record-triggered flows without committing.
- Navigation
- No minimap. Sticky zoom, single-click to open an element, a select-elements mode for multi-select, and a keyboard shortcut menu on Cmd-slash. Decisions, loops, waits and fault paths collapse; named collapsible groups arrive in Winter 27.
- Version diff
- Native Compare Flow Versions, plus an edit history panel with chronological change tracking and restore.
Only here
- Automatic re-convergence with a jump connector as the escape hatch. You get a tree's readability and still express the graph a tree cannot.
- Debugging wired to the canvas by a per-result View on Canvas action, in a split pane rather than a separate run-history page.
- An AI-driven Decision element whose outbound path is chosen at runtime by a model reading instructions instead of conditions. Nobody else ships a node whose branching semantics are evaluated by an LLM.
GapThe closest available blueprint. Salesforce proves a computed layout can still offer a jump primitive, canvas-linked debugging and named collapsible groups.
Microsoft Power Automate
Cloud flows, new designer
Compact cards, a minimap and on-canvas operation search make long flows navigable. The join between two branches is invisible, because it lives in a settings tab.
- Canvas model
- Auto-laid-out vertical tree. There are no coordinates in the flow definition. Dragging the flow pans the viewport; dragging an action shows blue dashed drop zones between cards.
- Branch and merge
- Condition, Switch, Apply to each and Do until are nesting containers rather than graph edges. Parallel branches sit side by side. There is no merge node: you rejoin by opening the downstream action's settings and configuring Run After.
- Node anatomy
- Compact chips. Classic cards showed configuration in situ; the new designer moved it into a left pane with parameters, settings, code view and testing tabs. A note symbol appears in a card's lower right when one is attached.
- Run data
- A test run puts a green check and an elapsed time on each card. Run history is a separate diagram with per-step error icons and raw JSON. Resubmit replays a failed run with the same input.
- Navigation
- Expand and collapse all, zoom, fit view, minimap and operation search in a bottom-left cluster, visible only when the configuration pane is closed.
- Known weakness
- Microsoft documents it: the new designer struggles visually with deeply nested structures, and branches can overlap or become hard to navigate past depth three.
Only here
- Pin one configuration pane so a second opens beside it, to compare two actions or copy values between them.
- Per-action static results. Flip a toggle and an action returns a chosen success or failure without calling the service, so you can exercise a branch you cannot otherwise reach.
- Code view on every node: the selected card's live JSON in the same pane as its form.
GapBoth tools hide the join, but Power Automate at least gives you a minimap and a node search to find your way. ServiceNow has those two; it lacks the mocking and the code view.
Tray.ai
Workflow builder
An auto-arranged step tree on a properly pannable canvas, with the best per-step testing story in the review and a genuinely novel data-dependency overlay.
- Canvas model
- Steps are sequenced automatically into a column, but the column sits on a real canvas: zoom on Cmd-scroll, pan on space-drag. You drop into a sequence position, not onto a coordinate.
- Branch and merge
- Boolean gives a true and false fork. Branch is a switch generator with named paths, and the docs are emphatic that it is not parallel processing. Children nest under the branch; there is no rejoin edge.
- Node anatomy
- Connector icon, step name, operation. Everything else is in the right panel, including an output schema preview.
- Run data
- A logs drawer on Shift-D with run, step list and per-step input and output records. Shift-click a log entry to jump to that step in the builder. Replay a whole run or a single step.
- Navigation
- A plus on the canvas opens connector discovery. Drag-select several steps and save them as a named snippet you can re-drop from the sidebar. No minimap.
- Collaboration
- None on the canvas. Governance is workspace separation with approval gates, and diffing is outsourced to Git via the Sync CLI shipped in August 2026.
Only here
- Step dependency highlighting. Select a step and the canvas colours which other steps consume its output, which share its storage key, and which loop it pairs with. Almost nobody visualises data edges on top of control edges.
- Run a single step in isolation, billed as one task, without executing the workflow around it.
- Snippets: a multi-step drag selection becomes a named, searchable, re-droppable object, which is grouping as reuse rather than grouping as decoration.
GapTesting granularity. ServiceNow tests a flow, not a step, and its execution details are off by default in production.
Workato
Recipe editor
A single vertical, auto-numbered step list with nested logic blocks. As of August 2026 there is still no node-and-edge canvas, and the changelog shows no sign of one.
- Canvas model
- None. A numbered vertical list, reordered by drag and drop. No placement, no zoom, no minimap, no frames, no annotations.
- Branch and merge
- IF, ELSE IF and ELSE render as nested indented blocks. Branches always implicitly rejoin, because a branch cannot skip ahead to an arbitrary later step.
- Node anatomy
- Configuration is inline and expands in place, so an expanded step can be hundreds of pixels tall. Inputs are filled by dragging datapills from a right-hand tree.
- Run data
- Strong, precisely because the diagram is a list. Job details replay the executed path over the same step tree, labelling unexecuted conditional children Condition not met. Any job can be rerun against the latest recipe.
- Sub-workflows
- A recipe function is one ordinary step. You navigate away to see the child.
- AI
- Recipe Copilot emits a sketch outline first, refinable by follow-up prompts, and only materialises real configured steps once you confirm connections. Each is marked Pending review.
Only here
- Structural visual diff that names reparenting and reordering as change types. Added is green, deleted is red, and blue tags mark moved, nested, unnested, skipped and config-updated, drillable to individual field mappings.
- The sketch-then-materialise AI flow. The generated thing is reviewable and non-executable until you approve it, rather than a live half-broken flow.
- Skip step: non-destructive disabling that survives in job history and appears in the diff as a tagged change.
GapServiceNow's flow history compare highlights a step list too, so this is parity. The difference is that Workato has no diagram to be inconsistent with.
03 / At a glance
Capability matrix
Read the ServiceNow row against the columns where it stands alone. The one column it already wins is the minimap, which four of the ten do not ship.
| Tool | Free node placement |
Branches rejoin |
Loops as back-edges |
Sub-flow opens in place |
Run data on the canvas |
Minimap | Canvas annotations |
Grouping or lanes |
Comments on a node |
Diff on the diagram |
Prompt to nodes |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ServiceNow | ○ | ◑ | ○ | ○ | ○ | ● | ◑ | ○ | ○ | ◑ | ● |
| Camunda | ● | ● | ● | ● | ● | ● | ● | ● | ● | ● | ● |
| UiPath | ● | ● | ● | ● | ● | ● | ● | ● | ○ | ◑ | ● |
| Appian | ● | ● | ● | ◑ | ● | ○ | ● | ● | ○ | ● | ○ |
| n8n | ● | ● | ● | ○ | ● | ◑ | ● | ● | ○ | ● | ● |
| Make | ● | ● | ○ | ○ | ● | ○ | ● | ○ | ○ | ○ | ● |
| Zapier | ◑ | ○ | ○ | ◑ | ◑ | ○ | ● | ● | ● | ○ | ● |
| Salesforce | ◑ | ● | ● | ○ | ● | ○ | ○ | ◑ | ○ | ● | ● |
| Power Automate | ○ | ○ | ○ | ○ | ◑ | ● | ◑ | ◑ | ○ | ○ | ● |
| Tray.ai | ○ | ◑ | ○ | ○ | ◑ | ○ | ○ | ◑ | ○ | ○ | ◑ |
| Workato | ○ | ◑ | ○ | ○ | ● | ○ | ○ | ○ | ○ | ◑ | ● |
04 / The answer to the question
What the diagram view does not have
Ranked by how much of the canvas experience each one blocks, not by implementation cost. The first four are structural; the rest are additive.
The diagram is a view, not the modelStructural
It is an optional Store install, a toggle beside the flow description list, and it supports an allow-list of components. Workflow Studio disables it outright when a flow contains anything outside that list, and there is a standing known error for it failing to open. A surface that can be switched off by its own contents cannot become the place people work.
Who does itCamunda and UiPath both make the diagram the artefact: the file you draw is the file that deploys, in an open notation.
No execution data anywhere on the diagramStructural
Flow execution details is a separate list on the Operations tab, with expandable rows. There is no status colour, no per-node count, no error marker on the canvas, and asked directly whether the diagram appears for a running flow, ServiceNow's own community answers that it does not.
Who does itAppian opens a live instance as a Monitor tab in the modeller and lets you edit it in flight. UiPath paints P50, P95 and a duration heatmap on the authored BPMN. Salesforce docks debug beside the canvas with a View on Canvas jump on every result. n8n loads a past execution back onto the live canvas.
No node placement, and no auto-layout to argue withStructural
Nodes carry a sequence number, not a coordinate. Nothing can be dragged, aligned, distributed or nudged, and there is no tidy-up command because there is nothing to tidy. On a flow of any size the reader gets whatever the renderer produces.
Who does itSix of the ten. Appian goes furthest with grid, snap, arrow-key nudging and sub-grid adjustment on Ctrl plus arrow.
No topology beyond a block-structured treeStructural
There is no back-edge, no jump between branches and no merge you can draw. Exit Loop and Skip Iteration exist precisely because arbitrary edges do not. The diagram cannot show a shape the model cannot hold, so this is a modelling limit that happens to surface as a drawing limit.
Who does itSalesforce is the cheap version: a Go To connector that jumps to any element and renders as a labelled reference rather than a crossing line, keeping the tree planar. UiPath and Camunda are the full version with converging gateways.
Subflows are opaqueAdditive
A subflow is a single node you configure. There is no drill-in, no breadcrumb, no inline expansion. The one expand-a-subflow feature ServiceNow ships, showing subflow stages in a parent flow, is scoped to execution details rather than the diagram.
Who does itCamunda drills into a collapsed sub-process and breadcrumbs back. Appian previews the child model in place and opens it in its own canvas tab. Zapier expands a whole Zap into its steps with one toggle.
No collaboration on the canvasAdditive
No presence, no avatars, no comment threads, no at-mentions. The concurrency model is optimistic locking with a modal saying the flow has been modified since you opened it. ServiceNow's own Workflow Automation CoE answer is that most customers rarely have two developers in the same flow, and suggests Git.
Who does itZapier Canvas has real multiplayer with threads and at-mentions on a step. Camunda anchors threaded discussions to a BPMN element with a permanent blue overlay so you can see which nodes are under discussion.
Version diff is a step list, not the diagramAdditive
Flow history compare gives a competent side-by-side with blue for changed, red for removed and green for added. It highlights steps. Having built a diagram view, the change is invisible on it.
Who does itCamunda highlights the added element on the geometry with a plus symbol. n8n renders both versions as two canvases side by side. Appian and Salesforce both diff natively.
Annotations are node metadata, not canvas objectsAdditive
Per-node annotation text renders in italics beneath the node, toggled by a view option. That is a caption, not a place to explain a decision, group a region or leave a note for the next person.
Who does itn8n sticky notes take markdown, images and video embeds, resize, take seven preset colours, and are routinely dragged behind nodes as visual grouping. Appian gives free text boxes with a font palette. Make anchors notes to a route as well as a module.
No grouping, no lanes, no collapseAdditive
A long flow cannot be chunked into named regions, and nothing collapses. Combined with the absence of placement, this is why the diagram stops paying for itself as flows grow.
Who does itn8n canvas groups collapse a connected chain behind one labelled block with a description. Appian has horizontal and vertical swimlanes. Salesforce collapses decisions, loops, waits and fault paths, and adds named groups in Winter 27.
Export is a degraded PNGAdditive
PNG only, split into multiple files when the flow is too large for one, and stripped of configuration detail. A 2022 community request for a graphical export was answered with screenshot workarounds, and four years later the answer has not changed. This is the single most requested thing in the threads.
Who does itCamunda downloads BPMN XML or SVG. UiPath exports a screenshot and a .bpmn file. Zapier exports a Zap as an image for people without an account.
No keyboard modelling, on flows specificallyAdditive
ServiceNow publishes a keyboard navigation page for the playbook diagram view: arrow keys between nodes, Enter to edit, plus on a connector to insert. There is no equivalent page for flows. The asymmetry inside one product is itself the finding.
Who does itCamunda moves a selection with arrow keys, faster with Shift, and pans with Ctrl plus arrow. n8n has a full shortcut table and a Cmd-K command bar.
AI arrives on the diagram, then leaves itAdditive
This is the one place the diagram is the primary surface, and it works: Now Assist previews a generated flow in the diagramming view with the prompt shown as an annotation under each node, and Zurich added next-step recommendations while you are in that view. But previews are not saved, discarding loses everything, and unmatched requests become placeholder nodes with nothing offered to resolve them.
Who does itWorkato's Copilot emits a reviewable sketch and only materialises steps once connections are confirmed, marking each Pending review. UiPath streams elements onto the canvas as they generate so you can correct the structure early.
05 / Provenance
Method and sources
Ten tools were selected for market presence combined with a genuine visual flow-configuration surface. Two screenshots are live captures of public no-login modellers, Camunda's bpmn-js demo and UiPath's Maestro sandbox, one is the live canvas the n8n home page renders, and the rest are captured from vendor documentation and product pages. Claims are taken from vendor documentation, release notes and changelogs current to August 2026, with community threads used only where they contradict or qualify the documentation.
Two caveats worth carrying. Some ServiceNow behaviours are inferred rather than documented, specifically the absence of node placement, multi-select and keyboard modelling, which rest on the absence of any documentation for them rather than on an explicit statement. And Reddit was not reachable from the research environment, so the community evidence here is drawn from ServiceNow's own forums and idea portal.
- ServiceNow Flow diagramming view, Flow execution details, Create a flow with Now Assist
- ServiceNow community: Flow Diagrammer, allow view to all users, Export flow visually to PDF, Diagram flow not displaying anything
- Camunda Web Modeler and 8.9 release notes; demo.bpmn.io
- UiPath Instance diagram view, Autopilot for Maestro; bpmn.uipath.com
- Appian Process Model Object 26.7 and AI-augmented process development
- n8n 2.x release notes, canvas groups, debug executions
- Make If-else and Merge, unified canvas navigation, Maia
- Zapier Create a canvas, Zap run details, Liveblocks case study
- Salesforce auto-layout, compare flow versions, Winter 26 debug panel
- Microsoft cloud flows designer, classic versus modern designer, drafts and versioning
- Tray.ai step dependencies, debug logs
- Workato recipe diff, Recipe Copilot, jobs