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. Review collected by and hosted on G2.com.
The learning curve, honestly. Two years in (I'm a technical implementation team of one) and there are still things that I'm learning about that I simply didn't know to look for. Functionality we brute forced that had a automatic counterpart we simply didn't know was there (and didn't know to ask about).
The documentation leaves a lot to be desired as well. Well, not the documentation itself, it's great - once you can find what you're looking for. The search engine in the documentation isn't the best and again, unless you know specifically what you're looking for, you're going to be hard pressed to find help outside of their support system. Probably 75% of my support requests (access to which is free with purchase) are simply answered with a link to the documentation (which is what I want).
I've mentioned the terminology thing several times now, so I'll give an example. You want a certain process to fire every Friday. Say it's a reminder that people need to fill out timesheets (VERY simple example). You search the documentation for 'reminder', 'automatically start a process', and 'schedule a task' among other things before finally asking for help. The reply is simply "that's called a 'goal'" with a link to the appropriate documentation.
Another; you want people to be able to submit a variable list of names and addresses (think vendor options for a large PO) with requirements on the number based on other criteria (is it already a contracted vendor, is there only one vendor that provides this product). As far as the main tools are concerned, most things are an html-based form. But to have a variable number of entries is called an 'array'. Makes sense in retrospect but I was being told 'no code' so I wasn't thinking in programmatic terms. Once I knew that, I could read all about it and take a stab at implementing it.
I guess to sum up, the greatest asset - there's a literal sea of content and functionality to build whatever you want - is also it's hardest feature to get through. It's hard to document how to play in a sandbox. Review collected by and hosted on G2.com.
Scott, this is some really great feedback. Will take this back to the team!
