Wiresk

Wiresk

Flow Versioning 

Estimated reading time: 3 min

Refers to the ability to create and manage multiple versions of your automation workflows (Flows). 

Flow versioning combined with Flow environment in Wiresk creates a robust system for developing, testing, and deploying workflows without disrupting live operations. 

In this environment, different versions of the Flow are created as new features, logic, or improvements are added. Developers can save multiple drafts of Flow, each with its unique version number, making sure that changes are tracked over time. 

Use Case: A team could be building a sales Fow in the Dev environment. Versioning allows them to save one version where lead data is captured, another version where notifications are sent, and so on. If a step in the Flow introduces bugs, the team can revert to an earlier version that functioned correctly without starting from scratch. 

The Flow version that passed initial development in the Dev environment is promoted to UAT for testing. New versions may be created if tweaks or bug fixes are needed after feedback. Multiple versions may be tested to find the most effective solution before moving it to production. 

Use Case: The same sales automation workflow might be promoted to UAT after development. Business users test it to ensure all steps, such as assigning leads to sales reps and sending follow-up emails, work as expected. If an issue is found, the developer can change the Flow in Dev and promote a new version to UAT. 

Only the most stable and well-tested workflow versions are promoted to production. If new features or improvements are needed, they are developed and tested in Dev and UAT before updating the Prod version. Critical issues can be mitigated by rolling back to a previous version if necessary. 

Use Case: Once the sales automation workflow passes UAT, it’s promoted to Production. The team can then watch performance and ensure leads are correctly routed and emails are being sent. If an issue arises, they can quickly revert to a prior version that was functioning properly without downtime or a major business impact. 

The connection between versioning and environments allows for a controlled and smooth Flow deployment process: 

  • Parallel Development: It involves being able to simultaneously work on different versions in the Development environment. One team could be experimenting with fresh automation logic, while another is focusing on incorporating a new API, each saved as a distinct version. 
  • Testing and Feedback Loop: Once development is complete, the versioned Flows can be transferred to UAT for validation. If problems are noticed, developers can generate updated versions using the feedback and retest them before going live. 
  • Managing Risk in Production: Versioning guarantees that only thoroughly tested Flows are deployed to the production environment. If a Flow does not function properly or does not achieve business objectives, Wiresk enables reverting to a previous version, ensuring minimal impact. If the most recent Flow update causes a crash, the team can go back to the previous version when the Flow was working properly. 

The process of version promotion (moving a workflow from one environment to another) is crucial to prevent untested workflows from going live. The version control system ensures: 

  • Clarity and Accountability: Versioning provides a clear history of changes, including who made updates, when, and why. This is crucial for debugging and audit trails. 
  • Controlled Release: Workflow versions are only promoted after passing tests in the previous environment. This promotes a gradual, careful deployment rather than rushing changes directly into production. 
  1. Development: The team creates an invoice generation Flow in Dev, saving versions as they add features like customer notifications, auto-reminders, and invoice status updates. 
  1. UAT: After finishing the development, they promote the Flow to UAT, where the finance team tests the automation with live-like data. If they notice issues (e.g., invoices aren’t sent on time), the developers will adjust the Flow, creating a new version, and the finance team will re-test it. 
  1. Production: Once the workflow passes UAT, it is moved to the production environment. The system now automatically generates and sends invoices to customers, sends reminders, and updates internal tracking systems without manual intervention. 

If a bug is found in production (e.g., incorrect invoice amounts), the team can instantly revert to the earlier working version while they investigate and fix the problem in Dev and UAT.