Map trigger, inputs, rules, and outputs
Want more background?
The idea in everyday life
Translate informal work into explicit states, decisions, data fields, and exceptions before configuring software.
A workflow is a sequence of steps. Define its trigger (what starts it), inputs (the data it needs), actions, and expected result.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Draw manual CSV batch → Approved filter → field validation → existing-ID lookup → destination write; add human-review and unavailable-destination branches.
- 2
Read the eight-column dictionary in README and all six test-cases.csv rows. event_id is the stable booking key; case_id identifies the test attempt.
- 3
Map event_id to booking_id, room to room, owner to coordinator. Dates are copied as supplied ISO date strings; minutes must be an integer from 15 through 120.
- 4
Predict each case using expected-results.md: success, lower boundary, duplicate, missing room, draft and simulated destination outage.
See how it works.
T01 creates B101 with 60 minutes, Room A and Lee; T03 repeats B101 and must not create it again. T04 has no room, so a human must correct its source. T06 fails before writing when destination_available is no. The date-format check does not promise calendar conflict detection.
Did you cover these?
- Your work includes a trigger-to-output workflow map with field dictionary, rules, exceptions, and defined scope for the first working version.
- Check this common mistake: Building directly in an automation tool while the process still depends on unstated assumptions in one person’s head.
- Another person can predict the workflow’s action for a valid record, duplicate, missing field, and exception.
What to finish
A trigger-to-output workflow map with field dictionary, rules, exceptions, and defined scope for the first working version.
Watch for this
Building directly in an automation tool while the process still depends on unstated assumptions in one person’s head.
How can I tell I understand it?
Another person can predict the workflow’s action for a valid record, duplicate, missing field, and exception.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkOptional course overview video · same video as Lesson 1
Power Automate Tutorials
From Microsoft Power Automate. Watch here or open it on YouTube .
Watch for an idea you can use in the practice below. You can pause or skip this optional overview.Tools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.