|
1 | 1 | ---
|
2 |
| -title: Create business processes to add business context |
3 |
| -description: Model a business process to add business context about transactions in Standard workflows created with Azure Logic Apps. |
| 2 | +title: Create business processes |
| 3 | +description: Model a business process to visualize and map transactions to Azure resources, such as Standard workflows in Azure Logic Apps. |
4 | 4 | ms.service: azure-business-process-tracking
|
5 | 5 | ms.topic: how-to
|
6 | 6 | ms.reviewer: estfan, azla
|
7 | 7 | ms.date: 06/07/2024
|
| 8 | + |
8 | 9 | # CustomerIntent: As a business analyst or business SME, I want a way to visualize my organization's business processes so I can map them to the actual resources that implement these business use cases and scenarios.
|
9 | 10 | ---
|
10 | 11 |
|
11 |
| -# Create a business process to add business context to Azure resources (Preview) |
| 12 | +# Create a business process to add business context about Azure resources using Azure Business Process Tracking (Preview) |
12 | 13 |
|
13 | 14 | > [!IMPORTANT]
|
14 | 15 | >
|
15 | 16 | > This capability is in public preview and isn't ready yet for production use. For more information, see the
|
16 | 17 | > [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
|
17 | 18 |
|
18 |
| -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. |
| 19 | +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. In Azure Business Process Tracking, 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. |
19 | 20 |
|
20 |
| -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)? |
| 21 | +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 Azure Business Process Tracking](overview.md)? |
21 | 22 |
|
22 | 23 | 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:
|
23 | 24 |
|
24 | 25 | :::image type="content" source="media/create-business-process/business-process-stages-example.png" alt-text="Conceptual diagram shows example power outage business process stages for customer service at a power company." lightbox="media/create-business-process/business-process-stages-example.png":::
|
25 | 26 |
|
26 | 27 | After you create a **Business Process** resource in Azure, you can use the process editor to create a flow chart that visually describes this business process, for example:
|
27 | 28 |
|
28 |
| -:::image type="content" source="media/create-business-process/business-process-stages-complete.png" alt-text="Screenshot shows process editor for business process tracking feature in an integration environment." lightbox="media/create-business-process/business-process-stages-complete.png"::: |
| 29 | +:::image type="content" source="media/create-business-process/business-process-stages-complete.png" alt-text="Screenshot shows process editor for Azure Business Process Tracking." lightbox="media/create-business-process/business-process-stages-complete.png"::: |
29 | 30 |
|
30 | 31 | > [!NOTE]
|
31 | 32 | >
|
@@ -55,7 +56,7 @@ After you define a business process, you can then map each stage to actual Azure
|
55 | 56 |
|
56 | 57 | > [!NOTE]
|
57 | 58 | >
|
58 |
| - > Although Business Process Tracking doesn't incur charges during preview, Azure Data |
| 59 | + > Although Azure Business Process Tracking doesn't incur charges during preview, Azure Data |
59 | 60 | > Explorer incurs charges, based on the selected pricing option. For more information, see
|
60 | 61 | > [Azure Data Explorer pricing](https://azure.microsoft.com/pricing/details/data-explorer/#pricing).
|
61 | 62 |
|
@@ -87,7 +88,7 @@ After you define a business process, you can then map each stage to actual Azure
|
87 | 88 |
|
88 | 89 | | Property | Required | Value | Description |
|
89 | 90 | |----------|----------|-------|-------------|
|
90 |
| - | **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. | |
| 91 | + | **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**: Azure 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. | |
91 | 92 | | **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. |
|
92 | 93 |
|
93 | 94 | The following example shows the sample transaction ID:
|
|
0 commit comments