This is a compendium of all my undo/redo related bug reports:
Is the staff not going to take care of these issues? To add more, undoing simply not works many times. Mos of times, if you modify the value of an activity parameter inside its text box, there’s no way of undoing it. Sometimes when you click ouside and you press ctrl+z, it will, but other, it won’t. Inside the text box, it will, I would say never, work. Don’t you think this is serious enough?
Undo/Redo appear to be context sensitive. For example, if you click an activity inside a Sequence and delete the activity, you have to have the Sequence selected for the Undo to work.
OMG… Seriously, @postwick ?
By the way, I just tryied like that in the activity I was messing with and I couldn’t go back no matter where I placed the cursor and clicked on. And who knows the side effects, if it has undone other things that I can’t see, while pressing CTRL+Z a million times to try to get it working.
Yes exactly, I have this same concern whenever I do it. I agree they need to make it more predictable and consistent.
I know it doesn’t help. But to add to the bonfire.
I recently used Studio Web to develop a quick and dirty thing to manually trigger a process which would normally be triggered by an Integration, for testing.
I went to go change the process name in a start job activity and it wiped out the data I was passing to the job, which I couldnt recall.
Whats worse is not only did Undo not do anything / be enabled, but I tried to leave the page without saving but nope. Autosave!!!
You have no version history from what I can see of your project either so one wrong click and oops, you lost everything, cannot undo, cannot avoid saving and cannot recover from a backup…
Ouch.
I feel your pain, man. The same has happened to me several times. The data/parameters inside an activity are gone and sometimes that’s a lot of information and you don’t keep it copy&pasted somewhere expecting that such a thing could happen. In my case, I don’t have autosave that I’m aware of, and I’ve resorted to exiting and reopening the project again, but anyway, sometimes you mess up with other things and then a while later (seconds?) you realize that something was lost in your activity but you’ve done something new you don’t want to lose, so you end up typing it again, and the like.
No local history either, as you pointed out. Although comparing changes with this workflow system is already so tricky that I don’t know if it would be really useful, as when I try to diff with the repository…
yeah, it happens alot with the ‘new’ style activities.
Like for example you want to add a queue item, but when you change the folder it wipes the queue name meaning you need to select it again, which is sooooo annoying.
These new ‘dynamic’ activities can be cool, but them nuking your info is nasty and in Studio Web its the toughests cause you cannot undo and you can’t not save.
At least Version Control can save my ass in Studio desktop.
The unreliability is showing up also when copying & pasting (duplicating) variables and undoing/redoing. I copied&pasted the “any” variable; then I undid it, then wanted to redo - It didn’t redo anything, but yet the exclamation symbol of “the variable is already declared in this scope” keeps apearing. This is only one of the weird behaviours I found out while messing with this copy&pasting variables redo/undo actions I could document.
Just for “fun”, here it goes a video I made showing that undo/redo don’t work properly.
And, as a bonus, you can see on it that Studio allows to “disable” or comment out an activity that’s already disabled. Yeah, I know it doesn’t make sense for me, as a user, to disable it if I know it’s already disabled, but… why is it offering the option, if it’s already disabled? If you want to nest commented blocks, that’s ok, I can’t think of an scenario for that, but it’s ok - but just don’t call it enable/disable activity, plainly call it “comment” or whatever. Poor UI design.
When is this gonna be addressed?
The scope of the undo/redo “functions” is not clear, plus it plainly DOESN’T WORK.
Here’s an example of an infinite redo.
I merely placed a “Try…Catch” scope by choosing the wrong right-menu option.
Immediately I pushed the “Undo” button. It did nothing. I don’t know if it had any other secondary effects.
That’s not fair.
Is there any temptative date for this to get fixed?
I try to manually remove the Try…Catch.
I want to cut&paste its contents, as you know it’s unreliable.
I don’t want to try to drag it outside because you know it’s unreliable.
I don’t want to individually do it activity after activity because you know it’s a hassle.
But there’s no “Remove Try…Catch” block available no matter where I place the cursor:
Anil_G
ashokkarale
sonaliaggarwal47
Yoichi
AJ_Ask
sharazkm32
Naveen_Kumar6
seki_i
manasrlenka25
Lahiru.Fernando