Study guide

11.3 BPF Action Steps, Workflows & Cloud Flow Execution

Microsoft Power Platform Functional Consultant PL-200

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Dataverse Tables, Relationships & Core Columns

1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx

2 Chapter 2: Dataverse Data Management & Governance

2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates

3 Chapter 3: Dataverse Security Model & Access Control

3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models

4 Chapter 4: Model-Driven App Fundamentals & Information Architecture

4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters

5 Chapter 5: Advanced Model-Driven App Components & Custom Pages

5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles

6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations

6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps

7 Chapter 7: Power Pages Site Design, Navigation & Content

7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets

8 Chapter 8: Power Pages Data Integration, Forms & Web Roles

8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration

9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers

9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References

10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls

10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls

11 Chapter 11: Business Process Flows & Guided Processes

11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle

12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility

12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics

13 Chapter 13: Power Platform Environment Architecture & Security

13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications

14 Chapter 14: Application Lifecycle Management (ALM) & Solutions

14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices

15 Chapter 15: Enterprise Interoperability & Service Integration

15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates

16 Chapter 16: Copilot, AI Capabilities & Exam Strategy

16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis

11.3 BPF Action Steps, Workflows & Cloud Flow Execution

Key Takeaways Explain This Topic AI

Business Process Flows can execute automated business logic using Classic On-Demand Workflows and Modern Instant Cloud Flows (Flow Steps).

Classic workflows can trigger automatically on BPF lifecycle events: Stage Entry, Stage Exit, Process Applied, Process Completed, and Process Abandoned.

Flow Steps render as interactive, actionable buttons directly within a stage flyout, allowing users to trigger Power Automate cloud flows on demand.

Cloud flows integrated into BPF steps use the 'When a business process flow step is run' trigger, receiving contextual parameters including BPF Instance ID, Stage ID, and Primary Record GUID.

Synchronous real-time classic workflows can validate stage criteria and cancel transitions with an error, whereas cloud flows execute asynchronously.

Last updated: August 2026

BPF Action Steps, Workflows & Cloud Flow Execution

A Business Process Flow is more than a passive visual checklist; it serves as an active orchestration engine. By binding workflow logic and cloud automation directly to stages and user actions, functional consultants can eliminate manual administrative overhead, trigger background integrations, and enforce complex validation checks during process execution.

For the PL-200: Microsoft Power Platform Functional Consultant exam, you must master the two primary automation mechanisms available within BPFs: Classic Workflows (triggered automatically upon stage transitions) and Power Automate Instant Cloud Flows (triggered interactively via Flow Steps / Action Steps).

1. Classic Workflow Integration in BPF Stages

Dataverse allows consultants to attach classic on-demand workflows to specific execution events within a Business Process Flow definition. +-----------------------------------------------------------------------------+

  • | BPF WORKFLOW TRIGGER EXECUTION HOOKS |
  • | |
  • | [ PROCESS APPLIED ] ---> Triggered when BPF is instantiated on a record |
  • | | |
  • | v |
  • | [ STAGE 1: QUALIFY ] |
  • | - STAGE ENTRY TRIGGER ---> Runs workflow on entering Qualify |
  • | - STAGE EXIT TRIGGER ---> Runs workflow on leaving Qualify |
  • | | |
  • | v |
  • | [ STAGE 2: DEVELOP ] |
  • | - STAGE ENTRY TRIGGER ---> Runs workflow on entering Develop |
  • | - STAGE EXIT TRIGGER ---> Runs workflow on leaving Develop |
  • | | |
  • | v |
  • | [ PROCESS COMPLETED ] ---> Triggered when final stage is finished |
  • | [ PROCESS ABANDONED ] ---> Triggered when user abandons the process |
  • +-----------------------------------------------------------------------------+
  • Workflow Execution Triggers

When configuring a stage in the BPF designer, makers can add a Workflow component and configure the trigger event:

Stage Entry: Fires automatically the instant the stage becomes the active stage (either upon advancing forward or stepping backward).

Stage Exit: Fires automatically when the user advances out of the stage into the subsequent milestone.

Global Process Events: Workflows can also be bound to the entire BPF lifecycle, firing when the process is first Applied , when it is marked Completed (Finished) , or when it is Abandoned .

Prerequisites for Classic BPF Workflows

