Merge pull request #114642 from ecfan/flat-file

Update screenshots and content for encoding and decoding flat files

Author: tfosmark

articles/logic-apps/logic-apps-enterprise-integration-flatfile.md

@@ -1,93 +1,103 @@
 ---
 title: Encode or decode flat files
-description: Encode or decode flat files for enterprise integration with Azure Logic Apps and Enterprise Integration Pack
+description: Encode or decode flat files for enterprise integration in Azure Logic Apps by using the Enterprise Integration Pack
 services: logic-apps
 ms.suite: integration
 author: divyaswarnkar
 ms.author: divswa
 ms.reviewer: jonfan, estfan, logicappspm
 ms.topic: article
-ms.date: 07/08/2016
+ms.date: 05/09/2020
 ---
 
-# Encode or decode flat files with Azure Logic Apps and Enterprise Integration Pack
+# Encode and decode flat files in Azure Logic Apps by using the Enterprise Integration Pack
 
-You may want to encode XML content before you send it to a business partner in a business-to-business (B2B) scenario. In a logic app, you can use the flat file encoding connector to do this. The logic app that you create can get its XML content from a variety of sources, including from an HTTP request trigger, from another application, or even from one of the many [connectors](../connectors/apis-list.md). For more information about logic apps, see the [logic apps documentation](logic-apps-overview.md "Learn more about Logic apps").  
+Before you send XML content to a business partner in a business-to-business (B2B) scenario, you might want to encode that content first. By building a logic app, you can encode and decode flat files by using the **Flat File** connector. Your logic app can get this XML content from various sources, such as the Request trigger, another app, or other [connectors supported by Azure Logic Apps](../connectors/apis-list.md). For more information, see [What is Azure Logic Apps](logic-apps-overview.md)?
 
-## Create the flat file encoding connector
-Follow these steps to add a flat file encoding connector to your logic app.
+## Prerequisites
 
-1. Create a logic app and [link it to your integration account](logic-apps-enterprise-integration-accounts.md "Learn to link an integration account to a Logic app"). This account contains the schema you will use to encode the XML data.  
+* An Azure subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
 
-1. In the Logic App Designer, add the **When an HTTP request is received** trigger to your logic app.
+* The logic app where you want to use the **Flat File** connector and a trigger that starts your logic app's workflow. The **Flat File** connector provides only actions, not triggers. You can use either the trigger or another action to feed the XML content into your logic app for encoding or decoding. If you're new to logic apps, review [Quickstart: Create your first logic app](../logic-apps/quickstart-create-first-logic-app-workflow.md).
 
-1. Add the flat file encoding action, as follows:
+* An [integration account](../logic-apps/logic-apps-enterprise-integration-create-integration-account.md) that's associated with your Azure subscription and [linked to the logic app](logic-apps-enterprise-integration-accounts.md#link-account) where you plan to use the **Flat File** connector. Both your logic app and integration account must exist in the same location or Azure region.
 
-   a. Select the **plus** sign.
+* A flat file [schema](logic-apps-enterprise-integration-schemas.md) that you've uploaded to your integration account for encoding or decoding the XML content
 
-   b. Select the **Add an action** link (appears after you have selected the plus sign).
+* At least two [trading partners](logic-apps-enterprise-integration-partners.md) that you've already defined in your integration account
 
-   c. In the search box, enter *Flat* to filter all the actions to the one that you want to use.
+## Add flat file encode action
 
