# Workflows

Below is a sample workflow structure

Each workflow bind with one digital form, each form get multiple layout(Each layout with different field, which could support to control the field permission for different node)

Each digital form include a lot of different fields(data input textbox), which come with different data verification rules, personnel selection support get user’s information, department selection support get department information, swift number support generate unified running number for each different request

Per workflow include multiple nodes (Node mean different process steps or approvers), each node can connect with different layout of the digital form\[For example, the Department head may not see the running number, so we could hide it in dept. Head layout]

So for following user guide, a leave application request workflow will be designed and test

<figure><img src="/files/H5kKBNFqyJ6sdETS4EZP" alt=""><figcaption></figcaption></figure>


---

# 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://echelp.weaver.com.co/workflows.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.