> For the complete documentation index, see [llms.txt](https://eohelp.weaver.com.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eohelp.weaver.com.co/design-a-new-workflow.md).

# Design a new workflow

## 1 High level understand about workflow

<figure><img src="https://lh5.googleusercontent.com/vD_przCvlopx-P0B43RlqDBRF_BA3xkuhAWBPxdCocVJzkxY4iniPdFmie4hCVim4X8A0sFhtnKIeJukRjqTBL-OmfJPtmXils_f_hplrM8MvboHPdZNnHvPvoOgTwtZupZwvTEx5sQaJNYR4w62oOU" alt=""><figcaption><p>High leve understanding</p></figcaption></figure>

<figure><img src="https://lh4.googleusercontent.com/RlG7mm35vdNQACRMkLURqfYf9p3iHN7HbKag76oIVzYDFxMLYEHGVfpQ5SWK7jvzr_Tf4luNf7J1vOVtEt5r1LHzzcPO7mzvOkbb9TrRUL2bofbB_cM6legso_V79YkqSiZNomU-xruI1oZ-kNjFW_k" alt=""><figcaption><p>Simple leave application form and approval</p></figcaption></figure>

A workflow is a business process/approval flow which include a data form and a approval flow

**Form** is used to collect essential data from user, but some basic information could get from system directly

**Workflow** is help to flow the form to each approver, reviewer, manager to check, verify and confirm. There are 2 different workflow, fixed and free flow

* Fixed - follow company policy, only all the relevant approver approved, then workflow will end and archived
* Free - for some requests, there is no clear company policy, so requester could fill in all relevant approver, if some approver need other’s input, they could forward the workflow to others as well

## 2 To design new workflow, you need login to e-office 11.0, and find the workflow from the menu

<figure><img src="https://lh4.googleusercontent.com/nsk19nJf12WfrCJVXZI5A0YkNQWg84unRPi7RCbyIxdnoeObbRxLe3shHxdYA-GCa-EpuEMGIfzWdyxJuR-NMEwUp8hmaR6UuPTlslVXC32NCUdAoranz9K1vM4mYyw6fxEksVE67GeoS4gsywo3EcQ" alt=""><figcaption></figcaption></figure>

## 3 Below screen will display, workflow menu

<figure><img src="https://lh6.googleusercontent.com/QmgSoxvmtn4KfKWmro4VwTiuDtMchL_ZmFFLd0J-30EG_jfWHqPGkq7vkyW2qhFpvnK2Osp8_cBRPcqWZK3JixLi9YT1fgayB4dZzJsxYdquLYAZy4fzlTBntfn-Zo5LbI1yMYY9J77fkAYQ5zFDcGs" alt=""><figcaption></figcaption></figure>

* New request - initial new approval flow
* Pending - check all workflow require user’s review/approval/verification
* Processed - all workflow approved/reject by user
* My request - check all workflow initialled by user
* Delegation - Delegate your approval/review permission to others in a period
* Monitor - Monitor workflow status, process and terminate the workflow
* Form design - design new data collect form
* Workflow design - design approval flow for different use scenarios
* Category - define workflow category by department/use scenarios


---

# 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://eohelp.weaver.com.co/design-a-new-workflow.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.