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-enterprise-integration-xml-validation.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ This guide shows how your logic app workflow can validate XML messages and docum
25
25
26
26
- The logic app resource and workflow where you want to validate XML.
27
27
28
-
Your workflow must start with a trigger, but you can use any trigger that works for your scenario. For more information, see these [general steps](create-workflow-with-trigger-or-action.md#add-trigger) to add any trigger you want.
28
+
Your workflow must start with a trigger, but you can use any trigger that works for your scenario. For more information, see these [general steps](add-trigger-action-workflow.md#add-trigger) to add any trigger you want.
29
29
30
30
The examples in this guide use the [**Request** trigger named **When an HTTP request is received**](../connectors/connectors-native-reqres.md), which waits until an external caller sends a request to the trigger. Alternatively, you can use the [**Schedule** trigger named **Recurrence**](../connectors/connectors-native-recurrence.md).
31
31
@@ -47,7 +47,7 @@ This guide shows how your logic app workflow can validate XML messages and docum
47
47
48
48
1. In the [Azure portal](https://portal.azure.com), open the logic app resource. Open your workflow in the designer.
49
49
50
-
1. On the designer, follow these [general steps](create-workflow-with-trigger-or-action.md?tabs=standard#add-action) to add the **XML Operations** action with the name that matches your workflow type:
50
+
1. On the designer, follow these [general steps](add-trigger-action-workflow.md?tabs=standard#add-action) to add the **XML Operations** action with the name that matches your workflow type:
51
51
52
52
| Workflow | Action name |
53
53
|----------|-------------|
@@ -73,19 +73,19 @@ This guide shows how your logic app workflow can validate XML messages and docum
73
73
74
74
1. To specify the schema for validation, follow the steps for your workflow type:
75
75
76
-
**Consumption**
76
+
-**Consumption**
77
77
78
-
From the **Schema Name** list, select the schema from the linked integration account.
78
+
From the **Schema Name** list, select the schema from the linked integration account.
79
79
80
-
**Standard**
80
+
-**Standard**
81
81
82
-
1. From the **Schema source** list, select **IntegrationAccount** or **LogicApp**.
82
+
1. From the **Schema source** list, select **IntegrationAccount** or **LogicApp**.
83
83
84
-
This example selects **IntegrationAccount**.
84
+
This example selects **IntegrationAccount**.
85
85
86
-
1. From the **Schema name** list, select the schema.
86
+
1. From the **Schema name** list, select the schema.
87
87
88
-
1.When you're done, save your workflow.
88
+
1.Save your workflow.
89
89
90
90
You're now finished with setting up your validate XML action. In a real world app, you might want to store the validated data in a line-of-business (LOB) app such as SalesForce. To send the validated output to Salesforce, add a **Salesforce** action.
0 commit comments