Skip to content

Commit 78f9b57

Browse files
authored
Update logic-apps-using-sap-connector.md
1 parent 65d9f09 commit 78f9b57

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/logic-apps/logic-apps-using-sap-connector.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ To follow along with this article, you need these items:
5858

5959
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.
6060

61-
### Add an HTTP request trigger
61+
### Add an HTTP Request trigger
6262

6363
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.
6464

@@ -68,7 +68,7 @@ In this example, you create a logic app with an endpoint in Azure so that you ca
6868

6969
1. In the search box, enter "http request" as your filter. From the triggers list, select **When a HTTP request is received**.
7070

71-
![Add HTTP request trigger](./media/logic-apps-using-sap-connector/add-trigger.png)
71+
![Add HTTP Request trigger](./media/logic-apps-using-sap-connector/add-trigger.png)
7272

7373
1. Now save your logic app so that you can generate an endpoint URL for your logic app. On the designer toolbar, select **Save**.
7474

@@ -134,7 +134,7 @@ In Azure Logic Apps, an [action](../logic-apps/logic-apps-overview.md#logic-app-
134134

135135
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.
136136

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.
138138

139139
![Select "Body" field](./media/logic-apps-using-sap-connector/SAP-app-server-action-select-body.png)
140140

@@ -166,7 +166,7 @@ Now add a response action to your logic app's workflow and include the output fr
166166

167167
1. On the designer toolbar, select **Run**. This step manually starts your logic app.
168168

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.
170170
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).
171171

172172
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.
265265

266266
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.
267267

268-
### Add an HTTP request trigger
268+
### Add an HTTP Request trigger
269269

270270
1. In the Azure portal, create a blank logic app, which opens the Logic App Designer.
271271

0 commit comments

Comments
 (0)