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 a request/response pair to share data between logic apps

There are times when the opposite is true – you want to send a message and you are expecting a return in good time. Here, you may just want a child logic app at the heart of it all, or an Azure Function as the engine for your processing. In my example and sticking with contacts, now I know that an action has taken place, and which Contact this affects, I have created a GetContact logic app that will perform an HTTP API POST call back to the legacy system to obtain the contact records. From here, I can pick out the new field, reformat the data, and then pass it into my new system (in my case, the contact's record in D365).

In the middle of my child logic app, which is designed to create a contact detail line, I have an HTTP action to the GetContact logic app. This performs the record lookup in the legacy system:

Figure 9.5 – The GetContact logic app has a request for its trigger...