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

Summary

I was very tempted to write this chapter much earlier in the book but felt that you need to understand the tools before mastering how you can improve logic app performance. In this chapter, you have been able to consider running code in parallel and the benefit of doing this. You have also considered that branching your logic app will also scope the data to entities on the same branch and above the action, as well as to any sections that are not in a branch. You have also learned to use branches that will only be used based on the status of the previous action – if the earlier action failed, follow, and use the fail branch. The default setting for all branches is that the earlier action passed. This is referred to as the run after state.

We considered a Common Data Service (Dataverse) action called List rows, which filters the entity by performing an OData query. Alternatively, we have the Get row action, which although similar relies on you knowing the primary GUID...