feat: add building-flow-approval-process skill - #286
Open
svaroteauxSFDC wants to merge 1 commit into
Open
Conversation
|
Thanks for the contribution! It looks like @svaroteauxSFDC is an internal user so signing the CLA is not required. However, we need to confirm this. |
Adds a new skill for Salesforce Flow Approval Processes (processType: ApprovalWorkflow), a distinct flow type not covered by the existing generating-flow skill. Key contributions: - Full architecture guide: orchestration, Background Steps, Approval Steps, Screen Flows, WebLink trigger, Lightning page components - Explicit delegation rule: AutoLaunched and Screen Flows are generated via the generating-flow MCP pipeline; only the ApprovalWorkflow orchestration XML is written manually - Hard-stop constraints mapped to known deployment/runtime errors - XML reference patterns in references/xml-patterns.md - Common errors quick reference table with root causes and fixes - Required deployment order to avoid dependency failures
svaroteauxSFDC
force-pushed
the
feat/building-flow-approval-process
branch
from
June 12, 2026 09:40
540723d to
dcc73db
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new skill for Salesforce Flow Approval Processes (
processType: ApprovalWorkflow) — a distinct flow type not covered by the existinggenerating-flowskill, with its own architecture, constraints, and XML patterns.Changes
skills/building-flow-approval-process/SKILL.md— core skill (~170 lines): goal, activation criteria, Classic vs Flow Approval Process distinction, delegation rules, step types, output reference syntax, hard-stop constraints, deployment order, common errors tableskills/building-flow-approval-process/references/xml-patterns.md— complete XML reference: orchestration variables, WebLink, Background Step, Approval Step, Decision routing, Screen Flow variables, full stage exampleMotivation
Flow Approval Processes (
ApprovalWorkflow) are frequently misimplemented because they look like regular flows but follow completely different rules:<subflows>elements — only Background StepsOutputs.prefix (StepName.Outputs.var)These constraints are not documented in
generating-flowand cause hard-to-debug deployment and runtime errors.Design decisions
references/xml-patterns.mdgenerating-flowMCP pipeline; only the ApprovalWorkflow orchestration (unsupported by the pipeline) uses manual XMLmetadata.version: "1.0",## Goalfirst section, imperative style)Notes
Tested against real Salesforce production deployments. All constraints and error fixes are verified against observed deployment and runtime behavior.