Hey, there! Ceci here.
Growing up there were two main route options to get to our family cabin: I-94 or the backroads along Highway 10.
Same destination, different routes, different traffic patterns, different ETAs โ and totally different vibes.
The interstate was faster (as long as you avoided rush hour), while the backroads were dotted with stop signs, traffic lights, and small-town slowdowns along the way.
Funny enough, business processes in Workday work a lot like that ๐
Just like multiple routes can get you to the same place, you can have multiple business process (BP) definitions โ each with different steps, participants, and levels of complexity.
In this newsletter, we cover how, when, and if to use multiple BP definitions.
Buckle up! Weโre going for a ride ๐

Whatโs a business process definition?
First, letโs fuel up with a quick recap: whatโs a BP definition?
(๐ Pssstโฆ if youโre a BP veteran, feel free to skip ahead.)
In Workday, a BP definition outlines the full workflow behind a task โ including the steps involved, whoโs responsible for each one, and any custom touches like notifications or help text to guide the process.
This is where the good stuff lives.
Free builds awareness. Premium fills all the gaps ๐ฆ
Below: how to set up multiple BP definitions, when to use object based vs. rule based, the gotchas that trip people up, and how Workday picks which definition to fire.
Plus everything else in Premium:
โญ๏ธ Release Ratings & Reviews
๐ Full archive access
๐ณ๏ธ A say in what gets built


