Skip to content

Commit 840660a

Browse files
committed
Partial updates
1 parent 6e67bff commit 840660a

File tree

7 files changed

+12
-12
lines changed

7 files changed

+12
-12
lines changed

articles/connectors/connectors-native-reqres.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -418,31 +418,31 @@ When you use the Request trigger to receive inbound requests, you can model the
418418

419419
1. In the workflow designer, under the step where you want to add the Response action, select **New step**.
420420

421-
For example, using the Request trigger from earlier:
421+
Or, to add an action between steps, move your pointer over the arrow between those steps. Select the plus sign (**+**) that appears, and then select **Add an action**.
422422

423-
![Add new step](./media/connectors-native-reqres/add-response.png)
423+
The following example adds the Response action after the Request trigger from the preceding section:
424424

425-
To add an action between steps, move your pointer over the arrow between those steps. Select the plus sign (**+**) that appears, and then select **Add an action**.
425+
![Screenshot showing Azure portal, Consumption workflow, and "New step" selected.](./media/connectors-native-reqres/add-response-consumption.png)
426426

427-
1. Under **Choose an action**, in the search box, enter `response` as your filter, and select the **Response** action.
427+
1. On the designer, under the **Choose an operation** search box, select **Built-in**. In the search box, enter **response**. From the actions list, select the **Response** action.
428428

429-
![Select the Response action](./media/connectors-native-reqres/select-response-action.png)
429+
For simplicity, the following examples show a collapsed Request trigger.
430430

431-
The Request trigger is collapsed in this example for simplicity.
431+
![Screenshot showing Azure portal, Consumption workflow, "Choose an operation" search box with "response" entered, and and Response action selected](./media/connectors-native-reqres/select-response-action-consumption.png)
432432

433-
1. Add any values that are required for the response message.
433+
1. In the Response action information box, add the required values for the response message.
434434

435435
In some fields, clicking inside their boxes opens the dynamic content list. You can then select tokens that represent available outputs from previous steps in the workflow. Properties from the schema specified in the earlier example now appear in the dynamic content list.
436436

437-
For example, for the **Headers** box, include `Content-Type` as the key name, and set the key value to `application/json` as mentioned earlier in this topic. For the **Body** box, you can select the trigger body output from the dynamic content list.
437+
For example, for the **Headers** box, include **Content-Type** as the key name, and set the key value to **application/json** as mentioned earlier in this article. For the **Body** box, you can select the trigger body output from the dynamic content list.
438438

439-
![Response action details](./media/connectors-native-reqres/response-details.png)
439+
![Screenshot showing Azure portal, Consumption workflow, and Response action information.](./media/connectors-native-reqres/response-details-consumption.png)
440440

441441
To view the headers in JSON format, select **Switch to text view**.
442442

443-
![Headers - Switch to text view](./media/connectors-native-reqres/switch-to-text-view.png)
443+
![Screenshot showing Azure portal, Consumption workflow, and Response action headers in "Switch to text" view.](./media/connectors-native-reqres/switch-to-text-view-consumption.png)
444444

445-
Here is more information about the properties that you can set in the Response action.
445+
The following table has more information about the properties that you can set in the Response action.
446446

447447
| Property name | JSON property name | Required | Description |
448448
|---------------|--------------------|----------|-------------|
@@ -451,7 +451,7 @@ When you use the Request trigger to receive inbound requests, you can model the
451451
| **Body** | `body` | No | The response body |
452452
|||||
453453

454-
1. To specify additional properties, such as a JSON schema for the response body, open the **Add new parameter** list, and select the parameters that you want to add.
454+
1. To add more properties for the action, such as a JSON schema for the response body, open the **Add new parameter** list, and select the parameters that you want to add.
455455

456456
1. When you're done, save your logic app. On the designer toolbar, select **Save**.
457457

64 KB
Loading
Binary file not shown.
14.5 KB
Loading
Binary file not shown.

0 commit comments

Comments
 (0)