From 08574cf6589ddb16825dfbf641cbc3af30d62518 Mon Sep 17 00:00:00 2001 From: Ayush Gupta Date: Fri, 13 Mar 2026 09:23:51 +0530 Subject: [PATCH 1/2] W-21541841 Updated Salesforce flow skill as Platform Event-Triggered Flows is not supported yet (#40) @W-21541841 Updated Salesforce flow skill as Platform Event-Triggered Flows is not supported yet --- skills/salesforce-flow/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/skills/salesforce-flow/SKILL.md b/skills/salesforce-flow/SKILL.md index e3a55d5..4513457 100644 --- a/skills/salesforce-flow/SKILL.md +++ b/skills/salesforce-flow/SKILL.md @@ -1,6 +1,6 @@ --- name: salesforce-flow -description: Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled, or Platform Event-Triggered Flows. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation. +description: Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation. --- ## Goal @@ -21,7 +21,7 @@ Use this skill when you need to: # Flow Metadata Specification ## Overview -Salesforce Flows are powerful automation tools that enable complex business process automation without code. Flows can collect and process data through interactive screens, execute logic and calculations, manipulate records, call external services, and trigger based on various events. Flow types include Screen Flows (user-guided), Autolaunched Flows (background processing), Record-Triggered Flows (database events), Scheduled Flows (time-based), and Platform Event-Triggered Flows (event-driven). +Salesforce Flows are powerful automation tools that enable complex business process automation without code. Flows can collect and process data through interactive screens, execute logic and calculations, manipulate records, call external services, and trigger based on various events. Flow types include Screen Flows (user-guided), Autolaunched Flows (background processing), Record-Triggered Flows (database events) and Scheduled Flows (time-based). ## Purpose - Automate complex business processes with declarative logic and branching From 39c8defd3e5becbe500845c28870aaeebfe68e36 Mon Sep 17 00:00:00 2001 From: h-kapoor-sfdc Date: Fri, 13 Mar 2026 14:46:03 +0530 Subject: [PATCH 2/2] W-21577425 Minor updates to the experts global rule file (#31) * Minor updates to the experts global rule * Minor update --- rules/a4v-expert-global-rule.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rules/a4v-expert-global-rule.md b/rules/a4v-expert-global-rule.md index b2d33b1..bef3cbf 100644 --- a/rules/a4v-expert-global-rule.md +++ b/rules/a4v-expert-global-rule.md @@ -8,7 +8,7 @@ Enforce: **skill load → API context → file generation** for all Salesforce m 1. **Never write** without both: metadata type skill loaded AND `get_metadata_api_context` called for that type 2. **One type at a time** - complete full cycle before next type 3. **One type per API call** - no batching -4. **No cross-type content** in files +4. **Child types need own context** - if adding any child metadata inside a parent metadata's file, load skill and call `get_metadata_api_context` for each child type (e.g. CustomField inside CustomObject) separately; don't rely on the parent's schema for creating child metadata 5. **Max one clarifying question** before starting ## Workflow @@ -51,9 +51,9 @@ Enforce: **skill load → API context → file generation** for all Salesforce m ### 3. Deploy Verification ```bash -sf project deploy start --dry-run -d "" --target-org --test-level NoTestRun --wait 10 --json +sf project deploy start --dry-run -d "force-app/main/default" --target-org --test-level NoTestRun --wait 10 --json ``` -On failure: attempt to fix the errors and re-run, retrying up to a maximum of 5 times until it succeeds. +On failure: attempt to fix the errors and re-run, retrying up to a maximum of 3 times until it succeeds. ## Anti-Patterns