Workflow Automator logic pathways

This is the first time this has been suggested.  The workflow automator has been available for how long now and we still don’t have the most basic ability to “redirect” a workflow to another part of the workflow.  Instead, you have to make a copy of every node, rename each node (if you don’t like “copy of”) and then hope you never have to update the workflow because update to a node will have to be replicated in each branch.

My most recent workflow automation, I have 4 branches to handle the manager approval step:

1. Requested for/by a VIP
2. Submitted for a user by their manager
3. Manager not found
4. Manager found

After the manager approval step, each branch has the identical 10 nodes (40 total), meaning I have 30 extra nodes to test and maintain.  Why can’t we get a simple “go here” action?  Or a “Go” step and a “target” step.  Put some sort of limit on the number of times the target can be passed through to avoid endless loops…

 

Hello, There are coming new options like loop and calling other WFA(workflow automator).
I have done a approval flow with one level/line. I trigger it it both on SR create and Approval status change to Approved. So the same WFA runs several times. The trick is to not have any actions after the approval node. I use complex expressions to who is going to approve and in what step. 

I’m using 2 custom objects to control the WFA who is going to approve. 

I haven’t read anything about a Go to function. 

Meant to say “NOT the first time this has been suggested”

haha, it’s a pain that we can’t edit our own posts afterwards :/ 

Almost wonder if we can submit ideas about the ideas portal 😂

But in respect to this post...I know a large amount of the community members have gone to great lengths to push the freshservice product team to expand and improve the workflow automator functionality. As @afautley so eloquently put it “Release the chains” so that we can open up the platform and let the businesses drive its use. My hope is this post gets a large number of votes because I would pick this over “Dark Mode” any day of the week!

Yes - absolutely @zachary.king - I crab at them all the time about the way that the portal will torpedo posts without warning and they never get moderated back to life. lol  This portal is a 3rd party product for FW and so the Vendor has a vested interest in hearing feedback about making it better.

After all, none of us “community experts” are being paid to share our expertise and our ideas - we do it bc we want to use the platform to the best of its ability.

Totally agree on the need of having multiple paths in the workflow automator.

Even add a second event that starts within the middle of the workflow.

@Daniel Söderlund 

You mentioned some news about loops in freshservice? I’d love to have this feature for a lot of usecases. Do you have any link or announcement for this feature?

It’s info we have gotten from our CSM when we have asked for a road map. So nothing official yet. 

PARTY TIME!!!!

We Desperately need this please should be a number one target

I’m soo glad and loving the enthusiasm here!! We hope we made your Friday better @afautley !! 😎

Let’s keep pushing 👊🏼

Come on Team Freshservice! we NEED this implemented, it’s essential!

Last roadmap session it was >1+ year away 

Support!!!

This is a really important feature we have so many needlessly complex workflows because we can’t just loop back in to the relevant part of the flow.

Putting my voice behind this too, especially around onboarding where things may or may not be needed.

Any updates on this? This feature always seems to be coming next year!

It’s crazy that this is not a default feature of Workflow Automator at the start. Not having this feature causes unnecessary complexity that could be avoided if this feature existed! “GO TO” should have the ability to point a workflow step to another workflow, or to another part of the same workflow. If we could use “GO TO” on another workflow we could build modules that do a specific task, somewhat like is done in programming. Make “GO TO” a feature today, not next year or next month!

Hello Folks!

Flagged this to our product team for a status check. Hoping to have more updates soon!!!

New customer here. checking in…. for the same problem

Unfortunately, loops and subflows don’t solve this, any updates?