Rename file and fix links

Author: ecfan

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

@@ -1,5 +1,10 @@
 {
     "redirections": [
+        {
+            "source_path_from_root": "/articles/logic-apps/workflow-definition-language-functions-reference.md",
+            "redirect_url": "/azure/logic-apps/expression-functions-reference",
+            "redirect_document_id": true
+        },
         {
             "source_path_from_root": "/articles/logic-apps/create-workflow-with-trigger-or-action.md",
             "redirect_url": "/azure/logic-apps/add-trigger-action-workflow",

articles/logic-apps/connectors/sap-create-example-scenario-workflows.md

@@ -159,7 +159,7 @@ The SAP built-in trigger is a non-polling, Azure Functions-based trigger, not a
 
 To receive IDoc packets, which are batches or groups of IDocs, the SAP trigger doesn't need extra configuration. However, to process each item in an IDoc packet after the trigger receives the packet, you have to implement a few more steps to split the packet into individual IDocs by setting up SAP to [send IDocs in packets](https://help.sap.com/viewer/8f3819b0c24149b5959ab31070b64058/7.4.16/4ab38886549a6d8ce10000000a42189c.html). 
 
-The following example workflow shows how to extract individual IDocs from a packet by using the [`xpath()` function](../workflow-definition-language-functions-reference.md#xpath):
+The following example workflow shows how to extract individual IDocs from a packet by using the [`xpath()` function](../expression-functions-reference.md#xpath):
 
 1. Before you start, you need a Consumption or Standard logic app workflow with an SAP trigger. If your workflow doesn't already start with this trigger, follow the previous steps in this guide to [add the SAP trigger that can receive messages to your workflow](#receive-messages-sap).
 
@@ -191,7 +191,7 @@ The following example workflow shows how to extract individual IDocs from a pack
 
    1. In the action, select inside the **Value** edit box to show the options for the dynamic content list (lightning icon) and expression editor (function icon).
 
-   1. Select the function icon to open expression editor, and create the following expression using the [`xpath()` function](../workflow-definition-language-functions-reference.md#xpath):
+   1. Select the function icon to open expression editor, and create the following expression using the [`xpath()` function](../expression-functions-reference.md#xpath):
 
       `xpath(xml(triggerBody()?['Content']), 'namespace-uri(/*)')`
 

articles/logic-apps/workflow-definition-language-functions-reference.md renamed to articles/logic-apps/expression-functions-reference.md

@@ -50,7 +50,7 @@ The **For each** action works only on arrays and repeats one or more actions on
 
 * To get predictable results from operations on variables during each iteration, run the iterations sequentially. For example, when a concurrently running iteration ends, the **Increment variable**, **Decrement variable**, and **Append to variable** operations return predictable results. However, during each iteration in the concurrently running loop, these operations might return unpredictable results.
 
-* Actions in a **For each** loop use the [`item()` function](../logic-apps/workflow-definition-language-functions-reference.md#item) to reference and process each item in the array. If you specify data that's not in an array, the workflow fails.
+* Actions in a **For each** loop use the [`item()` function](expression-functions-reference.md#item) to reference and process each item in the array. If you specify data that's not in an array, the workflow fails.
 
 The following example workflow sends a daily summary for a website RSS feed. The workflow uses a **For each** action that sends an email for each new item.
 

articles/logic-apps/logic-apps-control-flow-loops.md

@@ -23,7 +23,7 @@ For example, the Azure Logic Apps includes the following XML capabilities:
 | [Transform XML](logic-apps-enterprise-integration-transform.md) | Convert or customize an XML message based on your requirements or partner requirements by using maps. |
 | [Encode and decode flat files](logic-apps-enterprise-integration-flatfile.md) | Encode or decode a flat file. <br><br>For example, SAP accepts and sends IDOC files in flat file format. Many integration platforms create XML messages, including Azure Logic Apps. So, you can create a logic app workflow that uses the flat file encoder to convert XML into flat file format. |
 | [Validate XML](logic-apps-enterprise-integration-xml-validation.md) | Validate an inbound or outbound XML message against a specific schema. |
-| [XPath](workflow-definition-language-functions-reference.md#xpath) | Enrich a message and extract specific properties from the message. You can then use the extracted properties to route the message to a destination, or an intermediary endpoint. |
+| [XPath](expression-functions-reference.md#xpath) | Enrich a message and extract specific properties from the message. You can then use the extracted properties to route the message to a destination, or an intermediary endpoint. |
 
 ## Sample
 

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

@@ -100,7 +100,7 @@ Azure Logic Apps includes rich capabilities for advanced control flow, such as c
 You can access, convert, and transform multiple content types by using the many functions in the Azure Logic Apps [workflow definition language](logic-apps-workflow-definition-language.md). For example, you can convert between a string, JSON, and XML with the `@json()` and `@xml()` workflow expressions. Azure Logic Apps preserves content types to support content transfer in a lossless manner between services.
 
 * [Handle content types in Azure Logic Apps](logic-apps-content-type.md), such as `application/`, `application/octet-stream`, and `multipart/formdata`
-* [Reference guide to using functions in expressions for Azure Logic Apps and Power Automate](workflow-definition-language-functions-reference.md)
+* [Reference guide for expression functions in Azure Logic Apps and Power Automate](expression-functions-reference.md)
 * [Workflow Definition Language schema for Azure Logic Apps](logic-apps-workflow-definition-language.md)
 
 ## Create custom APIs and connectors

articles/logic-apps/logic-apps-examples-and-scenarios.md

@@ -174,8 +174,7 @@ With JSON, you can have literal values that exist at design time, for example:
 You can also have values that don't exist until run time. To represent these values, you can use *expressions*, which are evaluated at run time. An expression is a sequence that can contain one or more [functions](#functions), 
 [operators](#operators), [variables](logic-apps-create-variables-store-values.md), explicit values, or constants. In your workflow definition, you can use an expression anywhere in a JSON string value by prefixing the expression with the at-sign (\@). When evaluating an expression that represents a JSON value, the expression body is extracted by removing the \@ character, and always results in another JSON value.
 
-For example, for the previously defined `customerName` property, you can get the property value by using the [parameters()](workflow-definition-language-functions-reference.md#parameters) 
-function in an expression and assign that value to the `accountName` property:
+For example, for the previously defined `customerName` property, you can get the property value by using the [**parameters()** function](expression-functions-reference.md#parameters) in an expression and assign that value to the `accountName` property:
 
 ```json
 "customerName": "Sophia Owen",
@@ -295,9 +294,9 @@ In [expressions](#expressions) and [functions](#functions), operators perform sp
 
 ## Functions
 
-Some expressions get their values from runtime actions that might not yet exist when your workflow definition starts to run. To reference or work with these values in expressions, you can use [*functions*](../logic-apps/workflow-definition-language-functions-reference.md) that the Workflow Definition Language provides.
+Some expressions get their values from runtime actions that might not yet exist when your workflow definition starts to run. To reference or work with these values in expressions, you can use [*functions*](expression-functions-reference.md) that the Workflow Definition Language provides.
 
-## Next steps
+## Related content
 
-* Learn about [Workflow Definition Language actions and triggers](logic-apps-workflow-actions-triggers.md)
-* Learn about programmatically creating and managing logic apps with the [Workflow REST API](/rest/api/logic/workflows)
+* [Workflow Definition Language actions and triggers](logic-apps-workflow-actions-triggers.md)
+* [Workflow REST API](/rest/api/logic/workflows)

articles/logic-apps/logic-apps-workflow-definition-language.md

@@ -50,7 +50,7 @@ If you set the `Content-Type` header to `application/octet-stream`, you also mig
 
 ## Base64 encode content
 
-Before you [base64 encode](workflow-definition-language-functions-reference.md#base64) content to a string, make sure that you [convert the text to UTF-8](#convert-payload-encoding). Otherwise, characters might return corrupted.
+Before you [base64 encode](expression-functions-reference.md#base64) content to a string, make sure that you [convert the text to UTF-8](#convert-payload-encoding). Otherwise, characters might return corrupted.
 
 Next, convert any .NET-supported encoding to another .NET-supported encoding. Review the [Azure Functions code example](#azure-functions-version) or the [.NET code example](#net-version):
 
@@ -211,7 +211,7 @@ Example output:
 
 If you need to send a non-Unicode payload from your workflow, do the steps for [converting the payload to UTF-8](#convert-payload-encoding) in reverse. Keep the text in UTF-8 as long as possible within your system. Next, use the same function to convert the base64-encoded UTF-8 characters to the required encoding. Then, apply base64 decoding to the text, and send your payload.
 
-When you consume the return value from Azure Functions, make sure to use the [**base64ToBinary** function](workflow-definition-language-functions-reference.md#base64tobinary), not the **base64ToString** function.
+When you consume the return value from Azure Functions, make sure to use the [**base64ToBinary** function](expression-functions-reference.md#base64tobinary), not the **base64ToString** function.
 
 ## Convert payloads for AS2
 

articles/logic-apps/support-non-unicode-character-encoding.md

@@ -567,8 +567,8 @@ items:
     items:
       - name: Trigger and action types reference
         href: logic-apps-workflow-actions-triggers.md
-      - name: Functions reference
-        href: workflow-definition-language-functions-reference.md
+      - name: Reference for expression functions
+        href: expression-functions-reference.md
   - name: Standard Automated Test Framework
     items:
       - name: Standard Automated Test SDK