Making reusable tasks... reusable?

Hey there, maybe I'm missing this in the doc (and put in an "ideas" entry if we're still using that - http://ideas.inin.com/ideas/D3286) --- any way to reuse reusable tasks in different call flows? (Even if it's just a "copy to here" but it would be better if you could have the idea of a common piece of logic that can be used in multiple flows.

I am interested in this as well, any way?

Reusable task are only reusable within the current flow. A workaround is to could create another flow that does the common logic, then transfers back to the original flow. I'm attaching an example. In my normal flows MelissaTest1 & MelissaTest2, I use the set participant attribute before I transfer to CommonFlow so I know which flow to go back to. CommonFlow has a starting task instead of a starting menu. In CommonFlow after my common logic (the play audio action as a simple example), I use the get participant action to retrieve the name of the flow to return to. The switch transfers the caller back to the correct flow. Notice the transfer to ACD action as a safeguard in case the flow doesn't know which original flow to transfer back to; this could happen if you add a transfer to CommonFlow in a new Flow3 but don't remember to update CommonFlow to know about Flow3.

While the work around is appreciated and not a major stretch of the imagination, we're not wanting the workaround, but perhaps a new feature or ability of reusable tasks. You'd have to define the input and output but it would give you the ability to be a lot more flexible without working around anything. Does that make sense?

Yeah. That's something we'd like to do, but it's not on our current roadmap.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.