From 9184793d5e6e64fa8ef936e87694af6939f7e05c Mon Sep 17 00:00:00 2001 From: Yuto Date: Thu, 9 Nov 2023 10:15:22 +0900 Subject: [PATCH] Update faqs.md We wanted to make sure the flow categories: in context flow, parent flow, and child flow for the licensing clearer. --- power-platform/admin/power-automate-licensing/faqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/power-platform/admin/power-automate-licensing/faqs.md b/power-platform/admin/power-automate-licensing/faqs.md index 8040271310..ffaa1de4a3 100644 --- a/power-platform/admin/power-automate-licensing/faqs.md +++ b/power-platform/admin/power-automate-licensing/faqs.md @@ -69,7 +69,7 @@ In the following screenshot, all cloud flows are covered by one Process license, Core business processes can vary in size and complexity, ranging from small-scale initiatives to large-scale endeavors spanning multiple flows interconnected by shared data sources. For example, invoice processing process has multiple flows handling an invoice from creation through approvals to payment. All the flows are part of one business process as they are all handling an invoice through multiple steps to closure. You only need one Process license for a core business process. This encourages microservices architecture best practices where flows can be small with fine grained functionality resulting in better maintainability. Identify the flow that starts the process and assign a Process license to that flow. Parent and child flows of the flow with Process license are covered by the Process license. These flows can be in the same solution or in different solution. -Non parent/child flows can manually be associated to the flow with a Process license. These flows must be in the same solution and be using the same data sources. +Non parent/child flows, which are in context flows, can manually be associated to the flow with a Process license. These in context flows must be in the same solution and be using the same data sources. The flows organized as parent, child flows, in context flows are all treated as one process with one Process license assigned to the main flow and share Power Platform Request limits of Process license.