Azure Logic Apps

Overview – Azure Logic Apps
Create cross-environment parameters in Azure Logic Apps workflow
Create a Http trigger-based workflow
Creating a Logic App that showcases the use of all variable types
Logic app workflow involves a string or JSON object created from multiple inputs of different data types
Logic App – Insert data into On-Prem SQL Server
Logic App workflow to retrieve data from SQL using a stored procedure
Workflow triggered by recurrence that connects to on-premises file systems in Azure Logic Apps
Logic App workflow for creating a file in SFTP with exception handling
Create or join parallel branches using workflow actions in Azure Logic Apps
Logic App workflow with a “For Each” loop that processes items sequentially
Logic App workflow that retrieves JSON data from an HTTP request and converts it into a CSV format
Create HTML table in Logic App workflow
A Logic App workflow that uses Filter array, Select and Join actions
JavaScript code inline in Azure Logic Apps workflow
Batching (aggregating) messages using batch receive and batch sender in a Logic App
Manage large messages in workflows by using chunking in Azure Logic Apps
Azure Logic Apps workflow- Handle throttling problems (429 – “Too many requests” errors)
Identify and resolve workflow failures in Azure Logic Apps
Monitoring the health and performance of Azure Logic Apps workflows
An overview of automating the deployment of Azure Logic Apps using Azure Resource Manager templates
Ensuring secure access and data protection for workflows in Azure Logic Apps
Effective Planning and Management of Costs for Azure Logic Apps
Encoding and decoding flat files in Azure Logic Apps workflows using Text and XML formats
Testing workflows with mock outputs in Azure Logic Apps
Delay and Delay until action in Azure Logic Apps
Invoke REST API endpoints within workflows using Azure Logic Apps
Use Liquid templates as maps in workflows to transform JSON to JSON/TEXT and XML to JSON/TEXT in Azure Logic Apps
Manage Azure resources and monitor expenses by creating automated tasks
Previous Lesson
Next Lesson

Create or join parallel branches using workflow actions in Azure Logic Apps

Azure Logic Apps Create or join parallel branches using workflow actions in Azure Logic Apps
Adding a parallel branch in an Azure Logic App allows you to execute multiple actions simultaneously. This is useful when you want to perform independent tasks concurrently, such as sending notifications, logging data, or calling multiple APIs.
Below is an example of a Logic App workflow that includes a parallel branch:

Example Scenario

  • Trigger: HTTP request to start the workflow.
  • Parallel Branches:
    • Branch 1: Create a file on an SFTP server.
    • Branch 2: Send an email notification.
  • Merge: Wait for both branches to complete before sending a final HTTP response.

Steps to Create the Workflow

  1. Trigger: HTTP Request
    • Add an HTTP request trigger to start the workflow.
    • Define the JSON schema for the incoming request body (if applicable).
  2. Add a Parallel Branch
    • After the trigger, click the + button and select Add a parallel branch.
    • This will create two parallel branches.
  3. Branch 1: SFTP – Create File
    • Add an SFTP action to create a file on the SFTP server.
    • Configure the connection and specify the file path and content.
  4. Branch 2: Send Email Notification
    • Add a Send email (V2) Gmail action (or another email connector) to send an email.
    • Configure the email details (e.g., recipient, subject, body).
  5. Merge the Branches
    • After both branches, add a Condition or Response action to merge the branches.
    • Ensure the workflow waits for both branches to complete before proceeding.
  6. Final Action: HTTP Response
    • Add an HTTP response action to send a final response back to the caller.
    • Include a success message or data from the parallel branches.
Here's how Logic App should look:
estudy247-la-test-parallel-06

Key Points

  1. Parallel Branches:
    • Use the Add a parallel branch feature to create independent actions that run concurrently.
    • Each branch operates independently and does not wait for the other to complete.
  2. Merge:
    • After the parallel branches, add an action (e.g., HTTP response) that waits for both branches to complete.
  3. Outputs:
    • You can include outputs from both branches in the final response or logging.
  4. Error Handling:
    • Add exception handling within each branch if needed (e.g., retry policies or error responses).

You can download the logic app template from the estudy247 GitHub repository – la-test-parallel-06

Previous Lesson
Back to Course
Next Lesson
Post a comment

Leave a Comment

Scroll to Top