Class: RailsWorkflow::Context

Every operation and process has context. Context is a set of variables (by default it is a hash). If you navigate to process you can see context data in right column:

Navigate to operation and you will be able to see context in the bottom of the page:

When you create new process, you passing process template and initial context (hash) for that process:

RailsWorkflow::ProcessManager.start_process(
  process_template_id , { resource: resource }
)

Process manager takes process template and using it to build new process. It passing given context to template and by default using it as is. You can change that behaviour using custom ProcessTemplate class.

Operations context is build by operation template. By default operation template using process context (if operation has no dependencies and is building before process start) or previous operations context.

Let's say we have process template with 3 operaiton templates: A, B, C. Operation template C depends on
both operations A and B with DONE status. We have process build on that template with A and
B operations. A is just get completed (changed it's status to DONE). But since operation B is IN_PROGRESS
process not building operation C. Operaiton B is completed. Both A and B having DONE status so process starting
to build operation C. By default it using last completed operation context. In our case it is B operation context
but we have both operations A and B contexts passed to build_context method of OperationTemplate so you can easy
change that behaviour and merge A and B contexts.

Please note: in given example operation C depends on both A and B with DONE status. Default operation template
dependency resolver will build operation C if any of that operations will have DONE status. So in given example
I assumed that operation C template has custom resolve_dependencies method which only return true if both operations
exists in DONE status.