You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
is it possible to use the conductor for managing task's workflow with multiple transitions between tasks and task states?
I'd like to build a system similar to service desk system with a series of tasks that can be executed and it should be possible to restart execution, return tasks to previous state and so on.
Its very similar to how the Jira handles task lifecycle.
I know that the conductor manages workflow as DAG, so the flow direction mostly moves forward.
Also I know that the conductor provides switch and do-while tasks, but I'm not sure that it would cover all the possible cases. It would be great to have very flexible transition between task state by updating task state or definition and return execution to some previous point.
Another option the conductor provides are events, but I think that in this case it would require writing some additional logic to manage transitions. It would be better to use out-of-the-box possibilities as much as possible, and
writing control code as less as possible..
Does anyone know any idea or approach how to do that better?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi folks!
is it possible to use the conductor for managing task's workflow with multiple transitions between tasks and task states?
I'd like to build a system similar to service desk system with a series of tasks that can be executed and it should be possible to restart execution, return tasks to previous state and so on.
Its very similar to how the Jira handles task lifecycle.
I know that the conductor manages workflow as DAG, so the flow direction mostly moves forward.
Also I know that the conductor provides switch and do-while tasks, but I'm not sure that it would cover all the possible cases. It would be great to have very flexible transition between task state by updating task state or definition and return execution to some previous point.
Another option the conductor provides are events, but I think that in this case it would require writing some additional logic to manage transitions. It would be better to use out-of-the-box possibilities as much as possible, and
writing control code as less as possible..
Does anyone know any idea or approach how to do that better?
Beta Was this translation helpful? Give feedback.
All reactions