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
  • Define Conditional Logic
  • Add Condition
  • Creating Value Branches
  1. Workflows

Using Branch Conditionals

Using branch conditionals in Looply workflows

PreviousUsing ConditionalsNextUsing Advanced Conditionals

Last updated 1 year ago

Branch conditionals empower users to set a single variable and conditional operator rule, and then create multiple branches of outcomes tailored to the values evaluated against the specified condition.

With the ability to define diverse paths based on varying values or outcomes, these Branch Conditional Steps elevate the sophistication of your workflows, providing a nuanced approach to shaping the flow of your processes.

Define Conditional Logic

You can get started adding your conditional logic by clicking on a + button in your workflow and selecting the Branch Conditional step from the Workflow's toolbox.

Add Condition

Branch Conditionals work differently from standard Conditionals, in that they only support one single condition being defined but can have multiple different value outcomes.

You can define your single conditional rule by entering a variable in the text field and selecting a conditional operator from the dropdown menu.

Conditions we support are:

  • Boolean Equals

  • Is Boolean

  • Is Null

  • Is Numeric

  • Is Present

  • Is String

  • Is Timestamp

  • Not

  • Numeric Equals

  • Numeric Greater Than

  • Numeric Greater Than Equals

  • Numeric Less Than

  • Numeric Less Than Equals

  • String Equals

  • String Greater Than

  • String Greater Than Equals

  • String Less Than

  • String Less Than Equals

  • String Matches

  • Timestamp Equals

  • Timestamp Greater Than

  • Timestamp Greater Than Equals

  • Timestamp Less Than

  • Timestamp Less Than Equals

Creating Value Branches

Once you have defined your conditional rule, click and drag from the icon attached to the Branch Conditional step within the workflow to create a new value branch.

The Create Branch dialog will open and allow you to specify a:

  • Label - the user-friendly name for your outcome

  • Value - the value that will be evaluated against the condition

  • Type - the type of outcome being handled (Default, Positive, Negative, Warning or Info)

Enter these values for your branch and click Create.

You can create as many branches as required for your condition to handle different outcomes.

Deleting Branches

Branches can be edited by simply clicking on the branch and editing its values in the sidebar window or removed by clicking the Delete button.