DEV Community

Cover image for Let's Talk About The New Power Automate UI
david wyatt
david wyatt

Posted on

Let's Talk About The New Power Automate UI

If anyone follows me on LinkedIn (and if you don't you should 😉) they will know I have been vocal about the new Power Automate UI, and I've seen by the comments others are too

So I thought I would take a deep dive into my thoughts, with 'The Hits', 'The Misses' and the 'If Onlys'

The Hits

The Look
new ui
We can all agree the Classic UI looks dated, its still has a Windows XP vibe, and the New UI looks clean and modern.

And call out to the new Do Until, I love it, it looks like it would in code and so can easily be identified 😎 It's my new favourite action (before you say anything we all know we have one 😂).

do until

Pan and Zoom
One of the hardest things in the Classic UI was to get a full view of your flow. I often had to zoom out on the browser, which was not user-friendly or pretty. Additionally in dealing with horizontal branching/containers is just painful using scroll bars. The New UI smashes it.

pan zoom
Guessing even Microsoft's top web developers have trouble with CSS, the zoom buttons are always half hidden

The ability to zoom in, out, pan around, fit to screen and search for actions from list is great and a big improvement on the Classic UI.

Filter Actions
filter

Filters are simply better then seperate tabs, this is so much easier to use then the Classic UI.

Static Result (Mock Outputs)
Not many talk about this but I think its cool, the ability to stop an action running outside of the flow, but allowing the flow to continue. A good example is a Email trigger flow that after completing deletes the original email. If you rerun the flow it always fails because it can't delete the email again, but with this you can get it to skip deleting but act like it did.

test condition

The other big use is exception handling, as you can get an action to fail and then see how the exception is caught, no more imaginative ways to force an action to fail needed.

Shortcut Keys (Kind of)
I love shortcut keys, and the New UI allows you to use / to add in variables/expressions.

shortcut key

It's far to basic for the moment but its a welcome step in right direction, excited to see more shortcut keys.

Side Panel
Now this is an interesting one as it depends. From a negative side the action inputs are now not in the action, so you have to move your cursor further. It's marginal, but for pro developers everything adds up and can impact your productivity. Add in memory muscle changes and it can be more than you realise.

New UI mouse path
new ui mouse move

Classic UI mouse path
classic ui mouse move

So why's it a hit, well you just need to zoom out. If you try and use the Classic UI to action an edit, it all falls apart when you zoom out, as the action is too small. And you may argue is the trade off worth it, and I say yes. Microsoft are 100% right, we should be developing from a big picture view, it's simply more productive and efficient that way (other RPA tools do, look at Blue Prism and UI Path). So for me this UI change will improve the way we work in the long run, I just wish it would default to be a little more zoomed out.

The Misses

Copy and Paste
How the New UI went into general release without copy and paste is madness (that's a move from the Apple playbook not the Microsoft I know). They have added it since but it's a shadow of the classic.

It can't copy containers:
new copy actions

It only remembers the last action copied compared to a clipboard list in Classic.

classic copy actions

HTML
So if you want HTML in your emails you need an additional Compose action, what! Nearly every Send Email action I have in a flow usee HTML, it's a fundamental requirement, how this was missed is another crazy move.

New UI No HTML button (</>)
html new ui

Classic UI with HTML button
html classic ui

Trigger Default
We have been brought up with default trigger to split and for good reason. In all my years of development I have never had a use case that doesn't require it. So why does the New UI default to not split, crazy.

split on

Undo/Redo
On the list of the very very basic features you would expect from any software, an undo button must be one of the first. Yet this is missing from the new UI ðŸĪĶ‍♂ïļ

undo button missing in new

Open Multiple Actions
When code reviewing or debugging its definitely a lot harder in the New UI as you can only see one action at a time. This is another of the Zoom out trade offs, but it is a definite negative as there are now no benefits for the code review process.

new ui all actions
New UI above, Classic UI below
classic ui all actions

The If Onlys

For me there was lots of opportunities to make the developer experience better and/or to make the transition easier.

Panel and Action
For me this is obvious, why not have the best of both worlds, when zoomed in show the inputs within the action (Classic UI Style) and when zoomed out the side panel (New UI style). With zoom Microsoft didn't need to make the actions smaller.

My Design for Zoomed in Actions in the New UI
zoomed in new UI

Improved Filters
As I said the filter is definitely better then the Classic UI tabs, but they missed an opportunity to add functionality. I would love a filter that only shows available to me (so hides DLP blocked actions and if I don't have premium hides premium actions).

Secondly I would love a favourites filter, so I could star actions I use a lot and and then filter to just them.

Improved Copy and Paste
Imagine instead of removing Copy and Paste functionality they added to it, in the Office suite there are different types of copy (formula,theme,value), so I would love a copy inputs. How would that work, well lets say you have SharePoint Get Items, you copy inputs, then when you add a new SharePoint action any matching inputs would be auto populated (like site or list).

Improved Debugging
The 'Static Result' is a great start, but I would love to see more developer tools like what Chrome Dev tools have.

  • Start from action, (I have memory of this in preview but cant find it in Planned Features) this would allow you to test a flow with a previous failed run and continue from the failed point.
  • Break Point, instead of adding a terminate to stop during development you could add stop on an action. You can then click continue or end.
  • Conditional Break point, so if a condition is met it will stop
  • Trace variables, showing how variables change during the run, it would also show inputs/outputs (why can't I see the inputs of the condition in the run logs!!!!)

Find and Replace
The action search is a start, but I want to be able to search for values within actions not just action names. On top of that I want to be able to replace. If you think about it this is basic functionality found in nearly all programs.

In Conclusion

My starting place was very much that I didn't like the New UI (borderline hate it), but after completing this blog I realised that I like what Microsoft is trying to do, they made the right design choices, but messed up the rollout. The New UI is simply not ready for General release (barely preview), I suspect it was rushed out because they wanted to release Copilot.

Pro developers have a tight efficient work stream and muscle memory to the existing UI. If they are going to invest in changing there are 2 key requirements for a product refresh to work:

  • Feature Parity
  • Killer New Feature

All the Misses are missing features from the Classic UI, and with things like 'Static Result' there are potential for a Killer New Feature. So Microsoft could easily make the New UI work, they just need to:

Get proper feature Parity, that's not half fixes like 'Copy and Paste' it needs to be at least as good as Classic.

Add features for Pro Developers, Copilot is not useful for us and is definitely not a reason to change.


Microsoft really messed up the launch of the New UI, and a lot of developers like me only see the negatives and miss the positives. Let's hope they get their focus right, get feature parity and think of Pro Developers not just the Copilot generation.

Top comments (8)

Collapse
 
porpoisepower profile image
JB • Edited

Re: email composition,
I think it might default to HTML... if you check the code, it appears to be encoded in HTML even without enabling it... Which is fine sending plain text or rtf in 2024 is as the kids say... cringe. So just being HTML by default is fine. Note:I haven't tested this fully yet, but it should be okay in theory.

But the issue that really bugs me is that there is a size limit, that is way too small for any robust flow... The limit might increase at some point but as of the end of 2023 I can't use the new editor on some of my flows unless I split up some functionality into sub flows, which isn't always ideal.

Collapse
 
wyattdave profile image
david wyatt

For me it's the old homage "if it's not broken don't fix it", and the old html way worked great. I read they are planning on adding it later, but worst case that's because they gave into pressure from Devs, best case they planned it all along but released it when it wasn't ready

Collapse
 
balagmadhu profile image
Bala Madhusoodhanan

Spot on mate... The old UI design had a user empathy that made me feel good. The new UI design does not have the debugging toolkit and some important actions like copy, reset, and redo that I use a lot

Collapse
 
bobby_hill profile image
Robert Hill

The UI being different isnt my biggest issue. My biggest gripe is that the logic is different in the new version!

In my original flows I have several comparisons using "value is not null". The new UI doesn't allow this, and won't save. Who knows what other logic is different, leading to issues with that damn copilot.

Personally, I would've been happy with the old UI, but turned horizontal. This would provid the ability to open multiple actions, but without pushing the entire flow down and several could easily be viewed on screen together. Simply expand the opening action to zoom to 100%. This crazy change, missing several key features wasn't needed.

The push for copilot was such a bad move. The one time I used it, to replace every instance of email address A with email address B, it took 10 minutes to delete half my flow and called it good. Email B didn't even get put in anywhere.

Collapse
 
wyattdave profile image
david wyatt

Wow didn't know that, makes me glad I stayed with Classic UI. Horizontal idea sounds a good idea (it's how Dell Boomi is).
Copilot is a waste of time, it's LowCode NoCode so you don't need it, plus like you said it haa no idea, few times I tried it made the most inefficient mess I had every seen

Collapse
 
toptastic profile image
Chris Topham

Maybe it's a sign of me getting older, but I'm not convinced about this change. The overall aesthetic feels too cluttered. This could be due to Copilot automatically appearing on the right of the screen and the crosshatch background. I know that the days of having the option to switch will be numbered, but I'm still going to make the most out of having the older skin on this.

Collapse
 
wyattdave profile image
david wyatt

I agree, it feels like the design decisions are all about getting Copilot Infront of everyone. I'm like you and still use Classic UI and will be until they get the basics right

Collapse
 
helsey33 profile image
Himanshu Ranjan

What is used to build the node based UI