Saving and Loading Workflows

Saving and Loading Workflows

Your cleansing workflow represents a carefully constructed pipeline of transformations. MatchLogic persists workflows to the server so you can save your progress, leave the page, and return later to pick up exactly where you left off.

Saving a Workflow

To save your current workflow, click the Save button in the flow builder toolbar. This persists the complete state of your workflow to the server, including:

• All nodes and their positions on the canvas.
• All connections (edges) between nodes.
• All node configurations and property values.

After saving, a confirmation message appears to let you know the save was successful. The undo/redo history is reset at this point, with the saved state becoming the new baseline.

How Workflows Are Stored

Workflows are saved per-datasource, per-project. This means:

• Each datasource in your project can have its own independent cleansing workflow.
• Switching between datasources loads the saved workflow for that specific datasource.
• Different projects are completely isolated — workflows do not cross project boundaries.

Loading a Workflow

When you navigate to the Data Cleansing module and select a datasource, MatchLogic automatically loads the last saved workflow for that datasource. All nodes, connections, and configurations are restored exactly as they were when you saved.

If no workflow has been saved for the selected datasource, you will see a blank canvas with just the Start and End nodes, ready for you to begin building.

Unsaved Changes Warning

If you have made changes to your workflow since the last save and attempt to navigate away from the Data Cleansing page, MatchLogic displays a navigation guard warning. This dialog asks you to confirm whether you want to leave without saving, giving you the opportunity to go back and save your work.

The navigation guard is triggered when you:

• Click a link to navigate to a different module (e.g., Match Configuration).
• Switch to a different datasource within the Data Cleansing module.
• Close or refresh the browser tab.

Best Practices

• Save frequently. Save after adding and configuring each group of related nodes, not just when you are done with the entire workflow.
• Save before previewing large operations. If you plan to run a complex transformation, save your current workflow first so you have a clean state to return to.
• Save before switching datasources. Although the navigation guard will remind you, it is good practice to save proactively before switching.