6 Commits

Author	SHA1	Message	Date
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
mike cullerton	265381f48c	Delete TODO comment. Done	2022-02-07 16:44:59 -05:00
mike cullerton	2a6e8315a1	*** WIP *** ... Committing to deal w/ the migration	2022-02-07 11:22:45 -05:00
mike cullerton	572ca1db6b	Fixes for backend code after removing name column from workflow_spec and workflow_spec_category tables	2021-10-05 14:17:41 -04:00
mike cullerton	02949dc6e2	WorkflowProcessor handles this error	2021-06-15 11:12:50 -04:00
mike cullerton	c8f8888c17	Script to reset workflow. Requires workflow spec name.	2021-06-14 14:51:16 -04:00