Updates and file renames

Author: ecfan

articles/logic-apps/.openpublishing.redirection.logic-apps.json

@@ -1,5 +1,10 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/logic-apps/logic-apps-add-run-inline-code.md",
+            "redirect_url": "/azure/logic-apps/add-run-javascript",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/logic-apps/logic-apps-azure-functions.md",
             "redirect_url": "/azure/logic-apps/call-azure-functions-from-workflows",

articles/logic-apps/add-run-csharp-scripts.md

@@ -1,5 +1,5 @@
 ---
-title: Add and run JavaScript code snippets in workflows
+title: Add and run JavaScript in workflows
 description: Write and run JavaScript code snippets in workflows to perform custom integration tasks using Inline Code operations in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
@@ -10,7 +10,7 @@ ms.custom: devx-track-js
 # Customer intent: As a logic app workflow developer, I want to write and run my own JavaScript code snippets so that I can perform custom integration tasks in Standard workflows for Azure Logic Apps.
 ---
 
-# Add and run JavaScript code snippets inline with workflows for Azure Logic Apps
+# Add and run JavaScript code inline with workflows for Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](~/reusable-content/ce-skilling/azure/includes/logic-apps-sku-consumption-standard.md)]
 
@@ -28,11 +28,11 @@ The following diagram shows the highlights from example workflow:
 
 ### [Consumption](#tab/consumption)
 
-:::image type="content" source="media/logic-apps-add-run-inline-code/inline-code-overview-consumption.png" alt-text="Screenshot shows example Consumption workflow with the Execute JavaScript Code action." lightbox="media/logic-apps-add-run-inline-code/inline-code-overview-consumption.png":::
+:::image type="content" source="media/add-run-javascript/inline-code-overview-consumption.png" alt-text="Screenshot shows example Consumption workflow with the Execute JavaScript Code action." lightbox="media/add-run-javascript/inline-code-overview-consumption.png":::
 
 ### [Standard](#tab/standard)
 
-:::image type="content" source="media/logic-apps-add-run-inline-code/inline-code-overview-standard.png" alt-text="Screenshot shows example Standard workflow with the Execute JavaScript Code action." lightbox="media/logic-apps-add-run-inline-code/inline-code-overview-standard.png":::
+:::image type="content" source="media/add-run-javascript/inline-code-overview-standard.png" alt-text="Screenshot shows example Standard workflow with the Execute JavaScript Code action." lightbox="media/add-run-javascript/inline-code-overview-standard.png":::
 
 ---
 
@@ -87,7 +87,7 @@ The following diagram shows the highlights from example workflow:
 
    This example adds the action under the Office 365 Outlook trigger. By default, the action contains some sample code, including a `return` statement.
 
-   ![Screenshot showing the Execute JavaScript Code action with default sample code.](./media/logic-apps-add-run-inline-code/inline-code-action-default-consumption.png)
+   ![Screenshot showing the Execute JavaScript Code action with default sample code.](./media/add-run-javascript/inline-code-action-default-consumption.png)
 
 1. In the **Code** box, delete the sample code, and enter your code. Write the code that you'd put inside a method, but without the method signature.
 
@@ -98,15 +98,15 @@ The following diagram shows the highlights from example workflow:
 
    If you start typing a recognized keyword, the autocomplete list appears so that you can select from available keywords, for example:
 
-   ![Screenshot showing the Consumption workflow, Execute JavaScript Code action, and keyword autocomplete list.](./media/logic-apps-add-run-inline-code/auto-complete-consumption.png)
+   ![Screenshot showing the Consumption workflow, Execute JavaScript Code action, and keyword autocomplete list.](./media/add-run-javascript/auto-complete-consumption.png)
 
    The following example code snippet first creates a variable named **myResult** that stores a *regular expression*, which specifies a pattern to match in input text. The code then creates a variable named **email** that stores the email message's body content from the trigger outputs.
 
-   ![Screenshot showing the Consumption workflow, Execute JavaScript Code action, and example code that creates variables.](./media/logic-apps-add-run-inline-code/save-email-body-variable-consumption.png)
+   ![Screenshot showing the Consumption workflow, Execute JavaScript Code action, and example code that creates variables.](./media/add-run-javascript/save-email-body-variable-consumption.png)
 
 1. With your cursor still in the **Code** box, from the open dynamic content list, find the **When a new email arrives** section, and select the **Body** property, which references the email message's body.
 
