Resolve PG feedback

Author: ecfan

articles/business-process-tracking/create-business-process.md

@@ -17,7 +17,7 @@ ms.date: 06/07/2024
 
 To add business context around the Azure resources in an integration solution, you can visualize business processes flows for the tasks implemented by these resources. A business process is a series of stages that represent the tasks that flow through a real-world business scenario. This business process also specifies a single business identifer or *transaction ID*, such as a ticket number, order number, case number, and so on, to identify a transaction that exists across all the stages in the business process and to correlate those stages together.
 
-When you add a stage to your business process, you can also define other business properties to capture and track as that data moves through each stage. You can then later map the transaction ID and other properties to specific operations and data outputs in Standard logic app workflows. For more information, see [What is Business Process Tracking](overview.md)?
+When you add a stage to your business process, you can also define other business property values to capture as data moves through each stage. You can then later map the transaction ID and other properties to specific operations and data outputs in Standard logic app workflows. For more information, see [What is Business Process Tracking](overview.md)?
 
 For example, suppose you're a developer or business analyst at a power company. Your company's customer service team has the following business process to resolve a customer ticket for a power outage:
 
@@ -51,7 +51,7 @@ After you define a business process, you can then map each stage to actual Azure
 
 - An existing or new [Azure Data Explorer cluster and database](/azure/data-explorer/create-cluster-and-database)
 
-  This Azure resource is required to create a business process. Your business process uses this database to store the transactions and business property values that you want to capture as the real-time data moves through your workflows at run time. When you create a business process, you specify the cluster, database, and table to use for storing the data that you want to capture.
+  This Azure resource is required to create, deploy, and store specified data in a business process. Your business process uses this database to store the transactions and business property values that you want to capture as real-time data moves through your workflows at run time. When you create a business process, you specify the cluster, database, and table to use for storing the data that you want.
 
   > [!NOTE]
   >
@@ -87,7 +87,7 @@ After you define a business process, you can then map each stage to actual Azure
 
    | Property | Required | Value | Description |
    |----------|----------|-------|-------------|
-   | **Transaction ID** | Yes | <*transaction-ID*> | This important and unique ID identifies a transaction, such as an order number, ticket number, case number, or another similar business identifier that's available across all stages in your business process. <br><br>This example uses the transaction ID named **TicketNumber** to correlate events across the different systems in the example business process, which include CRM, Work Order Management, and Marketing. <br><br>**Note**: Business Process Tracking automatically includes and captures the transaction timestamp, so you don't have to separately add this value to capture and track. Although you can define only a single transaction ID when you create a business process, you can later define other business properties in each stage to capture and track. |
+   | **Transaction ID** | Yes | <*transaction-ID*> | This important and unique ID identifies a transaction, such as an order number, ticket number, case number, or another similar business identifier that's available across all stages in your business process. <br><br>This example uses the transaction ID named **TicketNumber** to correlate events across the different systems in the example business process, which include CRM, Work Order Management, and Marketing. <br><br>**Note**: Business Process Tracking automatically includes and records the transaction timestamp so that you don't have to separately add this value. Although you can define only a single transaction ID when you create a business process, you can later define other business properties in each stage that you want to record. |
    | **Data type** | Yes | <*transacton-ID-data-type*> | The data type for your transaction ID: **String** or **Integer**. <br><br>This example uses the **Integer** data type. |
 
    The following example shows the sample transaction ID:
@@ -106,9 +106,9 @@ After you define a business process, you can then map each stage to actual Azure
 
 1. When you're done, select **Create**.
 
-   When deployment completes, Azure opens the **Overview** page for your **Business Process** resource.
+   After the Azure portal completes deployment for your new **Business Process** resource, the portal automatically opens the resource's **Overview** page.
 
-1. Now, add the stages for your business process.
+1. Now, continue on to add the stages for your business process.
 
 <a name="add-stage"></a>
 
