Introduction
A Workflow levels are defined for a service with rightsRights/Role to perform a set of Workflow Actions . There would one or more than one levels involved in a workflow process. This page helps to understand and then defined the define all the levels with its job description and fill in a standard template.
Data Table
Sr. No. | Module | Service | Workflow Level | Role Name | Job Description |
1 | Water charges | New Application | Level 1 | Citizen, CEMP | |
2 | Water charges | New Application | Level 2 | Document Verifier | |
3 | Water charges | New Application | Level 3 | Field Inspector | |
4 | Water charges | New Application | Level 4 | Approver | |
5 | Water charges | New Application | Level 5 | Citizen, CEMP | |
6 | Water charges | New Application | Level 6 | CEMP |
Note: Data given in above table is sample data.
Procedure
Data Definition
Sr. No. | Column Name | Data Type | Data Size | Is Mandatory? | Definition/ Description |
|---|---|---|---|---|---|
1 | Module | Text | 64 | Yes | The module indicates for which the user would be mapped for a specific module to perform the action. |
2 | Service | Text | 64 | Yes | The service indicates the type of process which the user perform in a particular module |
3 | Workflow Level | Integer | 2 | Yes | The workflow level indicates when a process is executed the level at which the flow of process is progress. |
4 | Role Name | Text | 64 | Yes | The role is the one who approves or reject the action during the workflow. |
5 | Job Description | Text | 256 | Yes | A short description provided for the role (Example: Designation of the Role) |
Step to fill data
Download the data template attached to this page.
Have it open and go through all the headers and understand the meaning of them by referring 'Data Definition' section.
Make sure all the headers, its data type, field size and its definition/ description is understood properly. In case of any doubt, please reach out to the person who has shared this document with you to discuss the same and clear out the doubts.
Identify all different types of grievances on the basis of ULB’s functions.
Start filling the data starting from serial no. and complete a record at once. repeat this exercise till the entire data is filled into a template.
Verify the data once again by going through the checklist and taking care of each and every point mentioned in the checklist.
Checklist
The checklist is a set of activities to be performed once the data is filled into a template to ensure data type, size, and format of data is as per the expectation. These activities have been divided into 2 groups as given below.
Common Checklist
This checklist covers all the activities which are common across the entities.
To see common checklist refer to the page Checklist consisting of all the activities which are to be followed to ensure completeness and quality of data.
Entity Specific Checklist
Please discuss with a relevant department head before finalizing the workflow.