Book Image

Enterprise Integration with Azure Logic Apps

By : Matthew Bennett
Book Image

Enterprise Integration with Azure Logic Apps

By: Matthew Bennett

Overview of this book

Logic Apps are a visual flowchart-like representation of common programming actions, and are a flexible way to create logic without writing a single line of code. Enterprise Integration with Azure Logic Apps is a comprehensive introduction for anyone new to Logic Apps which will boost your learning skills and allow you to create rich, complex, structured, and reusable logic with instant results. You'll begin by discovering how to navigate the Azure portal and understand how your objects can be zoned to a specific environment by using resource groups. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will teach you the benefits and foundations of Logic App logic design. As you advance, you'll find out how to manage your Azure environment in relation to Logic Apps and how to create elegant and reliable Logic Apps. With useful and practical explanations of how to get the most out of Logic App actions and triggers, you'll be able to ensure that your Logic Apps work efficiently and provide seamless integration for real-world scenarios without having to write code. By the end of this Logic Apps book, you'll be able to create complex and powerful Logic Apps within minutes, integrating large amounts of data on demand, enhancing your systems, and linking applications to improve user experience.
Table of Contents (17 chapters)
1
Section 1: Logic App Fundamentals
7
Section 2: Logic App Design
13
Section 3: Logic App Maintenance and Management

Logic app branches

The standard way to write a logic app is to start with a trigger, then work sequentially down through the logic app in series. This approach can take longer than anticipated because of the amount of time needed for Common Data Service/Dataverse or SQL queries. When you are communicating with on-premises equipment and systems especially, there can be a delay while Azure performs a handshake with the system. This is especially noticeable if this is the first run of the day as subsequent runs cache connections.

As a rule, if your logic can be diverted into separate strands, attempt to write your logic app to operate in parallel. Where you are not referencing data from an entity in other actions, these can be split off to operate in a different path or branch.

Figure 11.1 – A logic app with two branches

In the preceding example, the trigger is when a record is created. Next, we initialize a variable for later use. We have a switch...