@@ -143,17 +143,23 @@ After you create your business process, add the stages for that process. For exa
 
    :::image type="content" source="media/create-business-process/add-stage-quick.png" alt-text="Screenshot shows pane named Add stage with stage name, description, and properties to track." lightbox="media/create-business-process/add-stage.png":::
 
-   In the **Properties to track** table, on the **Success** tab, the transaction ID that you previously defined when you created the business process automatically appears. This value is required and must exist for a successfully completed stage. The **Success** tab can specify other business property values to capture from a successfully completed stage. On the **Failure** tab, you can specify any business property values to capture from a failed stage.
+   In the **Properties to track** table, on the **Success** tab, your previously defined transaction ID is automatically included. This value is required for correlation across stages and workflows. 
 
-   To define other business property values that you want to capture and track for this stage, follow these steps:
+   On the **Success** and **Failure** tabs, you can optionally define and map other business property values that you want to record. You can use these property values to correspondingly identify a successful or failed stage, which is left entirely to your interpretation, business scenarios, or needs.
+
+   - **Success** tab: Define and map other business property values to identify and record from a successful stage.
+
+   - **Failure** tab: Define and map other business property values to identify and record from a failed stage.
+
+   To define other business property values to use for this stage, follow these steps:
 
    1. Under **Properties to track**, select **Success** or **Failure** as appropriate.
 
    1. Under the **Properties to track** table, select **Add property**.
 
    1. Enter the property name and type, which is either a **String** or **Integer**.
 
-   For example, this stage specifies a few more properties, such as **CustomerName**, **CustomerEmail**, and **CustomerPhone**, to capture from a successfully completed stage:
+   For example, this stage specifies a few more properties, such as **CustomerName**, **CustomerEmail**, and **CustomerPhone**, to record from a successfully completed stage:
 
    :::image type="content" source="media/create-business-process/add-properties.png" alt-text="Screenshot shows pane named Add stage with stage name, description, and more properties to track." lightbox="media/create-business-process/add-properties.png":::
 
@@ -165,7 +171,7 @@ After you create your business process, add the stages for that process. For exa
 
    - Under the last stage, select the plus sign (**+**) for **Add a stage**.
 
-   - Between stages, select the plus sign (**+**), and then select either **Add a stage** or **Add a parallel stage**, which creates a decision branch in your business process.
+   - Between stages, select the plus sign (**+**), and then select either **Add a stage** or **Add a parallel stage**, which creates a branch in your business process.
 
    > [!TIP]
    >

articles/business-process-tracking/deploy-business-process.md

@@ -31,14 +31,16 @@ After you map your business process stages to the operations and outputs in Stan
 
 - The Azure Data Explorer database associated with your business process must be online.
 
