cancel
Showing results for 
Search instead for 
Did you mean: 

Modify the Workflow Designer to move steps and stages

Author Name: Maxime Nobert-Bourbeau

It is not currently possible to move a stage or a step in the workflow designer.

It would be useful to be able to move a stage or a step in your Workflow. For example, your business logic has changed or you might just want to update the order of the execution steps/stages.

I would like to click on a step, drag it and drop it elsewhere in my Workflow and click save instead of recreating that step and deleting the older one.

I guess one of the workaround (never tried it before) would be to manually change the XML of that Worfklow, but it would then require a "skilled" developer. This is not necessary something that your customer can easily do.

Status: Planned

 

Thank you for the feedback!  This is a great suggestion, and we will definitely consider this in the roadmap. 

Regards,

 

Brandon

PM, Microsoft

Comments
Level: Powered On
Status changed to: Planned

 

Thank you for the feedback!  This is a great suggestion, and we will definitely consider this in the roadmap. 

Regards,

 

Brandon

PM, Microsoft

Level: Powered On
This would make editing advanced workflows a lot easier. This should really get a good upvote to improve productivity when creating workflows.
Level: Power Up
It is horror and money wasting to change a workflow. So this would be veryvery very great to have
Level: Powered On
Further, it would be nice to be able to disable/comment out steps/stages of workflows and to have some kind of "variable/state" tracking utility for testing and validation of workflows.
Level: Powered On
Include the ability to select one or more existing statements and "wrap" them in a condition, or to create a condition and move other steps "inside" it. Too many times I have found the business change the logic of a process and say "we only want to do this bit if foo and bar now, not baz". While in some cases it is appropriate to use a logically opposite condition to cause a stop, other times this is not suitable when only some of the existing steps are to be made conditional, and later ones should continue. Very often I now wrap whole chunks of workflow in conditions which effectively do a 1=1 always true (such as Entity:EntityID contains data). This means later on I can change this to a 'real' condition if I need to without lots of rewriting.
Level: Power Up
@Adam yes yes yes. but why there is no response from ms on this post. i would need this now, not in years.
Level: Powered On
So important!
Level: Power Up

There is a new designer which could now be easily adopted for workflow designing.
+1

Level: Powered On

Really hope they develop this.  Very painful when you need to move a step.

Level: Powered On

Please, please. This would save admin's a lot of time. Time is money!!