Study guide

11.4 BPF Security Roles, Order & Process Lifecycle

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.4 BPF Security Roles, Order & Process Lifecycle

Key Takeaways Explain This Topic AI

Access to Business Process Flows is governed by standard Dataverse Security Roles granting Create, Read, Write, and Delete privileges on the auto-generated custom BPF table.

When multiple BPFs exist on a single table, the Order Process Flow setting establishes evaluation precedence: on record creation, the highest-ranked BPF for which the user possesses Read privileges is automatically applied.

Every BPF instance transitions through a three-state lifecycle: Active ( statecode = 0 ), Finished ( statecode = 1, statuscode = 2 ), and Abandoned ( statecode = 1, statuscode = 3 ).

Users with appropriate security permissions can manually switch between active BPF definitions on a record using the 'Switch Process' command bar action.

The Client API ( formContext.data.process ) provides rich programmatic control to query active stages, advance steps, switch processes, and attach event listeners via JavaScript.

Last updated: August 2026

BPF Security Roles, Order & Process Lifecycle

In complex enterprise environments, organizations frequently maintain multiple distinct business processes for the same underlying table. A global organization might operate a Standard SMB Sales Process , an Enterprise Strategic Sales Process , and a Government Procurement Process all anchored to the Opportunity table. Controlling which users have access to specific processes, determining which process applies automatically upon record creation, managing process state transitions, and automating process navigation via client-side scripting are fundamental competencies for the functional consultant.

For the PL-200: Microsoft Power Platform Functional Consultant exam, you must master BPF security role administration, process order precedence rules, the three lifecycle states, and the Client API ( formContext.data.process ) object model.

1. BPF Security Roles & Access Governance

Because every Business Process Flow in Dataverse is stored as an autonomous custom table, access control leverages the standard Dataverse Role-Based Access Control (RBAC) security architecture. +-----------------------------------------------------------------------------+

  • | BPF SECURITY PRIVILEGE MODEL |
  • | |
  • | +---------------------------------------------------------------------+ |
  • | | DATAVERSE SECURITY ROLE: 'SALES REP' | |
  • | +---------------------------------------------------------------------+ |
  • | | | |
  • | v v |
  • | +-----------------------+ +-----------------------+ |
  • | | STANDARD SALES BPF | | ENTERPRISE SALES BPF | |
  • | | - Create: User Depth | | - Create: NONE | |
  • | | - Read: Org Depth | | - Read: NONE | |
  • | | - Write: User Depth | | - Write: NONE | |
  • | | - Delete: NONE | | - Delete: NONE | |
  • | +-----------------------+ +-----------------------+ |
  • | | | |
  • | v v |
  • | [ACCESS GRANTED] [ACCESS DENIED] |
  • | User sees BPF chevron on form BPF is completely hidden |
  • +-----------------------------------------------------------------------------+
  • Configuring BPF Security Privileges

In the Modern Process Designer, selecting Edit Security Roles opens the security configuration dialog. Security privileges for the custom BPF entity mirror standard Dataverse table privileges:

Create: Allows the user (or system automation running in user context) to instantiate a new instance of the BPF on a record.

Read: Allows the user to view the BPF chevron header on the model-driven form and inspect stages/steps.

Write: Allows the user to update data steps, advance stages, and modify the process instance record.

Delete: Allows the user to delete a BPF instance record from the database.

Important

No Read Privilege = Hidden Process: If a user's assigned security roles grant None for the Read privilege on a specific BPF table, the process is completely invisible to that user. The user will not see the BPF header, will not see the process in the Switch Process dialog, and cannot have that process automatically applied to records they create.

2. Order Process Flow & Process Precedence

When multiple Business Process Flows are enabled on the same table, Dataverse must determine which flow to apply automatically when a user creates a new record. This behavior is governed by the Order Process Flow configuration. +-----------------------------------------------------------------------------+

  • | ORDER PROCESS FLOW PRECEDENCE RESOLUTION |
  • | |
  • | [RECORD CREATED BY USER 'ALICE'] |
  • | | |
  • | v |
  • | +---------------------------------------------------------------------+ |
  • | | EVALUATE ORDER PROCESS FLOW | |
  • | | Rank 1: Government Sales Process ---> Does Alice have Read? [NO] | |
  • | | Rank 2: Enterprise Sales Process ---> Does Alice have Read? [YES]| |
  • | | Rank 3: Standard SMB Sales Process ---> (Skipped - Match Found) | |
  • | +---------------------------------------------------------------------+ |
  • | | |
  • | v |
  • | [INSTANTIATE RANK 2: 'Enterprise Sales Process'] |
  • +-----------------------------------------------------------------------------+
  • Evaluation Mechanics

