You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can set up pipelines that provision infrastructure and manage the CI/CD process for business process stages mapped to a Standard workflow's operations in different environments, such as development, test, and production, without having to rebuild and remap the stages to workflow operations aznd rebuild logic app projects, you can set up continuous integration (CI) and continuous deployment (CD) for your business processes and Standard logic app workflows.
15
+
You can set up pipelines that provision infrastructure and manage the CI/CD process for business process stages mapped to a Standard workflow's operations in different environments, such as development, test, and production, without having to rebuild and remap the stages to workflow operations and rebuild logic app projects, you can set up continuous integration (CI) and continuous deployment (CD) for your business processes and Standard logic app workflows.
16
16
17
17
This guide shows how to complete the following tasks:
18
18
@@ -284,7 +284,7 @@ Now, update your **business-process-pipelines-variables.yml** file to use the pr
284
284
285
285
1. In Visual Studio Code, go to your logic app project, find the **pipelines** folder, and open the file named **business-process-pipelines-variables.yml** at the end of this path:
The **business-process-pipelines-variables.yml** file contains a node named **`businessProcessMapping`**. This node includes references to your business process stage mappings and specific logic apps. These references contain paths with Azure subscription IDs and names for resource groups and logic apps.
290
290
@@ -334,7 +334,7 @@ Azure Business Process Tracking uses Azure Data Explorer as the backend data sto
334
334
335
335
1. For **Path**, find and select the **infrastucture-business-process-pipeline.yaml** file at the following location:
0 commit comments