Dan 5e54c90b47 "Reset" should not mean "re-start". Calling the reset_workflow script will now set the workflow to an "unstarted" state with no outstanding tasks, no json-state structure stored. The workflow is not yet running.
Also:
* Assured that arguments are consistent (we always seem to use workflow_spec_id, so I made sure we use that consistently.
* Don't require named parameters - so it's cool to call it like: reset_workflow('my_workflow_id')
* Task Actions (ie create, assign, etc...) are now an enumeration in the models, and not static variables on Workflow Service, so we can reference them consistently from anywhere.
* Removed some repetitive code
* Always try to validate as much as possible in the scripts to save folks time debugging.
*
2022-04-15 15:36:23 -04:00
..
2022-02-21 09:44:00 -05:00
2022-04-14 15:50:12 -04:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-03-01 16:17:34 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-03-11 18:02:37 -05:00
2022-03-11 18:02:37 -05:00
2022-03-28 11:59:53 -04:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-03-21 12:18:40 -04:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2020-06-18 12:01:02 -04:00
2022-02-21 09:44:00 -05:00
2022-02-21 10:17:18 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00
2022-02-21 09:44:00 -05:00