-  Deployment uses the database table that you selected during business process creation to add and store the data captured from the workflow run. Deployment also causes all the participating Standard logic app resources to automatically restart.
+  Deployment uses the database table that you selected during business process creation to store recorded data from the workflow run.
 
 <a name="deploy-business-process-tracking"></a>
 
 ## Deploy business process and tracking profile
 
 1. In the [Azure portal](https://portal.azure.com), open your business process in the editor, if not already open.
 
+1. Before you deploy, make sure that you're ready for all participating Standard logic app workflows to restart when deployment begins.
+
 1. On the process editor toolbar, select **Deploy**.
 
    :::image type="content" source="media/deploy-business-process/deploy.png" alt-text="Screenshot shows Azure portal, business process, and process designer toolbar with Deploy selected." lightbox="media/deploy-business-process/deploy.png":::
@@ -55,7 +57,7 @@ After you map your business process stages to the operations and outputs in Stan
 
 ## View recorded transactions
 
-After the mapped Standard logic app workflows run and emit the data that you specified to capture, you can view the recorded transactions.
+After the mapped Standard logic app workflows run and emit the data that you specified for collection, you can view the recorded transactions.
 
 1. In the [Azure portal](https://portal.azure.com), open your business process.
 

articles/business-process-tracking/manage-business-process.md

@@ -38,7 +38,7 @@ A business process exists in one of the following states:
 | State | Description |
 |------|-------------|
 | Draft | An unsaved or saved business process before deployment. |
-| Deployed | A business process that captures data during workflow run time. |
+| Deployed | A business process that records specified data during workflow run time. |
 | Deployed with pending changes | A business process that has both a deployed version and version with pending changes. |
 
 <a name="edit-process-or-stage"></a>
@@ -73,7 +73,7 @@ The following steps remove any pending changes for a deployed business process,
 
 ## Undeploy a business process
 
-The following steps remove only the deployment artifacts and tracking profile for a deployed business process. This action leaves the business process unchanged, but the process no longer captures and tracks data. Any previously captured data remains stored in your Azure Data Explorer database.
+The following steps remove only the deployment artifacts and tracking profile for a deployed business process. This action leaves the business process unchanged, but the process no longer records and tracks the specified data. Any previously recorded data remains stored in your Azure Data Explorer database.
 
 1. In the [Azure portal](https://portal.azure.com), find and open your business process.
 

articles/business-process-tracking/map-business-process-workflow.md

@@ -33,8 +33,6 @@ After you finish creating your business process, you can map each stage, transac
 
 - All the Standard logic app workflows that you want to map your business process stages. For more information, see [What is Azure Logic Apps](../logic-apps/logic-apps-overview.md)?
 
-- The Azure Data Explorer database associated with your business process must be online to store your mapping information.
-
 <a name="map-stage"></a>
 
 ## Map a business process stage
@@ -126,13 +124,17 @@ In the **Properties** section, follow these steps to map each property's value t
 
 1. On the **Edit stage** pane, select **Save stage**.
 
-   The platform sends the information to your database in Azure Data Explorer.
+1. Validate your mappings, or continue mapping any other stages that you might have.
 
 ## Validate mappings
 
-As you map each stage, you can check your mappings as build your business process, rather than wait until deployment, to reveal any errors or problems with your mappings.
+As you build your business process, you can check your mappings before you deploy. That way, you can find errors or problems earlier when your process is less complex and is easier to troubleshoot.
+
+If you wait until you finish or deploy, and your process is long or complex, you might find that your process has more errors than expected, which might take longer to resolve or prove difficult to troubleshoot.
+
+1. Before you validate your mappings, make sure to completely map all existing stages. Otherwise, unmapped stages generate errors.
 
-- On the editor toolbar, select **Validate**.
+1. When you're ready, on the editor toolbar, select **Validate**.
 
   The Azure portal shows notifications for any errors or problems that exist.
 

articles/business-process-tracking/overview.md

@@ -5,7 +5,7 @@ ms.service: logic-apps
 ms.topic: overview
 ms.reviewer: estfan, azla
 ms.date: 06/07/2024
-# CustomerIntent: As a developer or business analyst with a solution that has multiple or different Azure resources that integrate various services and systems, I want a way to visualize my organization's business processes and map them to the actual Azure resources that implement those use cases. For our business, I also want to capture key business data that moves through these resources to gain better insight about how our solutions perform.
+# CustomerIntent: As a developer or business analyst with a solution that has multiple or different Azure resources that integrate various services and systems, I want a way to visualize my organization's business processes and map them to the actual Azure resources that implement those use cases. For our business, I also want to record key business data that moves through these resources to gain better insight about how our solutions perform.
 ---
 
 # What is Business Process Tracking? (Preview)
@@ -15,7 +15,7 @@ ms.date: 06/07/2024
 > This capability is in public preview and isn't ready yet for production use. For more information, see the 
 > [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-As a developer or business analyst working on solutions that integrate services and systems using various Azure resources, you might have difficulties visualizing the relationship between the technical components in your solution and your business scenario. To include business context about the Azure resources in your solution, you can build business processes that visually represent the business logic implemented by these resources. A business process is a series of stages that represent the tasks that flow through a real-world business scenario.
+As a developer or business analyst working on solutions that integrate services and systems using various Azure resources, you might have difficulties visualizing the relationship between the technical components in your solution and your business scenario. To include business context about the Azure resources in your solution, you can build business processes that visually represent the business logic implemented by these resources. In Business Process Tracking, a business process is a series of stages that represent the tasks flowing through real-world business scenario.
 
 For example, suppose you're a developer or business analyst at a power company, and you work on a team that creates integration solutions. Your team is updating a solution for a work order processor service that's implemented by multiple Standard logic apps and their workflows. Your company's customer service team uses the following business process to resolve a customer ticket for a power outage:
 
@@ -31,15 +31,15 @@ This capability lets you decouple the business process design from your implemen
 
 ## Business process design and tracking
 
-When you create a **Business Process** resource in Azure, you define a single business identifier or *transaction ID*, such as an order number, case number, or ticket number, to identify a transaction that exists across all business process stages so you can correlate these stages together.
+When you create a **Business Process** resource in Azure, you define a single business identifier or *transaction ID*, such as an order number, case number, or ticket number, to identify a transaction that exists across all business process stages so you can correlate these stages and data together.
 
 :::image type="content" source="media/overview/define-transaction-id.png" alt-text="Screenshot shows Azure portal, the page named Create a business process page, and transaction ID details." lightbox="media/overview/define-transaction-id.png":::
 
 After you create your resource, you can use the process editor to design the stages in your business process, for example:
 
 :::image type="content" source="media/create-business-process/business-process-stages-complete.png" alt-text="Screenshot shows process editor with business process stages." lightbox="media/create-business-process/business-process-stages-complete.png":::
 
-To record business data from each stage as that data flows through deployed Azure resources at run time, you can specify more key business properties and values to capture. When you create a stage, you specify these business properties. For example, the **Create_ticket** stage defines the following business property values to capture in your deployed resources:
+To capture business data from each stage as real-time data flows through deployed Azure resources at run time, you can specify other key business property values that you want to record and store. When you create a stage, you define these business properties and their data sources. For example, the **Create_ticket** stage defines the following business property values to record from deployed Azure resources:
 
 :::image type="content" source="media/overview/define-business-properties.png" alt-text="Screenshot shows Edit stage pane with specified business properties to capture and track." lightbox="media/overview/define-business-properties.png":::
 
@@ -72,15 +72,13 @@ To help you organize and manage the deployed Azure resources that you use in you
 
 - Business process design, tracking, and deployment are currently available only in the Azure portal. No capability currently exists to export and import tracking profiles.
 
-- This preview release currently doesn't include application monitoring.
-
 - Business process mapping and tracking currently support only Standard logic app resources and stateful workflows in Azure Logic Apps. Stateless workflows currently aren't supported.
 
   If you have business scenarios or use cases that require stateless workflows, use the product feedback link to share these scenarios and use cases. 
 
 - This preview release is currently optimized for speed.
 
-  If you have feedback about workload performance, use the product feedback link to share your input and results from representative loads to help improve this aspect.
+  If you have feedback about workload reliability or performance, use the product feedback link to share your input and results from representative workloads to help improve this aspect.
 
 ## Pricing information
 

articles/integration-environments/overview.md

@@ -79,6 +79,10 @@ Azure Integration Environments doesn't incur charges during preview. However, wh
 
 Azure Data Explorer incurs charges, based on the selected pricing option. For more information, see [Azure Data Explorer pricing](https://azure.microsoft.com/pricing/details/data-explorer/#pricing).
 
+## Limitations and known issues
+
+- This preview release currently doesn't include application monitoring.
+
 ## Related content
 
 [Create an integration environment](create-integration-environment.md)