In the Power Apps Maker Portal, navigate to the table's process list and select Order Process Flow .

Reorder the active BPFs vertically to establish priority (Rank 1 at the top, followed by Rank 2, 3, etc.).

Runtime Precedence Resolution: When a user creates a new row, Dataverse scans the ordered list from top to bottom. The first (highest-ranked) BPF for which the creating user possesses Read security privileges is automatically instantiated and displayed on the new record.

Switching Processes on Existing Records

If a record requires a different process later in its lifecycle (e.g., an SMB deal expands into an Enterprise deal), users with Read privileges on both processes can click Switch Process on the model-driven app command bar:

A dialog opens listing all active BPF definitions available to the user.

Selecting a new process applies that BPF to the record. The previous BPF instance remains preserved in the database in its current state.

3. The BPF Lifecycle & Status Reasons

Every instance of a Business Process Flow possesses a system-managed lifecycle status, stored in the statecode and statuscode columns of the BPF table: +-----------------------------------------------------------------------------+

  • | BPF LIFECYCLE STATE MACHINE |
  • | |
  • | [ INITIALIZE ] |
  • | | |
  • | v |
  • | +-----------------+ |
  • | +-------------------> | ACTIVE | <-------------------+ |
  • | | | (statecode = 0) | | |
  • | | +-----------------+ | |
  • | | | | |
  • | | +---------------+---------------+ | |
  • | | | | | |
  • | | v v | |
  • | [REACTIVATE] +-------------+ +---------------+ | |
  • | | | FINISHED | | ABANDONED | | |
  • | | | (state = 1, | | (state = 1, | ---+ |
  • | | | status = 2) | | status = 3) | |
  • | | +-------------+ +---------------+ |
  • | | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+

Active ( statecode = 0, statuscode = 1 ): The process is actively underway. Users can edit steps and navigate forward/backward.

Finished ( statecode = 1, statuscode = 2 ): The process reached the final stage and the user clicked Finish . The process bar is marked with a completion indicator and steps become read-only unless reactivated.

Abandoned ( statecode = 1, statuscode = 3 ): The process was terminated early without reaching full completion (e.g., an Opportunity was marked Lost or a project was cancelled). Abandoned processes can be reactivated at any time.

4. Programmatic Control via Client API ( formContext.data.process )

For advanced requirements where business rules or UI events must dynamically interact with the BPF, developers and functional consultants use the Client API via JavaScript web resources bound to model-driven form events.

  • The formContext.data.process Object Model // 1. Get the current active process and active stage
  • var activeProcess = formContext.data.process.getActiveProcess();
  • var processId = activeProcess.getId();
  • var processName = activeProcess.getName();
  • var activeStage = formContext.data.process.getActiveStage();
  • var stageId = activeStage.getId();
  • var stageName = activeStage.getName();
  • var stageCategory = activeStage.getCategory().getValue();
  • // 2. Programmatically Advance or Move Backwards
  • formContext.data.process.moveNext(function (result) {
  • if (result === "success") {
  • console.log("Successfully advanced to next stage.");
  • } else if (result === "invalid") {
  • console.log("Cannot advance: Required stage steps are missing.");
  • }
  • });
  • // 3. Switch Active Process Programmatically
  • var targetProcessId = "a1b2c3d4-0000-0000-0000-000000000000";
  • formContext.data.process.setActiveProcess(targetProcessId, function (result) {
  • if (result === "success") {
  • formContext.data.refresh();
  • }
  • });
  • // 4. Register Stage Change Event Handlers
  • formContext.data.process.addOnStageChange(function (executionContext) {
  • var currentStage = formContext.data.process.getActiveStage();
  • console.log("Stage changed to: " + currentStage.getName());
  • });
  • Essential Client API Methods Reference

Method Return Type Architectural Purpose

getActiveProcess() Process Object Retrieves the currently running BPF definition ( getId() , getName() , isRendered() ).

setActiveProcess(id, callback) void Programmatically switches the active BPF on the current record.

getActiveStage() Stage Object Retrieves the active stage object ( getId() , getName() , getStatus() , getSteps() ).

setActiveStage(id, callback) void Sets a previously traversed stage as the active stage.

moveNext(callback) void Advances the BPF to the next valid stage, evaluating stage gate rules.

movePrevious(callback) void Navigates the BPF back to the preceding stage.

getStatus() string Returns the process status ( "active" , "finished" , or "abandoned" ).

setStatus(status, callback) void Sets the process status ( "active" , "finished" , or "abandoned" ).

addOnStageChange(handler) void Attaches a listener that fires whenever the active stage changes.

addOnStageSelected(handler) void Attaches a listener that fires when a user clicks any stage chevron in the UI.