435889ee79
- Migrate from custom HTTP server to VitePress framework - Rename project to Tokenized License Approval System (TLAS) - Add comprehensive documentation for all stakeholders: - Business: Executive summary, value proposition, governance - Operations: Infrastructure, installation, monitoring, backup - Departments: User guide, workflows, verification, issuance - Developers: API reference, authentication, webhooks, SDKs - Compliance: OWASP, DPDP Act, IT Act, audit framework - Add modern theme with dark mode and full-text search - Update Dockerfile for VitePress build process Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
81 lines
2.1 KiB
Markdown
81 lines
2.1 KiB
Markdown
# Workflow Management
|
|
|
|
## Understanding Workflows
|
|
|
|
A workflow defines the approval stages an application passes through before license issuance. Department administrators configure workflows for each license type.
|
|
|
|
## Workflow Components
|
|
|
|
### Stages
|
|
|
|
Each stage represents a review step:
|
|
|
|
| Property | Description |
|
|
|----------|-------------|
|
|
| Name | Stage identifier (e.g., "Document Verification") |
|
|
| Order | Sequence position (1, 2, 3...) |
|
|
| Assignee Rule | Who receives applications at this stage |
|
|
| Required Actions | What must be completed to proceed |
|
|
| SLA | Maximum time allowed |
|
|
|
|
### Stage Types
|
|
|
|
**Sequential**: Applications must pass through in order
|
|
```
|
|
Stage 1 → Stage 2 → Stage 3 → Issuance
|
|
```
|
|
|
|
**Parallel**: Multiple reviews happen simultaneously
|
|
```
|
|
┌→ Technical Review ─┐
|
|
Stage 1 ─┤ ├→ Final Approval
|
|
└→ Financial Review ─┘
|
|
```
|
|
|
|
### Assignment Rules
|
|
|
|
- **Round Robin**: Distribute evenly across available officers
|
|
- **Load Based**: Assign to officer with fewest pending items
|
|
- **Manual**: Supervisor assigns each application
|
|
- **Specific Role**: Route to designated role
|
|
|
|
## Creating a Workflow
|
|
|
|
1. Navigate to **Settings** → **Workflows**
|
|
2. Click **Create New Workflow**
|
|
3. Enter workflow name and description
|
|
4. Add stages in sequence:
|
|
- Define stage name
|
|
- Set assignment rule
|
|
- Configure SLA duration
|
|
- Specify required documents
|
|
5. Set workflow as active
|
|
6. Assign to license type(s)
|
|
|
|
## Modifying Workflows
|
|
|
|
Changes apply only to new applications. In-progress applications continue with their original workflow.
|
|
|
|
To modify:
|
|
1. Open workflow in editor
|
|
2. Make changes
|
|
3. Review impact summary
|
|
4. Confirm and save
|
|
|
|
## SLA Configuration
|
|
|
|
| Field | Description |
|
|
|-------|-------------|
|
|
| Duration | Hours/days allowed |
|
|
| Warning | Alert before breach |
|
|
| Escalation | Action on breach |
|
|
| Override | Manual extension allowed |
|
|
|
|
## Best Practices
|
|
|
|
- Keep stages focused on single responsibility
|
|
- Set realistic SLAs based on actual processing time
|
|
- Use parallel stages for independent reviews
|
|
- Document stage requirements clearly
|
|
- Review workflow performance monthly
|