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

Examining a Try scope's output for debugging data

One other advantage of using scopes is that you can access the scope's own result status to see whether there is any problematic code within that section. That is useful when you want to test a section of your logic app you are unsure about or think of as unreliable.

To simulate this, I've amended our exercise. Scope 3 has been moved to the top of the logic app and simply renamed scope, for clarity. Within the scope, I have added a Terminate action of Failed (this can be found in the Control section of the Dynamic catalog). The new scope now looks like this:

Figure 8.15 – The amended scope with a forced failure

When I run this, the Terminate action will force a failure at this point. As an action within the scope has failed, the entire scope will be marked as failed.

Failure is a good and useful process. Logic apps should be tested both for their success as well as how they...