-   d. Select the **Flat File Encoding** option from the list.   
+1. In the [Azure portal](https://portal.azure.com), open your logic app in the Logic App Designer.
 
-      ![Screenshot of Flat File Encoding option](media/logic-apps-enterprise-integration-flatfile/flatfile-2.png)   
+1. Under the trigger or action in your logic app, select **New step** > **Add an action**. This example uses the Request trigger, which is named **When a HTTP request is received**, and handles inbound requests from outside the logic app.
 
-1. On the **Flat File Encoding** dialog box, select the **Content** text box.  
+   > [!TIP]
+   > Providing a JSON schema is optional. If you have a sample payload from the inbound request, 
+   > select **Use sample payload to generate schema**, enter the sample payload, and select **Done**. 
+   > The schema appears in the **Request Body JSON Schema** box.
 
-   ![Screenshot of Content text box](media/logic-apps-enterprise-integration-flatfile/flatfile-3.png)  
+1. Under **Choose an action**, enter `flat file`. From the actions list, select this action: **Flat File Encoding**
 
-1. Select the body tag as the content that you want to encode. The body tag will populate the content field.     
+   ![Select "Flat File Encoding" action](./media/logic-apps-enterprise-integration-flatfile/select-flat-file-encoding.png)
 
-   ![Screenshot of body tag](media/logic-apps-enterprise-integration-flatfile/flatfile-4.png)  
+1. Click inside the **Content** box so that the dynamic content list appears. From the list, in the **When a HTTP request is received** section, select the **Body** property, which contains the request body output from the trigger and the content to encode.
 
-1. Select the **Schema Name** list box, and choose the schema you want to use to encode the input content.    
+   ![Select content to encode from dynamic content list](./media/logic-apps-enterprise-integration-flatfile/select-content-to-encode.png)
 
-   ![Screenshot of Schema Name list box](media/logic-apps-enterprise-integration-flatfile/flatfile-5.png)  
+   > [!TIP]
+   > If you don't see the **Body** property in the dynamic content list, 
+   > select **See more** next to the **When a HTTP request is received** section label.
+   > You can also directly enter the content to decode in the **Content** box.
 
-1. Save your work.
+1. From the **Schema Name** list, select the schema that's in your linked integration account to use for encoding, for example:
 
-   ![Screenshot of Save icon](media/logic-apps-enterprise-integration-flatfile/flatfile-6.png)  
+   ![Select schema to use for encoding](./media/logic-apps-enterprise-integration-flatfile/select-schema-for-encoding.png)
 
-At this point, you are finished setting up your flat file encoding connector. In a real world application, you may want to store the encoded data in a line-of-business application, such as Salesforce. Or you can send that encoded data to a trading partner. You can easily add an action to send the output of the encoding action to Salesforce, or to your trading partner, by using any one of the other connectors provided.
+   > [!NOTE]
+   > If no schema appears in the list, your integration account doesn't contain any schema files to use for encoding. 
+   > Upload the schema that you want to use to your integration account.
 
-You can now test your connector by making a request to the HTTP endpoint, and including the XML content in the body of the request.  
+1. Save your logic app. To test your connector, make a request to the HTTPS endpoint, which appears in the Request trigger's **HTTP POST URL** property, and include the XML content that you want to encode in the request body.
 
-## Create the flat file decoding connector
+You're now done with setting up your flat file encoding action. In a real world app, you might want to store the encoded data in a line-of-business (LOB) app, such as Salesforce. Or, you can send the encoded data to a trading partner. To send the output from the encoding action to Salesforce or to your trading partner, use the other [connectors available in Azure Logic Apps](../connectors/apis-list.md).
 
-> [!NOTE]
-> To complete these steps, you need to have a schema file already uploaded into you integration account.
+## Add flat file decode action
 
-1. In the Logic App Designer, add the **When an HTTP request is received** trigger to your logic app.
+1. In the [Azure portal](https://portal.azure.com), open your logic app in the Logic App Designer.
 
-1. Add the flat file decoding action, as follows:
+1. Under the trigger or action in your logic app, select **New step** > **Add an action**. This example uses the Request trigger, which is named **When a HTTP request is received**, and handles inbound requests from outside the logic app.
 
-   a. Select the **plus** sign.
+   > [!TIP]
+   > Providing a JSON schema is optional. If you have a sample payload from the inbound request, 
+   > select **Use sample payload to generate schema**, enter the sample payload, and select **Done**. 
+   > The schema appears in the **Request Body JSON Schema** box.
 
-   b. Select the **Add an action** link (appears after you have selected the plus sign).
+1. Under **Choose an action**, enter `flat file`. From the actions list, select this action: **Flat File Decoding**
 
-   c. In the search box, enter *Flat* to filter all the actions to the one that you want to use.
+   ![Select "Flat File Decoding" action](./media/logic-apps-enterprise-integration-flatfile/select-flat-file-decoding.png)
 
-   d. Select the **Flat File Decoding** option from the list.   
+1. Click inside the **Content** box so that the dynamic content list appears. From the list, in the **When a HTTP request is received** section, select the **Body** property, which contains the request body output from the trigger and the content to decode.
 
-      ![Screenshot of Flat File Decoding option](media/logic-apps-enterprise-integration-flatfile/flatfile-2.png)   
+   ![Select content to decode from dynamic content list](./media/logic-apps-enterprise-integration-flatfile/select-content-to-decode.png)
 
-1. Select the **Content** control. This produces a list of the content from earlier steps that you can use as the content to decode. Notice that the *Body* from the incoming HTTP request is available to be used as the content to decode. You can also enter the content to decode directly into the **Content** control.     
+   > [!TIP]
+   > If you don't see the **Body** property in the dynamic content list, 
+   > select **See more** next to the **When a HTTP request is received** section label. 
+   > You can also directly enter the content to decode in the **Content** box.
 
-1. Select the *Body* tag. Notice the body tag is now in the **Content** control.
+1. From the **Schema Name** list, select the schema that's in your linked integration account to use for decoding, for example:
 
-1. Select the name of the schema that you want to use to decode the content. The following screenshot shows that *OrderFile* is the selected schema name. This schema name had been uploaded into the integration account previously.
+   ![Select schema to use for decoding](./media/logic-apps-enterprise-integration-flatfile/select-schema-for-decoding.png)
 
-   ![Screenshot of Flat File Decoding dialog box](media/logic-apps-enterprise-integration-flatfile/flatfile-decode-1.png) 
+   > [!NOTE]
+   > If no schema appears in the list, your integration account doesn't contain any schema files to use for decoding. 
+   > Upload the schema that you want to use to your integration account.
 
-1. Save your work.  
+1. Save your logic app. To test your connector, make a request to the HTTPS endpoint, which appears in the Request trigger's **HTTP POST URL** property, and include the XML content that you want to decode in the request body.
 
-   ![Screenshot of Save icon](media/logic-apps-enterprise-integration-flatfile/flatfile-6.png)    
-
-At this point, you are finished setting up your flat file decoding connector. In a real world application, you may want to store the decoded data in a line-of-business application such as Salesforce. You can easily add an action to send the output of the decoding action to Salesforce.
-
-You can now test your connector by making a request to the HTTP endpoint and including the XML content you want to decode in the body of the request.  
+You're now done with setting up your flat file decoding action. In a real world app, you might want to store the decoded data in a line-of-business (LOB) app, such as Salesforce. Or, you can send the decoded data to a trading partner. To send the output from the decoding action to Salesforce or to your trading partner, use the other [connectors available in Azure Logic Apps](../connectors/apis-list.md).
 
 ## Next steps
-* [Learn more about the Enterprise Integration Pack](logic-apps-enterprise-integration-overview.md "Learn about Enterprise Integration Pack").  
 
+* Learn more about the [Enterprise Integration Pack](logic-apps-enterprise-integration-overview.md)