> 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/process-test-and-debug-guideline.md).

# Process Test & Debug Guideline

Once a process is completed, user will need to test it before migrating it to other environments. For this ONEWEB provides the Simulator utility.

**How to use Simulator?**\
Once the process is validated successfully, click on the Simulation Test tab. Here user can provide the input for testing in JSON format. User can test the process until completion by clicking on the Complete button by changing the inputs accordingly. For more details check [Simulate your process](/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/start-with-business-process-in-oneweb/simulate-your-process.md) section

![](https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FpbOZb1iY0XcBErTDpJIY%2Fimage.png?alt=media\&token=724d3e1e-9695-412d-aa9f-2f842632c06d)

Once a process is deployed, user can test that process by using any REST client like the **Postman.**

![](https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FhcKUh46UTvwjSoRKit0B%2Fimage.png?alt=media\&token=30ee9888-ff49-4043-a688-fe51f6f2dde5)

**How to test using Postman?**

When you open **Postman Application**, you must configure the value for testing.

1. Set request method type as **POST**. 
2. Set URL: http\://**{IP}:{Port}**/BPMREST/service/runtime/process/**{Process name}**/start for starting flow.
3. Click setting **Body**. 
4. Choose data as **raw**.
5. Choose data type as **JSON (application/json)**.
6. Enter JSON data for input parameter of the process.

Now click Send button and view response text in response panel of the **Postman**.

![](https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FDEXRY7ngeCCVqLXdnmeC%2Fimage.png?alt=media\&token=fe5a68c3-7a86-421f-8e0b-65f5bf035902)

On response panel, user will receive Instance ID **on** data property of JSON text. When instance id is sent, it means the flow has started.

User can use **Instance ID** to get task id by calling the task service. Set request method type is **GET**, set **BODY** is empty and use url as follow. \
http\://**{IP}:{Port}**/BPMREST/service/runtime/instance/**{Instance ID}**/tasks 

When user want to claim task or complete task, user can bring **Task ID** and user name for working to set in url as follows. \
http\://**{IP}:{Port}**/BPMREST/service/runtime/tasks/**{Task ID}**/claim?user=**{Username}** \
http\://**{IP}:{Port}**/BPMREST/service/runtime/tasks/**{Task ID}**/complete?user=**{Username}**


---

# 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/process-test-and-debug-guideline.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.