# Integrate with Other Systems from/to Process Flow

**Process Designer** is a core tool in ONEWEB used to design, execute, and manage **business processes** within an application.\
In addition to workflow modeling, Process Designer also supports **integration with other systems** through dedicated node tasks.

Process‑based integration is typically used when integration:

* Is part of a **business workflow**
* Is **long‑running or stateful**
* Requires orchestration across multiple steps or systems
* Involves human or system interaction over time

Many integration node tasks in Process Designer are functionally similar to those in Microflow Designer, but they are executed **within the context of a process flow**.

***

### Database Node

Process Designer provides a **Database Node** to interact with databases as part of a business process.

This node is commonly used to:

* Retrieve data required during a process
* Persist process‑related data
* Synchronize information with external or legacy databases

#### Supported Connection Types

* **JNDI** – recommended for managed, server‑side environments
* **JDBC** – suitable for custom or external database connections

#### Supported Database Commands

The Database Node supports the following SQL operations:

* **SELECT**\
  Retrieve required values from the database using an SQL query.
* **INSERT**\
  Insert new records into the database.
* **UPDATE**\
  Update existing records using an SQL command.
* **DELETE**\
  Remove records from the database.

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FcLft9IIS63kqr0APSEEt%2F0?alt=media" alt=""><figcaption></figcaption></figure>

***

### Sub Process Node

In complex applications, a single process may become large or contain repeated logic.\
The **Sub Process Node** allows a process to invoke another process as a **subroutine**.

Using a Sub Process Node, developers can:

* Break large processes into smaller, reusable flows
* Improve readability and maintainability
* Treat a group of steps as a single logical activity

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FANcsFNAPcuTC67msEs9O%2F1?alt=media" alt=""><figcaption></figcaption></figure>

***

### Web Service Node (SOAP & REST)

Process Designer provides a **Web Service Node** that allows a process to integrate with **external web services**.

This node supports both:

* **SOAP web services**
* **REST APIs**

Developers configure service details visually, and ONEWEB automatically:

* Generates service invocation logic
* Creates request and response data structures

#### SOAP Integration

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2Fx5jlkys0roVSFD3UVxMl%2F2?alt=media" alt=""><figcaption></figcaption></figure>

#### REST Integration

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2F5JBwAYd45529dOsMGh0Y%2F3?alt=media" alt=""><figcaption></figcaption></figure>

From a configuration perspective, SOAP and REST integrations follow the same design pattern within Process Designer.

***

### File Read Node & File‑Triggered Processes

Process Designer supports integration with **structured files**, including:

* Microsoft Excel files
* Delimited (CSV) files
* XML files
* Fixed‑width files

The **File Read Node** can be used to:

* Read file contents
* Create data models from files
* Populate process data for further processing

Files can be read from:

* Local file systems
* FTP
* SFTP
* FTPS

In addition to reading files, Process Designer also provides a **File Input Node**, which allows a process to **start automatically when a file becomes available** in a monitored location.

This is commonly used for:

* Batch processing
* File‑driven workflows
* Legacy system integration

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2Fsoh2lK3YXxd8wg45sTzG%2F4?alt=media" alt=""><figcaption></figcaption></figure>

***

### When to Use Process Designer for Integration

Process‑based integration is best suited for scenarios that are:

* Long‑running or multi‑step
* Workflow‑oriented
* Dependent on business rules and states
* Involving coordination across systems or users

For **short‑lived, stateless, or service‑style integration**, **Microflow** is usually a better fit.

***

### Summary

**Process Flow integration** in ONEWEB enables applications to integrate external systems as part of business workflows.

Using Process Designer, applications can:

* Interact with databases during process execution
* Call SOAP and REST web services
* Read and react to files from multiple sources
* Orchestrate complex, long‑running integrations
* Reuse processes through subprocess nodes

Process Designer plays a critical role in ONEWEB’s integration architecture when integration logic is tightly coupled with **business workflows and lifecycle management**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.onewebstack.com/oneweb-platform-th/building-apps/integrations/what-is-oneweb-integration/integrate-with-other-systems-from-to-process-flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.