The course is part of this learning path
Creating a Logic App
Creating a Custom Connector for Logic Apps
Creating a Custom Template
The Microsoft Azure cloud offers many options for developers who want to build websites and services on Web Apps. Normally, the coding is done using proprietary Microsoft languages like C#, Visual Basic, and others. More recently Microsoft has made it easier for open source developers to use the IDE and language of their choice with support for PHP, Java, Node.js, and Go for server-side code. However, some web solutions may not require a complex programming language to meet the requirements, and that’s where Logic Apps comes in.
This course looks at some of the features and benefits of Logic Apps and examines the kinds of business processes that you can easily model. We will look at the wider topic of workflow and automation problems and then show you how to transform these into Logic App solutions. We will also look at the internal components that make up a Logic App, including triggers, conditions, actions, and standard connectors.
For connecting to third-party SaaS services, or even your own homegrown APIs, you will learn how to create a custom connector. You will also learn about rapid deployment using Azure templates.
- Implement simple automation and workflow using Logic Apps
- Model business processes as a series of conditions and actions
- Monitor Azure Apps, Office 365, or third-party services using triggers
- Connect to Azure services and other well-known third-party websites
- People who want to become Azure developers
- Non-developers who want to build point-and-click solutions
- Solution architects
- General exposure to basic cloud technology
- Familiarity with the Azure Portal
Creating a custom template for Logic Apps. You can create a template for most of your Azure designs by using the same built-in JSON definition files that are used to deploy them.
To create a template for our first Logic App, let's go back to the Logic App Designer. Now in the middle pane, let's click on Automation scripts. Here again, you can see the code along with Parameters, Variables, and Resources used.
You have the option to edit the template in code and also to save the template to your library.
We will name it and now go over to the template section of the Azure portal. Notice our template is here.
From this interface, you can deploy any of your previous designs. You can make any adjustments or changes before the deployment with your old design as a starting point. I will deploy the design again as LA_test2. After a few seconds, you will see the running Logic App.
In this section, we talked about using parameters to make it easier to centralize values in your Logic App definitions. Let's take a look at the Office 365 properties that we are using. If you look at the specifications for the SharePoint sites and the email, you can see that they trace back to a subscription that was defined here. This is a good example of how parameters are used. Another developer could use this definition and simply change out the subscription to point to another account.
You can define the parameters yourself. Here's an example of an URL that was changed from a specific value to a parameter just to show you the format.
And that's it for creating a custom template.
About the Author
Derrick is a content contributor and trainer for Microsoft cloud technologies like Azure, Office 365 and Dynamics 365. He works across North America and Europe to help companies and organizations with these technology shifts. Before that he has worn many hats but prefers to wear them one at a time.
When he is not night walking during his travels, you can find him on a bicycle path or performing guitar solos to an imaginary audience in his basement.