> For the complete documentation index, see [llms.txt](https://docs.oneweb.tech/oneweb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/best-practice-for-process-design.md).

# Best practice for Process Design

The design of your business process has significant impact on its usability and performance. To optimize the process structure, we recommend the following best practices:

**Create small processes** and divide them into separate blocks. We do not recommend placing more than 10 - 15 elements on a single diagram. If a process is complex, some element groups in a process can be implemented by using sub processes, and then connecting those sub processes into your main Business process. 

**The Main flow in the process should be in the same line** and alternate paths should be lined in branches. For example: In an approval process (Fig: Approval Process) below, elements that lead to successful process execution are lined on a single level and additional conditional approval paths are depicted in the branches.

![Fig: Approval Process](https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2F2b5ma2V8v6FuZRqi3vIF%2Fimage.png?alt=media\&token=6a86ecca-b6c3-4be1-b7b5-bc984d987b52)

**Build a process so that the maximum number of flows is lined in one direction.** There are two ways to achieve it: building a process downwards or from left to right. Minimize the number of intersecting flows for the process to look clearer. 

**Name processes & nodes by their purpose.** Always name all elements, flows and connections on the process diagram and avoid identical and similar names. Node tasks and Events names should include an action, that is to be executed by an element or an object, and the object to which said action is applied, for example: “Place order’, “Send message”, “Register issue”. 

**Delete obsolete process parameters.** 

**When using the \[Read data] task** like Database Node/ File Read Node etc, **configure reading of only the required columns**, if there is no need to read them all. Reading all columns might lead to slow business process execution performance. 

**When branching the process flow, set one of the flows to “default”**. This will prevent the business process from “freezing” if there are no eligible branches. 

**Avoid overlapping of elements** and connections and make sure names are clearly visible. 

**When setting up a new process**, make sure the diagram does not contain any unnecessary elements.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/best-practice-for-process-design.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.