Implement Segmented Workflows
authorSawyer Bergeron <sawyerbergeron@gmail.com>
Fri, 14 Dec 2018 21:05:47 +0000 (16:05 -0500)
committerSawyer Bergeron <sawyerbergeron@gmail.com>
Thu, 3 Jan 2019 15:34:13 +0000 (10:34 -0500)
commitf27e25c199c3c5c9433463732b776ae9b4357cf8
treed684ed4b89355db5050021b4aaaf505d4de70bc8
parente26a8259dbe879d722d5e619f9d6efe0b113d1cd
Implement Segmented Workflows

A major source of bugs has been how we've approached inlining
workflows. We no longer inline them as of this commit, and instead
use a stack structure. This commits the result of workflows to the
database before other workflows try to read them, so we don't have
to maintain a code path for when something is or isn't committed
to db.

This patchset allows for workflows to pass limited information
to preset selections

Change-Id: I3d040c7f3024c7420017ae4ec66a23219303dcb6
Signed-off-by: Sawyer Bergeron <sawyerbergeron@gmail.com>
13 files changed:
src/templates/booking/steps/booking_meta.html
src/templates/dashboard/searchable_select_multiple.html
src/templates/workflow/confirm.html
src/templates/workflow/exit_redirect.html [new file with mode: 0644]
src/templates/workflow/no_workflow.html
src/templates/workflow/viewport-base.html
src/workflow/booking_workflow.py
src/workflow/forms.py
src/workflow/models.py
src/workflow/sw_bundle_workflow.py
src/workflow/views.py
src/workflow/workflow_factory.py
src/workflow/workflow_manager.py