Hi Russell,

Could you elaborate a bit on this one? I'm not sure I fully understand the ask. We recently released a default "Flexible" Workflow template that has as many loopbacks as possible built in already. I'm assuming you are referring to custom built workflows? Specifically I'm interested to understand what the challenge is with building a custom workflow once that has all the possible loopbacks vs. what you propose.

Thanks,
Luis

Hi Luis,

We'd ideally like to be able to just move the tasks to any workflow step at any time. For example, if something needs to go all the way back to translation, we'd prefer to just do one action to move the tasks instead of a reject loopback for each step backwards. If we need to build all possible loopbacks, that could create some overly complicated workflows depending on how many human steps there are with options to move backwards to any of the human steps. We'd also like this from an admin level and not necessarily the option for linguists to choose to move something backwards.

There've been some other TMS solutions I've worked with and I really liked how easily it was to move tasks back and forth if needed.

Best,

Russell

I agree with Russel, it would be usefull to provide the user with the ability to move the tasks back to any of the workflow steps, at any time. The Flexible workflow is not that "flexible" in the end.

Thank you, Carla and Russell for your feedback. 

I'm still not clear I fully understand the ask, see below what we have today. I can have multiple files in any stage of the WF and as PJM I can complete the task, or multiple tasks at once and send it where I need to. 

What else is missing or not possible as a use case?

Luis Lopes You shouldn't have to prebuild all possible loop backs to be able to move something back to previous step or even forward if necessary. An admin or someone with appropriate permissions should be able to select a task or tasks and move them where they need to go. The method that exists today relies on you fully building out all possibilities for all workflow steps. Building all these loopbacks makes the workflow visually busy in the workflow editor and isn't a great UX when trying to manage and update workflows.

The best way I have seen this managed in other TMS solutions is that you can select and move files/tasks whenever to wherever in the workflow. I am also not a fan of how you have to build a time bound hold for feedback step if you ever want to move something back into progress to make changes. With appropriate permissions you should be able to move between steps that exist in the linear workflow.

Luis Lopes You shouldn't have to prebuild all possible loop backs to be able to move something back to previous step or even forward if necessary. An admin or someone with appropriate permissions should be able to select a task or tasks and move them where they need to go. The method that exists today relies on you fully building out all possibilities for all workflow steps. Building all these loopbacks makes the workflow visually busy in the workflow editor and isn't a great UX when trying to manage and update workflows.

The best way I have seen this managed in other TMS solutions is that you can select and move files/tasks whenever to wherever in the workflow. I am also not a fan of how you have to build a time bound hold for feedback step if you ever want to move something back into progress to make changes. With appropriate permissions you should be able to move between steps that exist in the linear workflow.