-   ![Screenshot showing the Consumption workflow, Execute JavaScript Code action, dynamic content list, and email message's "Body" property selected.](./media/logic-apps-add-run-inline-code/select-output-consumption.png)
+   ![Screenshot showing the Consumption workflow, Execute JavaScript Code action, dynamic content list, and email message's "Body" property selected.](./media/add-run-javascript/select-output-consumption.png)
 
    The dynamic content list shows the outputs from the trigger and any preceding actions when those outputs match the input format for the edit box that's currently in focus. This list makes these outputs easier to use and reference from your workflow. For this example, the list shows the outputs from the Outlook trigger, including the email message's **Body** property.
 
@@ -130,13 +130,13 @@ The following diagram shows the highlights from example workflow:
 
 1. To differentiate the email message's **Body** property that you selected from the trigger's `body` property, rename the second `body` property to `Body` instead. Add the closing semicolon (**;**) at the end to finish the code statement.
 
-   ![Screenshot showing the Consumption logic app workflow, Execute JavaScript Code action, and renamed "Body" property with closing semicolon.](./media/logic-apps-add-run-inline-code/rename-body-property-consumption.png)
+   ![Screenshot showing the Consumption logic app workflow, Execute JavaScript Code action, and renamed "Body" property with closing semicolon.](./media/add-run-javascript/rename-body-property-consumption.png)
 
    The **Execute JavaScript Code** action doesn't syntactically require a `return` statement. However, by including the `return` statement, you can more easily reference the action results later in your workflow by using the **Result** token in later actions.
 
    In this example, the code snippet returns the result by calling the `match()` function, which finds any matches in the email message body to the specified regular expression. The **Create HTML table** action then uses the **Result** token to reference the results from the **Execute JavaScript Code** action and creates a single result.
 
-   ![Screenshot showing the finished Consumption logic app workflow.](./media/logic-apps-add-run-inline-code/inline-code-complete-example-consumption.png)
+   ![Screenshot showing the finished Consumption logic app workflow.](./media/add-run-javascript/inline-code-complete-example-consumption.png)
 
 1. When you're done, save your workflow.
 
@@ -150,19 +150,19 @@ The following diagram shows the highlights from example workflow:
 
    If you start typing a recognized keyword, the autocomplete list appears so that you can select from available keywords, for example:
 
-   ![Screenshot showing the Standard workflow, Execute JavaScript Code action, and keyword autocomplete list.](./media/logic-apps-add-run-inline-code/auto-complete-standard.png)
+   ![Screenshot showing the Standard workflow, Execute JavaScript Code action, and keyword autocomplete list.](./media/add-run-javascript/auto-complete-standard.png)
 
    The following example code snippet first creates a variable named **myResult** that stores a *regular expression*, which specifies a pattern to match in input text. The code then creates a variable named **email** that stores the email message's body content from the trigger outputs.
 
-   ![Screenshot showing the Standard workflow, Execute JavaScript Code action, and example code that creates variables.](./media/logic-apps-add-run-inline-code/save-email-body-variable-standard.png)
+   ![Screenshot showing the Standard workflow, Execute JavaScript Code action, and example code that creates variables.](./media/add-run-javascript/save-email-body-variable-standard.png)
 
 1. With your cursor still in the **Code** box, follow these steps:
 
    1. In the **Code** box's lower right corner, select **Dynamic content** to open the dynamic content list.
 
    1. From the opened list, find the **When a new email arrives** section, and select the **Body** token, which references the email's message body.
 
-   ![Screenshot showing the Standard workflow, Execute JavaScript Code action, dynamic content list, and email message's "Body" property selected.](./media/logic-apps-add-run-inline-code/select-output-standard.png)
+   ![Screenshot showing the Standard workflow, Execute JavaScript Code action, dynamic content list, and email message's "Body" property selected.](./media/add-run-javascript/select-output-standard.png)
 
    The dynamic content list shows the outputs from the trigger and any preceding actions where those outputs match the input format for the edit box that's currently in focus. This list makes these outputs easier to use and reference from your workflow. For this example, the list shows the outputs from the Outlook trigger, including the email message's **Body** property.
 
@@ -175,28 +175,28 @@ The following diagram shows the highlights from example workflow:
    > and quotation marks (**""**), for example:
    >
    > `// Correct`</br>
-   > `workflowContext.actions["my.action.name"].body`
+   > `workflowContext.actions["myAction.name"].body`
    >
    > `// Incorrect`</br>
-   > `workflowContext.actions.my.action.name.body`
+   > `workflowContext.actions.myAction.name.body`
    >
    > Also, in the **Execute JavaScript Code** action, you have to add the **Actions** parameter 
    > and then add these action names to that parameter. For more information, see 
    > [Add dependencies as parameters to an Execute JavaScript Code action](#add-parameters) later in this article.
 
 1. To differentiate the email message's **Body** property that you selected from the trigger's `body` property, rename the second `body` property to `Body` instead. Add the closing semicolon (**;**) at the end to finish the code statement.
 
-   ![Screenshot showing the Standard logic app workflow, Execute JavaScript Code action, and renamed Body property with closing semicolon.](./media/logic-apps-add-run-inline-code/rename-body-property-standard.png)
+   ![Screenshot showing the Standard logic app workflow, Execute JavaScript Code action, and renamed Body property with closing semicolon.](./media/add-run-javascript/rename-body-property-standard.png)
 
    The **Execute JavaScript Code** doesn't syntactically require a `return` statement. However, by including the `return` statement, you can reference the action results later in your workflow by using the **Outputs** token in later actions.
 
    In this example, the code snippet returns the result by calling the `match()` function, which finds any matches in the email message body to the specified regular expression.
 
-   ![Screenshot showing the Standard logic app workflow and Execute JavaScript Code action with a return statement.](./media/logic-apps-add-run-inline-code/return-statement-standard.png)
+   ![Screenshot showing the Standard logic app workflow and Execute JavaScript Code action with a return statement.](./media/add-run-javascript/return-statement-standard.png)
 
    The **Create HTML table** action then uses the **Outputs** token to reference the results from the **Execute JavaScript Code** action and creates a single result.
 
-   ![Screenshot showing the finished Standard logic app workflow.](./media/logic-apps-add-run-inline-code/inline-code-complete-example-standard.png)
+   ![Screenshot showing the finished Standard logic app workflow.](./media/add-run-javascript/inline-code-complete-example-standard.png)
 
 1. When you're done, save your workflow.
 
@@ -322,11 +322,11 @@ For example, suppose the Office 365 Outlook connector's **Send approval email**
 
 ### [Consumption](#tab/consumption)
 
-![Screenshot that shows the Consumption workflow and Execute JavaScript Code action with updated example code snippet.](./media/logic-apps-add-run-inline-code/add-actions-parameter-code-snippet-consumption.png)
+![Screenshot that shows the Consumption workflow and Execute JavaScript Code action with updated example code snippet.](./media/add-run-javascript/add-actions-parameter-code-snippet-consumption.png)
 
 ### [Standard](#tab/standard)
 
-![Screenshot that shows the Standard workflow and Execute JavaScript Code action with updated example code snippet.](./media/logic-apps-add-run-inline-code/add-actions-parameter-code-snippet-standard.png)
+![Screenshot that shows the Standard workflow and Execute JavaScript Code action with updated example code snippet.](./media/add-run-javascript/add-actions-parameter-code-snippet-standard.png)
 
 ---
 
@@ -348,7 +348,7 @@ Before you start, you need the JSON name for the trigger or action in the underl
 
    For example, `Send_approval_email` is the JSON name for the **Send approval email** action.
 
-   ![Screenshot showing the action name in JSON.](./media/logic-apps-add-run-inline-code/find-action-name-json.png)
+   ![Screenshot showing the action name in JSON.](./media/add-run-javascript/find-action-name-json.png)
 
 1. To return to designer view, on the code view toolbar, select **Designer**.
 
@@ -360,7 +360,7 @@ Before you start, you need the JSON name for the trigger or action in the underl
 
    For example, `Send_approval_email` is the JSON name for the **Send approval email** action.
 
-   ![Screenshot showing the action name in JSON.](./media/logic-apps-add-run-inline-code/find-action-name-json.png)
+   ![Screenshot showing the action name in JSON.](./media/add-run-javascript/find-action-name-json.png)
 
 1. To return to designer view, on the workflow menu, select **Designer**.
 
@@ -382,11 +382,11 @@ Before you start, you need the JSON name for the trigger or action in the underl
 
 1. For this example, select the **Actions** parameter.
 
-   ![Screenshot showing the Execute JavaScript Code action with the Actions parameter selected.](./media/logic-apps-add-run-inline-code/add-actions-parameter.png)
+   ![Screenshot showing the Execute JavaScript Code action with the Actions parameter selected.](./media/add-run-javascript/add-actions-parameter.png)
 
 1. In the **Actions Item - 1** box, enter the action's JSON name.
 
-   ![Screenshot showing the Actions Item -1 box and the action's JSON name.](./media/logic-apps-add-run-inline-code/add-action-json-name.png)
+   ![Screenshot showing the Actions Item -1 box and the action's JSON name.](./media/add-run-javascript/add-action-json-name.png)
 
 1. To add another action name, select **Add new item**.