cancel
Showing results for 
Search instead for 
Did you mean: 

Flowchart design mode in Power Automate Desktop / PAD for more complex flows

When creating moderately complex flows in PAD (which is already doable) the overview gets muddy and that fast. Working with subflows helps but the current flow design view is a limiting factor.

 

I know this is early days for PAD and I am super enthusiastic to work with it, and see it grow, but for it to really be relevant in the long run it needs some way to help PAD Flow Developers to build more complex flows. imo.

 

I dare give UiPath as an example for an approach

Fjalar_0-1619695383813.png

 

Status: New
Comments
WorkingForFood
Advocate II

This would be great! I'm also coming to PAD from UiPath and would like to see this feature replicated by Microsoft.

Fjalar
Helper I

@WorkingForFood, I am sure Microsoft's PAD engineering team is aware of this feature and many others (in the other top 3-5 RPA products) but we should voice them here never the less, and that way if possible (and if the engineering team reads this), give good features a little weight and visibility.

 

Another thing I miss from UiPath is the log message activity and the message window for, variable outputs and errors. Using Display messsge action in developing and debugging is challenging at times...

 

WorkingForFood
Advocate II

Yes, the Write Line activity was very useful in UiPath and I haven't found a similar function in PAD. I'd also like to see some additional activities for DataTable variables, but that probably deserves its own post.

Fjalar
Helper I

Yes, we just need to add the features we miss from UiPath here and hope others agress with us 🙂 

 

I compiled this list in a reddit post few days ago. I will try to add these as Ideas:

 

  1. Log/output message window: for dev/debug and displaying error messages. Display messages is better than having nothing but not the best dev tool.

  2. Rename Actions and add descriptions/comments to them. The generic names of the Actions become more of a noise and less informative when a flow grows. Currently one has to read what the function of an action is specifically doing to see what it does. As a bonus feature, with the action renamed to something meaningful it could then be collapsed to only the title, minimizing the noise on the screen when.

  3. Custom Actions (Custom packages in UiPath), which I read here is a technical possibility already but probably not supported yet.

  4. And then Flowchart design view/mode similar to the one in UiPath. When the flows get complicated - and they can - you lose sight of where you are and spend more time scrolling up and down. You could use subroutines to simplify matters, and I am doing that, but the current design mode is linear and not all flows are linear, far from it.

  5. And in general a lot of capability that I miss, like string.format, that makes life so much easier when e.g. dealing with dynamic JSON request body construction. But I guess that kind of fancy stuff is anti-pattern when it comes to low/no-code functionality. Which means some smart Actions are then needed to help you build stuff like JSON request bodies 🙂

WorkingForFood
Advocate II

I'm a fan of all of these suggestions - will definitely keep an eye out for these Ideas.