Context:
This document covers below point:
- Workflow In general
- What is egov workflow-V1.1
- What is the diff b/w egov workflow-V1 and workflow-V1.1
Versions:
V1 (Jan-2017 To Dec-2018)
- V1.1(Nov-2018 To Jan 2019)
- V1.2 (Apr-2019 To May-2019)
- V2 (Jun-2019 To Sept-2019)
Audience:
- Product Managers
- Developers
- Testers
- Co-creation partners
- Implementation Team
- Third Party(TP) integrators
What is Workflow?:
Workflows are a series of steps that moves a process from one state to another state by actions performed by different kind of Actors - Humans, Machines, Time based events etc. to achieve a goal like onboarding an employee, or approve an application or grant a resource etc.
Why do we need Workflow ?:
User View:
- Manage worklist for user.
- Make people accountable.
- Control action task based on roles.
Development View:
- No need for recompiling
- Rules kept as data
- Easier rule editing
Type of Workflow:
- Role based
- Department based
- Assignment Based
- Jurisdiction based
- Role + Jurisdiction based*
Objective V1.1:
- Role based workflow.
- Easy way of writing rule.
- File movement within workflow roles.
Key Features:
Below are the feature list.
- Always allow anyone with a role in the workflow state machine to view the workflow instances and comment on it
- On the creation of workflow it will appear in the inbox of all employees that have roles that can perform any state transitioning actions in this state.
- Once an instance is marked to an individual employee it will appear only in that employees inbox although point 1 will still hold true and all others participating in the workflow can still search it and act if they have necessary action available to them
- If the instance is marked to a person who cannot perform any state transitioning action, they can still comment/upload and mark to anyone else.
- Overall SLA
- State level SLA