You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-using-sap-connector.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ To follow along with this article, you need these items:
58
58
59
59
This example uses a logic app that you can trigger with an HTTP request. The logic app sends an IDoc to an SAP server and returns a response to the requestor that called the logic app.
60
60
61
-
### Add an HTTP request trigger
61
+
### Add an HTTP Request trigger
62
62
63
63
In Azure Logic Apps, every logic app must start with a [trigger](../logic-apps/logic-apps-overview.md#logic-app-concepts), which fires when a specific event happens or when a specific condition is met. Each time the trigger fires, the Logic Apps engine creates a logic app instance and starts running your app's workflow.
64
64
@@ -68,7 +68,7 @@ In this example, you create a logic app with an endpoint in Azure so that you ca
68
68
69
69
1. In the search box, enter "http request" as your filter. From the triggers list, select **When a HTTP request is received**.
1. Now save your logic app so that you can generate an endpoint URL for your logic app. On the designer toolbar, select **Save**.
74
74
@@ -134,7 +134,7 @@ In Azure Logic Apps, an [action](../logic-apps/logic-apps-overview.md#logic-app-
134
134
135
135
1. Click inside the **Input Message** box so that the dynamic content list appears. From that list, under **When a HTTP request is received**, select the **Body** field.
136
136
137
-
This step includes the body content from your HTTP request trigger and sends that output to your SAP server.
137
+
This step includes the body content from your HTTP Request trigger and sends that output to your SAP server.
@@ -166,7 +166,7 @@ Now add a response action to your logic app's workflow and include the output fr
166
166
167
167
1. On the designer toolbar, select **Run**. This step manually starts your logic app.
168
168
169
-
1. Trigger your logic app by sending an HTTP POST request to the URL in your HTTP request trigger.
169
+
1. Trigger your logic app by sending an HTTP POST request to the URL in your HTTP Request trigger.
170
170
Include your message content with your request. To the send the request, you can use a tool such as [Postman](https://www.getpostman.com/apps).
171
171
172
172
For this article, the request sends an IDoc file, which must be in XML format and include the namespace for the SAP action you're using, for example:
@@ -265,7 +265,7 @@ Your logic app is now ready to receive messages from your SAP system.
265
265
266
266
This example uses a logic app that you can trigger with an HTTP request. The SAP action sends a request to an SAP system to generate the schemas for specified IDoc and BAPI. Schemas that return in the response are uploaded to an integration account by using the Azure Resource Manager connector.
267
267
268
-
### Add an HTTP request trigger
268
+
### Add an HTTP Request trigger
269
269
270
270
1. In the Azure portal, create a blank logic app, which opens the Logic App Designer.
0 commit comments