Depends on how you define “complex”, and also depends on if you integrate the Queues.
A typical “complex” automated process would perform over 3 various tasks per process item. And, if any one of the tasks enters a retry attempt due to an exception, then ideally you would want the process to continue where it left off when it enters the Process state again.
If you don’t integrate the Queues, then you would also need to store each item index so it can skip to that item when it enters the Process state again after a retry attempt. If you do use the Queues (which I’m still learning), then in theory it should be able to process the items without that extra logic, however, I am still unsure how well the Queues actually work considering how much a process needs to update files (you can’t update files in use) — it’s still something I want to play around with and learn more about, but to be honest, there’s little difference in each process using all robots vs each process using the Queues and waiting for availability of robots.
Now, I did briefly look over the Enhanced a while back and set it aside because of how complicated the structure and naming were; it was hard to understand right away even though I understand how State Machines work. I showed it to my colleague who doesn’t know programming that well, then I showed her a variation of a Framework I had created and been working with, and she said she’ll use mine cause it was more visually pleasing with a simpler folder structure; she could basically place in each workflow module that completes each task of an item, and it is ready to go right away.
I actually do like many ideas that were put in Enhanced, but I think a version that’s easier on the eyes, simple to implement a project into, and versatile toward various ways to design your project should be more desired. For example, simply placing a Process.xaml workflow into the Process state will not work, because of the complexity of performing many tasks per item, and if you don’t use the Queues, then you get an even bigger mess if no logic is in place to skip already processed items.
So sorry for the lengthy reply.
I’m definitely going to revisit the Reframework though and see what I can do about some of the ideas I’ve had, cause it seems to be the standard among consultants. Also, “Attended” processes should be considered. All in all, you shouldn’t need a training session to understand the Reframework structure; the structure should speak for itself in my opinion.