Looply Academy
  • Getting Started
    • What is Looply?
    • Deployment Models
  • System Requirements
  • SAP Integration: ABAP Add-on & Access
  • Security & Identity - What IT Teams Need to Know
  • Authenticating Teams User Actions to Enterprise Systems
  • Signing Up & Onboarding Your Team
  • Looply Implementation Plan
  • Looply Integration Demos
  • Integrations
    • Microsoft Integration
    • SAP Integration
      • Installing the ABAP Looply Add-On
        • Gateway Service Setup - Single System
        • Gateway Service Setup - Hub scenario
      • Triggering or Resuming a Looply Workflow from SAP
      • Triggering SAP code from Looply
      • SAP Workflow Integration
      • Varo/Stelo Integration
      • SSL & IP address
      • SSO Authentication
  • App Management
    • Building Apps
    • Deploying apps to Teams App catalog
      • Looply Dashboard
      • Manual Installation
    • Installing Looply Apps
    • Uninstall/Update Looply Apps
    • Teams Admin center
  • Adaptive Cards
    • Building Adaptive Cards
      • Container Elements
      • Content Elements
      • Input Elements
      • Actions
    • Data Binding
    • Conditional Rendering
    • AI Assistant
    • Inline Functions
  • Workflows
    • Building Workflows
    • Triggering Workflows
    • Environment Variables & Profiles
    • Versioning Workflows
    • Using HTTP Requests
    • Using Functions
    • Using Conditionals
    • Using Branch Conditionals
    • Using Advanced Conditionals
    • Using Integrations
      • Adaptive Card Actions
      • SAP Requests
    • Using Redirects
    • Using Override Payload
    • Terminating Workflows
  • Data Vault
    • Variable Datastores
  • Monitoring & Logs
    • Monitoring Workflows
    • Error Notifications
  • API REFERENCE
    • Developer API Overview
    • Workflow API
    • Adaptive Card API
  • Team Management
    • Managing Organisations
    • Team Roles and Permissions
  • Resources
    • JavaScript Libraries
  • Tutorials
    • Creating MS Teams Apps
    • Designing Workflows
    • Building Adaptive Cards
    • Adaptive Cards with AI
    • Examining Workflow Executions
  • Support
    • Changelog
    • Contacting Support
Powered by GitBook
On this page
  • Version Statuses
  • Creating New Versions
  • Locking Versions
  1. Workflows

Versioning Workflows

Manage and track changes with ease with the power of workflow versioning at your fingertips

Workflow versioning is a critical feature that empowers users to manage changes, updates, and enhancements to their workflows with precision and control.

By creating versions of your workflows, you can ensure that improvements are made safely, test new configurations without disrupting ongoing operations, and easily roll back to previous versions if needed.

Version Statuses

Each version of a workflow within Looply is assigned a unique status, a fundamental aspect of our version control system.

When a workflow is in its Draft phase, it grants you the flexibility to freely modify and test your processes without impacting any operational Looply processes that utilise the most current version.

Upon finalising your adjustments, activating the workflow solidifies its status, thereby securing it against further modifications. Activation ensures that this particular version becomes the default for Looply processes configured to utilise the latest workflow version, maintaining system integrity and operational continuity.

For more information on triggering specific workflow versions see Triggering Workflows

Creating New Versions

You can get started creating a new version for your workflow by navigating to the latest active version, making some changes and then saving your workflow.

As the workflow is active, you will be prompted to confirm your changes and agree that a new version will be created in order to prevent potentially breaking changes to the existing workflow version. Once you have confirmed this, your workflow will immediately be versioned up and placed into Draft status to continue working on your changes.

Locking Versions

Once you have made the necessary changes to your workflow and are ready to go live, you can activate your workflow by clicking the Activate button.

This will prevent any further changes from being allowed on this version of your workflow and will ensure this version is now picked up as the latest.

PreviousEnvironment Variables & ProfilesNextUsing HTTP Requests

Last updated 1 year ago