22.10 Studio Layout and Design

Feedback Studio
,
1

Is there option to use back the prior studio layout and design under version 22.10?

I find the new layout and design style very “disturbing”, every activity became “thicker” and taking up more spaces.

Furthermore some of the activities no longer works the same as per prior version.
Eg. Text input activity now must be within attach window or etc scope activity.
If activity also looks different and there is another “Else If” activity.

The overall experience with 22.10 is horrible for me, especially on UI.

3 Likes
4

Thanks for sharing your experience. Stay tuned for 22.10.4 update as we will be pushing a shrunk designer with thinner activities.

1 Like
5

True! :no_mouth: :no_mouth: :no_mouth:

6

Hey,

Any plans on more UX customizability? The colors surrounding scope activities are very nice addition but I wish we could customize it, also managing the lines on flowcharts is a huge pain, in terms of flowchart design BluePrism does it much better.

7

Rarely do I get emotional about the software I use.

I always try to provide constructive criticism.

I must admit, however, the new look raised my blood pressure quite a bit (and did so in record time, might I add), so please forgive my straightforwardness:

It is absolutely terrible. It’s clunky, chunky, the studio itself seems slower than before.

Not only does the change not address the biggest problem with uipath’s design - very poor readibility, especially in big projects - it exacerbates the problem even more.

I cannot comprehend how these changes got approved, developed, tested (?) and deployed without anyone at UiPath pointing out how horrible these feel.

What was the reasoning behind these changes?

What’s downright atrocious, however, is the asinine design of the “IF” activity I noticed just 5 minutes ago.

Who in their right mind thought it is a good idea to have the “then” and “else” parts not side by side? And who thought having the “else” option first is good? What programming language follows such convoluted logic? :see_no_evil: Aaaargh!

In times where people have access to widescreen 30+ inch monitors your design team somehow decided to make uipath even more vertical (instead of using that potential horizontal space), because apparently it’s such a joy having to scroll down or up by an entire screen’s worth every time I want to do absolutely anything.

For the love of all that’s good and pure in this world, please oh pretty please, give us the ability to revert … this.

7 Likes
8

Agreeing wholeheartly, I think tho it should be an option to have vertical or horizontal IFs, I have some legacy spaghetti cases where I wish it could go vertical :smiley:

9

I am gonna stick to v22.4.7 until they revert the design and etc…

If they continue with the horrible updates on design and activities like IF and etc, better to change and recommend other RPA software in the market

10

Personally, for me I want them to have the ugly colours be something we can remove. If some users want them then ok, listen to the crowd. But research shows visual noise like that does not help.

Regarding the If, I cannot feel as strongly. But think some toggle options would be great. I used to be able to ignore the else, hide it entirely. Now I cannot.
Perhaps we can have two toggles, one to hide the else and another toggle the layout from vertical and horizontal.

Oh and please please please in the new activity card stuff, restore the properties pane. I really like the enhancements to the activity cards so we can make them in libraries, but why are you removing the properties pane and denying us access to some properties and making things harder?

11

I guess they think the new layout works better when presenting to a potential client? This is the only way I can think someone used to justify this atrocious change. Sometimes, the UiPath team seems like they don’t care at all about how their software works for those who use it daily. We can see some poor decision-making in many areas, such as Studio Design, the existence of Studio X, Integration Service only working for attended automation, and Orchestrator tags that have no use besides cluttering the UI. The list goes on…

And im not even starting to tell you about the Legacy to Windows migration tool.

12

Whilst some design choices can be appropriately questioned these are both just false statements.
The Integration service works for both attended and unattended bots and the tags do have uses. The reserved tags are actually used already in Build Pipeline stuff, you just likely haven’t seen it yet.

13

Integration Service does not work in unnatended bots it does? Are you certain? I tried to use it, but since the integration service connection are linked to a Orchestrator user, and this user cant be a robot user, the connection does not work when you play the process on an unnatended session.
I even got a ticket from support double checking that for me. But please, If you was able to somehow make it work cna you share with me how that was done?

About the tags, you are right :slight_smile:

14

Thats the part where you are probably going wrong. An Orchestrator User can run unattended robots.
If you want to do this try setting up your account so it can run unattended robots the create a unattended job against your account. It will run it fine as it does attended or in Studio.

Purely robot accounts cannot yet, so I will concede that. But it is possible to use the integration service with unattended bots.

The purpose of the integration service initially seemed to be to connect specific users and help make authentication easier and not for using in robot accounts, but its nice to hear its being expanded to also include those.

Edit:
Oh and here it is also explained by UiPath
See the intent is the connection isn’t intended to be shared across users.

15

The find the new design fairly distracting to use, I too put my vote in going back to the old version. It looks much better and you more easily can tell what your looking at.