11.3 BPF Action Steps, Workflows & Cloud Flow Execution
Key Takeaways
- 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.
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 specificOpportunityorCaseID).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 currentProcessStage.Stage NameandProcess 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(orFailedwith error details), and records the timestamp of the last execution.
A functional consultant is designing a Business Process Flow for the 'Loan Application' table. The credit committee mandates that when a loan officer attempts to exit the 'Underwriting' stage, the system must synchronously verify that the applicant's debt-to-income ratio is below 40%. If the ratio exceeds 40%, the system must immediately block the stage transition and display a custom error message on the screen. Which automation mechanism should the consultant configure?
A maker wants to add an interactive button inside a BPF stage flyout that allows customer support representatives to generate and email a PDF warranty certificate to the customer on demand. The maker creates an Instant Cloud Flow in Power Automate. Which trigger must the cloud flow use to be available for selection inside the BPF Flow Step configuration?
A consultant configures an on-demand classic workflow to send a notification email when a sales deal enters the 'Negotiation' stage. However, when opening the BPF designer and trying to add the workflow to Stage 3 (Opportunity entity), the workflow does not appear in the selection drop-down list. What are the two most likely reasons for this issue?
An instant cloud flow is triggered from a BPF Flow Step button on a Case record. Inside the flow, the maker needs to retrieve additional columns from the specific Case record where the button was clicked. Which dynamic content parameter supplied by the BPF trigger provides the unique identifier of the Case record?