The workshop tutorial path
Three pages, in order. They all use the same prepared project, so what you build on the first page is what you change on the second and put through CI on the third.
The page titles say “Day 1” and “Day 2” because that is how the material is split, not how the calendar is. The Workshop page has the actual schedule.
- Day 1: Vacation approval — build an approval that waits for a person, run it, test it, look at what it recorded, hand it to a stand-in, and restart the process to prove it survives.
- Day 2: Multi-role approval — read a workflow with several approvals in a fixed order, then change one of them.
- CI and deployment — run the same project in a CI-style job and start it a second time from a different directory.
The Workshop page is for whoever is running the room: timing, breaks, what to do when a block overruns. It isn’t a fourth exercise.
Everything in these three pages runs against prepared test identities. It is deterministic: the same input gives the same result on every machine, so a difference is a real difference and not a flaky provider.
There is one optional exercise that talks to a live identity provider. It has its own preflight and its own page, the live Role Engine adapter. If that preflight fails, nothing in the three pages above is affected — carry on with the prepared data and note the live part as not attempted.