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

Using pass/fail branches and run after

One other point to note is that branches can be used to determine execution context. By pressing the more button (three dots) on the topmost action in a branch, you can adjust the arrow at the top of the branch to define when data is passed into this branch. The default is to flow data to the action if the subsequent action has a status of passed. In other words, if the previous action worked, carry on to the next one below it. However, this context can be changed, as you can see in the following screenshot:

Figure 11.3 – The combined logic app can reference fields from either branch. Note the arrow has changed to red to indicate a non-default option is in use

Now, only one path will execute. If the Switch statement failed, an entry will be added to the database; otherwise, if the Switch statement succeeded, the contact is updated in our CRM system, for example, Dynamics 365. This is common practice for auditing...