Note:
Auto Flow Creation is supported only for Cloud deployments on Whatfix Mirror.
Currently, Branching in a Flow is not supported with Auto Flow Creation. Each Flow follows the same sequence as the captured Mirror Workflow.
What is Auto Flow Creation?
Whatfix enables you to automatically create and maintain Flows in sync with your Mirror Workflows using Auto Flow Creation. When you capture a Mirror Workflow, Whatfix automatically creates the Flow and provides a description for each step. If you add, remove, or recapture Mirror Bildschirms in the Mirror Workflow, the auto-created Flow updates automatically to stay in sync with the Workflow.
For example, you can capture a new employee onboarding process as a Mirror Workflow, and Whatfix automatically creates a matching Flow for you to review and publish for your learners. Additionally, if you edit the Workflow to add two new Mirror Screens for a revised approval stage, Whatfix automatically adds the corresponding steps to the Flow.
For more information, see Auto Create a Flow.
How Auto Flow Creation Works
When you create a Mirror Workflow using Whatfix Studio, Whatfix selects the Create guidance flow for the Workflow checkbox by default and creates a Flow that replicates the captured Workflow step for step. Each Flow step receives an AI-generated description based on the content of the corresponding Mirror Bildschirm, reducing the overall effort to create a guided experience for your learner.
Additionally, Whatfix sets the source URL of the Flow to the Draft stage URL of the Mirror Workflow. As the Mirror Workflow moves across stages, Whatfix automatically updates the Flow's source URL to match, so you do not have to update it manually.
Note:
If you clear the Create guidance flow for the Workflow checkbox before you create a Mirror Workflow, Whatfix does not create a Flow.
Mirror and Flow Synchronization
By default, a Mirror Workflow and its auto-created Flow stay in sync automatically. Changes to the Mirror Workflow apply to the Flow, and stage movements on the Mirror Workflow reflect on the Flow.
Expand the following accordions for more details:
Adding a Mirror Screen to a Mirror Workflow
When you add a new Mirror Screen to a Mirror Workflow, Whatfix creates a corresponding step in the auto-created Flow at the same position. If you add the screen after all existing screens, the new step appears at the end of the Flow. If you insert the screen between two existing screens, the new step is inserted between the two corresponding Flow steps, and all subsequent steps are renumbered.
For example, if a Workflow has 5 screens and you add a sixth screen at the end, a sixth step appears in the linked Flow. Similarly, if you insert a new screen between screen 2 and screen 3, a new step appears between step 2 and step 3, and the former step 3 becomes step 4.
Stage movement between a Mirror Workflow and its auto-created Flow
When you move a Mirror Workflow across lifecycle stages (Draft to Ready, Ready to Production), the auto-created Flow moves to the same stage at the same time as the Workflow. This also applies to actions such as Unpublish and Edit in Draft.
For example, publishing a Mirror Workflow to the Production stage also publishes its auto-created Flow to Production.
Causes of Sync Breaks
A Mirror Workflow goes out of sync with its associated Flow when either of the following conditions occurs. Once a Flow goes out of sync, updates to the Mirror Workflow no longer apply to the Flow, and stage movement no longer applies to both.
Manually edit the Flow's steps using Launch live edit: When you edit the steps of an auto-created Flow using Launch live edit, the sync with its Mirror Workflow breaks.
Move the auto-created Flow: When you move the Flow to a different stage, the Mirror Workflow does not move with the Flow, and the sync between them breaks.
Note:
When you duplicate a Mirror Workflow that has an auto-created Flow, Whatfix does not duplicate the Flow.
Similarly, when you duplicate a Flow that is in sync with a Mirror Workflow, Whatfix does not duplicate the Mirror Workflow, and it does not carry over the sync.