/
Pipeline Versioning & History

Pipeline Versioning & History

Overview

All Mapping pipelines now feature automatic version control. This internal tracking allows users to modify configurations with confidence, providing the flexibility to revert to any previous version at any time.

 

  1. Creating a Pipeline

    When a new mapping pipeline is initialized, EazyDI automatically generates an initial version and designates it as the Current Version.

    • To View Versions: Click the vertical ellipses (⋮) on the pipeline card and select Versions from the dropdown menu.

    image-20260220-084309.png

     

     

  2. Editing and Saving

    Every time a user modifies and saves a pipeline, the application captures the state as a new version.

    • Automatic Updates: The newly saved version is immediately promoted to the Current Version.

    • Archiving: All previous iterations are preserved and marked as available for restoration, ensuring no work is ever lost during experimentation.

    image-20260220-112833.png

     

  3. Reverting and Modifying Versions

    Users have full control over which version of a pipeline is active:

    • Restoring: To revert to a previous state, navigate to the Versions list and click the Restore button next to the desired version.

    • Adding Descriptions: For better traceability, you can add context to any version (e.g., "Updated mapping logic for Q3"). Click the Edit icon next to the "No description" placeholder located directly beneath the version date.

  4. Version Governance & Metadata

    To ensure a clear audit trail, the application automatically tracks specific data for every version created:

    • Automatic Timestamping: Every save is tagged with a precise date and time, allowing for a chronological history of all pipeline evolutions.

    • User Attribution: Each version displays the name of the user who performed the save, making it easy to identify contributors in a collaborative environment.

    • Current Version Badge: The active version is clearly labeled with a "Current Version" badge within the history list to prevent accidental overwrites or confusion during restoration.

  5. Best Practices and Guardrails

    • Descriptive Tagging: We recommend replacing the "No description" placeholder immediately after a major change (e.g., "Updated source-to-target mapping for Q3") to make future rollbacks faster.

    • The Restore Logic: Restoring a version does not delete your current work. Instead, it promotes the selected historical state to be the new Current Version, while your previous state remains safely archived in the history.

    • Pre-Restore Check: Always ensure your current workspace is saved before hitting the Restore button, as this action will refresh your active pipeline to match the historical version.