מתי להשתמש
"Salesforce", "SF Flow", "Flow Builder", "Process Builder migration", "Apex vs Flow".
הוראות עבודה
1. Why Flow over Process Builder
Salesforce deprecated Process Builder ו-Workflow Rules. Flow הוא המקום היחיד לאוטומציה ב-2026.
2. Flow Types
א. Screen Flow
- UI שמשתמשים אינטראקטיביים איתו.
- Wizard-style.
- Used in Lightning pages, Communities.
ב. Record-Triggered Flow
- Trigger on insert/update/delete.
- Replaces Process Builder + Workflow Rules.
ג. Scheduled Flow
- Run at specified time.
- Replaces Scheduled Apex (for simpler tasks).
ד. Platform Event-Triggered
- Pub/sub events.
- Async automation.
ה. Auto-launched Flow
- Called by Apex / API.
3. Flow Building Blocks
- Element = step (Get/Update/Create/Delete records).
- Resource = variable / formula / collection.
- Decision = branching (if/then).
- Loop = iterate over collection.
- Subflow = call another flow.
4. Common Patterns
A. Lead Conversion Automation
Trigger: Lead changes status to 'Qualified'
→ Get Account by Domain (lookup)
→ Decision: Account exists?
├── Yes: Convert Lead, Link to existing Account
└── No: Create Account, Convert Lead
→ Send Slack notification
B. Opportunity Stage Automation
Trigger: Opportunity stage = 'Closed Won'
→ Update Account: Customer Status = Active
→ Create Tasks for CSM
→ Send Email to Customer
→ Trigger Webhook to billing system
5. Governor Limits
Important
- 100 SOQL queries per transaction.
- 50K records returned per query.
- Bulk processing recommended.
Best Practice
- Avoid SOQL in loops.
- Bulkify all operations.
6. Flow vs Apex
| Need | Use |
|---|---|
| Simple CRUD | Flow |
| Complex business logic | Apex |
| External callouts | Apex (or Flow + Action) |
| Scheduled simple tasks | Flow |
| High-volume processing | Apex (better governor handling) |
| Trigger conditions | Flow first, fallback Apex |
7. External Integrations
- Outbound Messages (legacy).
- HTTP Callouts (Apex).
- Platform Events.
- MuleSoft / Workato / Zapier for non-developer integrations.
8. Common Pitfalls
❌ Recursive flows — A triggers B triggers A. ❌ No bulkification — fails on bulk imports. ❌ No error handling — silent failures. ❌ Hardcoded IDs — break in sandbox/prod.
9. Best Practices
- Naming: "[Object][Trigger][Action]".
- Description filled.
- Version control before changes.
- Test in Sandbox first.
- Bulk-test with 200+ records.
10. Pricing
- Flow built-in to all Salesforce editions.
- Some advanced features (Data Cloud Flow) extra.
11. Israel Specifics
- Hebrew RTL: works in screen flows with effort.
- Israeli Salesforce partners: Touchpoint, Geneo, Salesforce IL.
- Israeli VAT (17%): Flow can calculate.
12. אסיים בהמלצה.
קלט נדרש
| פריט | תיאור |
|---|---|
| Salesforce edition | Pro / Enterprise / Unlimited |
| Use case | Lead / Opp / Service |
| Volume | records/day |
| Tech capability | Admin / Developer |
פלט צפוי
| רכיב | תיאור |
|---|---|
| Flow type | מומלץ |
| Flow design | high-level |
| Bulk consideration | אם volume |
| Apex integration | אם נדרש |
| המלצה | פעולה אחת |
דגלים אדומים
- 🚨 Process Builder — migrate ASAP.
- 🚨 No bulkification — fails on imports.
- 🚨 Recursive flows — infinite loops.
הערות חשובות
- Salesforce moves fast — features change yearly.
- Trailhead = best free training resource.
- Admin certification = essential for serious work.
פרומפט לדוגמה
Lead → Contact → Account flow. Build ב-Flow Builder.
Opportunity Closed Won → Notify CSM + Create handoff. Flow.
Process Builder migration ל-Flow. תכנון.
© 2026 Automation Expert Pro | גרסה 1.0.0