hi I'm Jason Lefever I'm a product manager with the platform workflow automation team and today we're talking about process automation designer also known as pad a commonly encountered question is why should I use PAD as we answered in the previous video process automation designer is the no code builder for sequencing automations and building Enterprise processes what we have here is an example process in p so we have both a combom board style view that allows me to seamlessly sequence process stages and steps also known as activities this is a drag and drop type of experience so that I can quickly see all of the steps that should be involved in every stage of my process we also have a diagramming view so if I have a complicated process with multiple stages or activities running in parallel diverging and converging paths I can easily see those nuances in the diagrammatic view so anytime that I need to take a sequence of steps that are used to achieve a business outcome essentially a process I can automate that process on the now platform using process automation designer some common use cases case management incident response procurement Services onboarding suppliers onboarding employees anytime that you have a series of steps that need to be completed in order to achieve an outcome you can build a process inad one of the things that we'd like everyone to know is that process automation designer uses the power a flow designer so even though pad is a no code Builder under the hood we use the subflows and actions that are available in flow designer so as a developer type of persona build builds actions builds subflows these things we can consider as our building blocks they can be reused in any process context now process automation designer takes those building blocks and turns them into a building a process so reusable pieces of automation can be sequenced to achieve an endtoend business outcome we hope you found this helpful good luck building your processes using process automation designer