Flows

Use Orchestration > Flows to inspect, compare, copy, migrate, edit, back up, and manage DaVinci flows.

Flows are the main entry point for FlightIQ Director, Flow Inspector, Flow Versions, ReplaceIQ, and NodeIQ Connect.

Common Uses

  • Compare source and destination flows.
  • Copy flows to another environment or repository target.
  • Open FlightIQ Director for guided migration.
  • Inspect parent and subflow relationships.
  • Review and manage flow versions.
  • Set flow log levels.
  • Apply naming and versioning tools.
  • Perform selected bulk actions.

Basic Workflow

  1. Select an Org Root.
  2. Select a source environment.
  3. Select a destination environment or repository target when comparing or copying.
  4. Search for the flow.
  5. Review match indicators.
  6. Open the flow, Director, Flow Inspector, or a row action as needed.

Flow Inspector

Flow Inspector gives a deeper view of a selected flow.

Use it to:

  • Review flow structure and metadata.
  • Inspect parent and subflow relationships.
  • Open subflows from the Subflow Map.
  • Review versions when the flow is backed by a PingOne environment.
  • Use ReplaceIQ for scoped, preview-first refactoring.
  • Use NodeIQ Connect for supported node-level edits.

When a flow is loaded from a file, environment-only actions such as Flow Versions are hidden.

Flow Versions

Use Flow Versions to review, alias, revert, and delete versions.

Important behavior:

  • Revert creates a staged current version and refreshes the flow list and inspector.
  • Delete can act on selected versions when multiple rows are checked.
  • Alias actions update version labels for later auditing.
  • Rollback does not automatically deploy unless the specific workflow says so.

Copy and Migration

Use direct copy actions for simpler movement. Use FlightIQ Director when the migration requires dependency review, subflow handling, naming, versioning, aliases, descriptions, or upgrade-in-place behavior.

Before broad flow changes:

  1. Confirm source and destination environments.
  2. Review matches and conflicts.
  3. Export backups where available.
  4. Resolve connector, variable, form, notification, or MFA dependencies.
  5. Review final confirmation modals.

Repository Use

Flows can be loaded from or written to enabled repository targets. Repository-backed flows may hide environment-only actions that require live PingOne APIs.

Troubleshooting

If flows do not appear, confirm:

  • Source environment is selected.
  • Worker app has DaVinci read access.
  • Search and filters are cleared.
  • Repository path points to flow content when using a repository source.