To be selectable inside the BPF designer, a classic workflow must satisfy two strict criteria:

On-Demand Property: The workflow definition must have the setting "As an on-demand process" checked.

Entity Scope: The workflow must be defined for the same primary entity as the stage where it is being added (or configured as a Global workflow).

Real-Time (Sync) vs. Background (Async) Execution

Real-Time Workflows (Synchronous): Execute within the same database transaction as the stage navigation. If a real-time workflow encounters a "Stop Workflow as Cancelled" step with a custom error message, the entire stage transition is rolled back, displaying the error message in an infobar and keeping the user in the current stage. This makes real-time workflows ideal for complex server-side stage gating validations .

Background Workflows (Asynchronous): Execute queued tasks in the background without delaying the user interface (e.g., sending email notifications or recalculating financial aggregates).

2. Power Automate Cloud Flows in BPFs (Action Steps / Flow Steps)

Modern Power Platform implementations leverage Power Automate Cloud Flows to deliver interactive, on-demand automation directly from the BPF header using the Flow Step (Action Step) component. +-----------------------------------------------------------------------------+

  • | FLOW STEP (ACTION STEP) USER INTERFACE |
  • | |
  • | +---------------------------------------------------------------------+ |
  • | | STAGE: [ DEVELOP ] | |
  • | | ----------------------------------------------------------------- | |
  • | | Data Step: Proposed Budget ($) [ $150,000 ] | |
  • | | Data Step: Delivery Timeline [ 3 Months ] | |
  • | | | |
  • | | Flow Step: [ Run Credit Check & Risk Assessment ] <--- (BUTTON) | |
  • | | Status: Succeeded (Last Run: Today, 10:45 AM) | |
  • | | | |
  • | | [ Next Stage ] | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+
  • Adding a Flow Step to a Stage

In the BPF designer, drag a Flow Step (Action Step) from the Components pane into the target stage.

In the properties pane, select an existing cloud flow or click Create New .

Enter a clear, user-friendly Display Name for the button (e.g., "Request Supervisor Discount Approval" or "Generate Proposal Document" ).

Save and Activate the Business Process Flow.

The BPF Cloud Flow Trigger & Contextual Payloads

Cloud flows designed for BPF Flow Steps must utilize the dedicated trigger: When a business process flow step is run (from the Microsoft Dataverse connector). +-----------------------------------------------------------------------------+

  • | BPF CLOUD FLOW CONTEXTUAL DATA PIPELINE |
  • | |
  • | [USER CLICKS BUTTON IN BPF FLYOUT] |
  • | | |
  • | v |
  • | [TRIGGER: 'When a business process flow step is run'] |
  • | - Provides automatic contextual dynamic content: |
  • | * bpf_instance_id: Unique GUID of the running BPF record |
  • | * bpf_stage_id: GUID of the current active stage |
  • | * bpf_stage_name: Display name of the active stage |
  • | * bpf_process_id: GUID of the BPF definition |
  • | * entity_record_id: GUID of the underlying business row |
  • | * entity_name: Logical schema name of the entity |
  • | | |
  • | v |
  • | [CLOUD FLOW EXECUTES ACTIONS] |
  • | - Queries Dataverse record using entity_record_id |
  • | - Sends Teams Adaptive Card for executive approval |
  • | - Updates Dataverse row status or advances BPF via Web API |
  • | | |
  • | v |
  • | [RETURNS STATUS TO BPF UI: 'Processing' -> 'Succeeded' / 'Failed'] |
  • +-----------------------------------------------------------------------------+
  • Dynamic Context Parameters Available in the Flow

When triggered, the cloud flow automatically receives essential metadata describing the execution environment:

Entity record identifier ( entity_record_id ): The primary key GUID of the active record on which the BPF is displayed (e.g., the specific Opportunity or Case ID).

Business Process Flow instance identifier ( bpf_instance_id ): The GUID of the record in the custom BPF table.

Active Stage identifier ( bpf_stage_id ): The GUID of the current ProcessStage .

Stage Name and Process Name : Human-readable string names of the active stage and process definition.

Runtime UX State Progression

When an end user clicks the Flow Step button in model-driven apps:

The button state changes immediately to Processing... , accompanied by a loading spinner.

The cloud flow runs asynchronously in Power Automate.

Upon completion, the button updates to display Succeeded (or Failed with error details), and records the timestamp of the last execution.