# Workflow Data Templates

A **workflow process** is a series of sequential tasks that are carried out based on user-**defined** rules or conditions, to execute a business **process**. It is a collection of data, rules, and tasks that need to be completed to achieve a certain business outcome.

In DIGIT, workflow for a business process is divided into three units out of which two are completely configurable while the remaining is fixed and lays the foundation of the other two.

### [Workflow Actions](#workflow-actions) <a href="#workflow-actions" id="workflow-actions"></a>

This is the first unit which defines the actions and their nature which are basically executed during the workflow process by the workflow actors. It plays the foundation and is configurable in nature as per the ground needs.

### [Workflow Levels](#workflow-levels) <a href="#workflow-levels" id="workflow-levels"></a>

This is the second unit which defines the number of steps a workflow process may have and then trigger the creation role for each and every step with appropriate rights to perform a set of actions at each step. It is completely configurable.

### [Workflow Process](#workflow-process) <a href="#workflow-process" id="workflow-process"></a>

This is the third unit which defines the workflow process including the steps, roles with actions and the present, next and previous state of a step/level of the workflow process. It is completely configurable.


---

# 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.digit.org/local-governance/v2.8/platform/configure-digit/configuring-master-data-templates/module-setup/workflow-data.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.
