FlightIQ Director

FlightIQ Director is the guided migration workflow for DaVinci flows. Use it when copying a flow bundle as new, upgrading an existing destination flow in place, resolving dependencies, or applying naming and versioning standards during migration.

When to Use Director

Use Director when:

  • Migrating a flow and its subflows.
  • Upgrading an existing destination flow in place.
  • Copying a flow bundle as new.
  • Resolving connector, form, notification, MFA, code snippet, or variable dependencies.
  • Applying naming, versioning, alias, and description updates as part of migration.

Before You Start

Confirm:

  1. Worker app credentials test successfully.
  2. Source and destination environments are selected.
  3. The source flow is selected in Orchestration > Flows.
  4. Destination access is correct.
  5. You understand whether the run should copy as new or upgrade in place.

For production-like environments, export backups before running a migration.

Open Director

From Orchestration > Flows:

  1. Select the source environment.
  2. Select the destination environment.
  3. Find the source flow.
  4. Open the row action for FlightIQ Director or the copy/migration action that launches Director.

Director Steps

Run Setup

Review source and destination context, defaults, match status, and the flow plan.

The flow plan shows:

  • Main flow and subflows.
  • Default action.
  • Include Subflows setting.
  • Per-flow overrides.
  • Destination matches.
  • Copy names for new flows.
  • Blocking issues and warnings.

Director blocks continuation when required choices are missing.

Connectors

Resolve connector and special dependency issues.

Review mappings for:

  • Connector instances.
  • PingOne Forms nodes.
  • Notification templates.
  • MFA-related connector requirements.
  • Code snippet connector requirements.

Continue only after required issues are resolved.

Naming & Versioning

Review generated names and version behavior.

Use this step to confirm:

  • Source and destination flow names.
  • Version bump behavior.
  • Reuse, copy, and upgrade actions.
  • Destination conflicts.

Aliases & Descriptions

Set or confirm source and destination aliases and description updates. These values help later audits identify what Director touched and why.

Final Review & Execute

The Final Review step is read-only.

Confirm:

  • Source and destination environments.
  • Planned action counts.
  • Dependency resolutions.
  • Flows being copied, upgraded, reused, or skipped.
  • Alias and description updates.

Only execute after this review matches your intended change.

Directing

The Directing step shows execution progress while Director applies the plan. Do not close the app or change environments during execution.

Results

Review the migration outcome. Confirm the expected flows were copied, upgraded, reused, or skipped. Open the destination flow after execution to inspect the final result.

Copy as New vs Upgrade in Place

Use Copy as New when the destination should receive a new flow or subflow.

Use Upgrade in Place when an existing destination flow should be updated while preserving the destination flow identity where possible.

Before executing an upgrade:

  • Confirm the destination match is correct.
  • Resolve all blocking dependency issues.
  • Review planned names, aliases, descriptions, and version behavior.
  • Export backups where available.

Subflows

When Include Subflows is enabled, Director treats the selected root flow as the start of a tree and includes referenced subflows in the plan.

Review each subflow action. A subflow can be copied as new, upgraded, or reused depending on the plan and available destination matches.

Dependency Resolution

Director migration depends on destination-compatible artifacts. Missing or ambiguous dependencies must be resolved before execution.

Common dependency areas:

  • Connector instances.
  • Forms.
  • Notification templates.
  • Variables.
  • MFA connectors.
  • Code snippets.

If a resolution choice is unclear, stop and verify the destination configuration before continuing.

Backup and Rollback Expectations

Use backup actions where available before executing a migration.

Rollback behavior depends on the action taken:

  • Upgraded flows can rely on version history and revert workflows.
  • Copied flows may need to be deleted manually if the run should be undone.
  • Alias and description updates should be reviewed in the Results step.

Rollback does not automatically deploy unless the specific workflow explicitly says so.

Troubleshooting

Director Cannot Continue

Review the blocking issue summary. Common causes include missing destination selections, unresolved connector mappings, unresolved form mappings, or copy names that conflict with existing destination names.

Destination Match Looks Wrong

Do not execute. Return to the flow plan, override the destination selection, or use Copy as New instead of Upgrade in Place.

Execution Fails

Review the Results step and any run log available in the modal. Confirm worker app permissions, destination access, and upstream PingOne constraints.