Datasources

Datasources are responsible for receiving incoming data and triggering workflow execution.

They act as the entry points into a project. When new data is received, the datasource forwards that event to the workflow engine, which then begins processing according to the defined workflow logic.

Without a datasource, a workflow has no external trigger.

---

Role in the System

In SolutionEngine, execution is event-driven. Workflows do not run continuously on their own. Instead, they are activated when a datasource detects new input.

A datasource typically:

• Listens for incoming data from an external system.
• Validates or structures the received payload.
• Triggers a linked workflow.
• Passes the data into the workflow as an execution event.

This model ensures that computation only occurs when relevant data is available.

---

Scope and Isolation

Datasources belong to a specific project. They are isolated within that project and cannot trigger workflows in other projects.

Each datasource can be associated with one or more workflows depending on the system design. All execution events generated by a datasource remain scoped to the project boundary.

---

Configuration Model

Different types of datasources exist, each designed for a specific integration pattern. Because external systems vary, configuration requirements also vary.

Depending on the datasource type, configuration may include:

• Network connection details
• Authentication credentials
• Input formatting rules
• Polling or subscription settings
• Reconnection behavior

While configuration differs by type, the operational model remains the same: receive input and trigger execution.

---

Runtime Behavior

Datasources are long-running components. Once activated, they continuously monitor their configured input source.

If a connection is interrupted or an input source becomes temporarily unavailable, the datasource handles reconnection based on its configuration.

When new data is detected, the datasource emits an execution event to the workflow engine. That event contains structured data that flows through the workflow’s nodes.

---

Design Considerations

When designing a system, consider:

• What external system produces the data?
• How frequently does data arrive?
• Is the input event-based or polled?
• What validation or filtering should occur before workflow execution?

Selecting the appropriate datasource type and configuration ensures stable and predictable workflow behavior.

---

Supported Datasource Types

While SolutionEngine can be extended with custom connectors, the following standard types cover most common operational patterns.

---

Datasources form the beginning of the execution lifecycle. The next step in the process is defining how that data is processed within a Workflow.