Course 2.9 · Curriculum 2026.1
Flow patterns, and the point where Apex is the right answer
Pick the automation that fits: screen, record-triggered, scheduled, autolaunched or Apex. Then learn the four tells that a flow has grown into something that should have been code, from an org running roughly 191 active flows beside 32 triggers.
- Estimated effort
- 5 hr
- Lessons
- 39
- Modules
- 7
- Material
- 5 hr
Estimated effort is the sum of the lesson and lab times in this version of the course. It is not video runtime, which is lower.
Canadian dollars. One learner, lifetime access to this course version. Tax extra.
1 lesson free to preview
This course does not issue a certificate on its own. It counts toward the paths listed below, and those do.
01What you will learn
7 capabilities, stated as things you can do
Each one is what you should be able to do at the end, not what the course covers. If an outcome is not testable, it is not an outcome.
- Choose a flow type from the trigger, the audience and the volume, in that order.
- Build a before-save flow for a field update, and state the performance argument in numbers.
- Schedule a flow over a filtered set without scanning the whole object every night.
- Call a subflow and an Apex action, and pass a collection across the boundary safely.
- Order automation across triggers, flows and validation rules, and predict the save order.
- Name the four tells that a flow should have been Apex, and act before year three.
- Convert a flow to Apex without changing behaviour, proved by a before-and-after run.
02Curriculum
7 modules, 39 lessons
Every lesson shows its length and its type. A SCORM lesson looks like any other lesson, which is the point of ingesting packages rather than linking out to them.
7 modules · 39 lessons · 5 hr of material
The trigger, the audience and the volume decide the type, in that order. Getting the order backwards is how a screen flow ends up running nightly on 50,000 records.
- VideoChoosing a flow type from the trigger, the audience and the volumePreview8 min
- VideoScreen flow versus record-triggered versus autolaunched, on one page7 min
- VideoScheduled and platform-triggered flows: the two people forget6 min
- ReadingReading: a flow-type decision tree5 min
- LabLab: pick a flow type for three real automations12 min
A before-save field update is free. An after-save update is a second DML statement on every record. The numbers make the choice for you.
- VideoBefore-save versus after-save, and the performance argument in numbers8 min
- VideoField updates: before-save is free, after-save costs a second DML7 min
- VideoWhen a rollup or a cross-object write forces after-save6 min
- ReadingReading: the record-triggered flow entry condition, tightened7 min
- ReadingReading: before-save flow limits and what still applies5 min
- LabLab: convert a field-update flow from after-save to before-save12 min
Scanning the whole object every night does not scale, and an empty result that looks like success is worse than a slow one.
- VideoScheduling a flow over a filtered set, not the whole object8 min
- VideoBatch size, entry conditions, and why "every record, nightly" does not scale7 min
- VideoThe screen flow that reported success while logging nothingIt listed an order’s work orders. 42 active orders had zero. An empty collection loops zero times, straight into a success screen.7 min
- ReadingReading: designing a flow so an empty result is visible5 min
- LabLab: build a scheduled flow that skips what does not need it12 min
Two ways to hand work to something else, and the collection boundary that has to survive 200 records, not one.
- VideoCalling a subflow, and when it earns its own maintenance cost8 min
- VideoInvocable Apex actions, and the method signature a flow can call7 min
- VideoPassing a collection across the boundary safely7 min
- VideoBulkifying an invocable method so a flow calling it 200 times survives6 min
- ReadingReading: input and output variables, and the types that trip people up5 min
- LabLab: build an invocable Apex action that accepts a collection12 min
Triggers, flows and validation rules interleave in a fixed order. Predicting it before you build beats discovering it from a ticket.
- VideoOrdering automation across triggers, flows and validation rules8 min
- VideoPredicting the save order before you build, not after a ticket7 min
- VideoWhere a validation rule blocks a flow update mid-save6 min
- ReadingReading: the order of execution, and where flow sits in it5 min
- LabLab: predict then verify a save order involving two flows12 min
An org running roughly 191 active flows beside 32 triggers has already answered this question many times. This module states the answer as a rule.
- VideoThe four tells that a flow should have been Apex8 min
- VideoTell one: arithmetic spread across more branches than a person can hold6 min
- VideoTell two: the same subflow called from a dozen places6 min
- VideoTells three and four: nested loops, and logic no reviewer can follow6 min
- VideoThe 5,460-line flow XML file, read as the case that outgrew Flow Builder7 min
- LabLab: score a real flow against the four tells12 min
Behaviour must not change. The proof is a before-and-after run, not a confident read of the old flow.
- VideoConverting a flow to Apex without changing behaviour8 min
- VideoA before-and-after run that proves nothing moved7 min
- VideoDeprecating the flow without breaking what still calls it6 min
- ReadingReading: a migration checklist for retiring a flow5 min
- LabLab: convert a scored flow to Apex and prove equivalence12 min
- QuizCheck: flow patterns and when Apex wins12 min
03Before you start
What you need first
Assumed knowledge and setup
- Course 1.4. This course assumes you have shipped a flow already.
- Course 2.1 for the final two modules. The Apex is read first, then written.
- A Developer Edition org with the Salesforce CLI installed.
Courses that come first
- 1.4 · Flow: the automation you will actually build8 hr · Intermediate
Part of these paths
- Salesforce DeveloperShareCo Certified Developer
- The Full StackShareCo Certified Platform Engineer
04Who teaches it
Ege Taskent
Salesforce Developer, Certified Platform Administrator
The credential, and the rollout. The half of an implementation where people actually start using the thing.
Salesforce Certified Platform Administrator
05Reviews
No learner reviews yet
This course has not been taken by enough people to publish an honest rating, and we will not print invented quotes on a page that sells verification discipline. Here is what we can evidence instead.
- Assessment
- Lesson checks onlyThis course carries lesson checks. The certificate is issued by the path assessment, not by this course.
- Curriculum version
- 2026.1You enrol into a version. Content changes do not move you mid-course, and your required-lesson count is snapshotted at enrollment.
- Refunds
- 14 daysFull refund within 14 days if you have completed under a quarter of the required lessons. Stated here rather than in a footer.
Start 2.9
Enrol as an individual, or buy seats and assign this course to your team. Progress is reported per lesson, per module and per path.
- 5 hr estimated effort, labs included
- Lifetime access to the version you enrol in
- A ShareCo certificate is not a Salesforce certification