Documentation

Workflows

A Workflow defines how data is processed inside a project.

It describes the sequence of operations that should occur when an event happens. Workflows are created using a visual editor where nodes are connected to represent processing steps.

A workflow does not run continuously on its own. It runs when it is triggered by an event. That event can come from a datasource or from other supported system triggers.


Structure of a Workflow

A workflow consists of nodes connected in a defined order.

Each node performs a specific task. Tasks may include:

  • Receiving input data
  • Transforming or restructuring data
  • Applying logical conditions
  • Executing a model
  • Sending results to storage or external systems

The connections between nodes determine how data moves through the workflow.


Triggering a Workflow

A workflow begins execution when it receives a trigger.

Triggers can originate from:

  • Datasources
  • Manual Triggers
  • Time based triggers

When a trigger occurs, the workflow receives structured input data and begins processing from its starting node.


Execution Behavior

Each time a workflow is triggered, it runs as a separate execution instance.

During execution:

  • Data flows from one node to the next.
  • Each node processes the input it receives.
  • The output of one node becomes the input for the next connected node.

If the workflow contains branching logic, only the connected paths that meet defined conditions are executed.

Execution continues until there are no remaining nodes to process.


Workflow Configuration

Workflows are stored within a project.

Each workflow can be:

  • Saved in a draft state
  • Deployed to one or more environments
  • Updated and redeployed when changes are made

Workflow definitions include:

  • Node configuration
  • Connection structure
  • Model references (if used)
  • Parameter settings

When deployed, the workflow definition is sent to the selected environment for execution.


Using Workflows Effectively

When designing a workflow, consider:

  • What event should start the execution
  • How data should be structured at each step
  • Where branching logic is required
  • What outputs should be produced

Workflows are the core mechanism for defining system behavior in SolutionEngine. All data processing, decision-making, and model execution occurs within a workflow.