Once you get your head round the terminology (which is probably different than whatever you call it) and know where to find what you're looking for, going from design of a process to implementation and end user consumption is really a fairly straightforward and simple-ish thing. It is definitely low code (you need to understand conditional logic but you're never actually writing script unless you need to do something the tools aren't designed for, and this is an additional module you have to pay for if you're a cloud customer), but you need a programmatic mindset to get the most out of it.

The ability to design and build forms and also the ability view results quickly and easily. I quite often use the reference guide when I am trying to come up with a method to accomplish a task and often find my answers without reaching out for assistance. Utilizing timelines to control the flow of a form and the processes that follow and being able to audit that timeline if items are missing or troubleshooting an issue. Another thing I like about the form designer is the ability to view the source code of the form to make any adjustments.

I like the graphical interface, especially for workflows. I like to see the flow laid out. It's like Visio in that way. There are so many features, I haven't even tried them all! I They consistently update the product and offer new features. Machine Learning is one of the newer ones that I still need to wrap my brain around. Process Director is mostly a no-code solution. However, if you do want to code, you can dig into web services and even create ascx forms - which you can manipulate till your coder's heart is content.