cr-connect-workflow/package-lock.json

{
  "name": "cr-connect-workflow",
  "lockfileVersion": 2,
  "requires": true,
  "packages": {}
}
Missed committing a pile of changes last night. 2020-06-02 07:08:29 -04:00			`{`
"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			`"name": "cr-connect-workflow",`
			`"lockfileVersion": 2,`
			`"requires": true,`
			`"packages": {}`
Missed committing a pile of changes last night. 2020-06-02 07:08:29 -04:00			`}`