Task Lifecycle & Execution — business view

Technical trace: Task Lifecycle & Execution

1. Business Summary

Tasks are the executable units of localization production: assigned, scheduled, accepted, delegated, rejected, verified, closed. Each task is the basis for vendor cost, internal cost, and quality measurement.

2. Business Value

Atomic accountability for delivery, cost, and quality.

3. Users / Stakeholders

PMs, vendors/resources, reviewers, vendor managers, finance.

4. Workflows

  • Auto-creation from auto-planning. Tasks are produced from job phases, with start/end dates, type, and amount.
  • Manual creation. PMs create or adjust tasks via UI or mobile API.
  • Assignment & delegation. Resource selection or RFR finalises the assignee; partial or full delegation is supported.
  • Acceptance / rejection. Vendors accept or reject via web/mobile; rejection captures the reason.
  • Verification & closure. Verification completes; deliverable files flow back to the OUT folder; the PM closes the task.
  • Logging. Logs, vendor availability records, and working-day records track activity.

5. Sub-Features

  • Per-phase or per-file task scheduling.
  • Delegation paths (partial / full).
  • Task rejections with reasons.
  • Vendor availability tracking per task.
  • Checklists per task type.

6. Business Rules

  • Tasks belong to a job and a phase; phase scheduling is sequential.
  • Risk factor reduces available time.
  • Approval status drives downstream finance availability.
  • Submitted approved evaluations queue background processing.

7. Data Entities

Task, Task Log, Task Rejection, Task Relation, Task Vendor Availability, Task Working Day, Task Checklist, Task Status, Approval Status, Evaluation Template.

8. Entry Points

  • Task screens.
  • Mobile API actions (accept/reject/upload/download).
  • TMS task assignment.
  • Auto-planning.

9. Inputs & Outputs

  • Inputs: job, phase, type, dates, assignee, files.
  • Outputs: Task record, logs, vendor invoice eligibility.

10. Integrations

  • Finance (vendor invoice, internal invoice).
  • Resource selection.
  • TMS file flow.
  • Email/push alerts.

11. Calculations / Logic

  • Time-share % per task type per phase.
  • Productivity rates drive capacity.

12. Status Lifecycle

  • Created → assigned → in-progress → completed → verified → closed (or rejected/cancelled).
  • Approval status: pending → approved/rejected.

13. Permissions

  • PM, vendor, reviewer, VM, finance.

14. Reports & KPIs

  • On-time delivery, rejection rate, productivity, vendor utilisation, evaluation scores.

15. Risks & Observations

  • State transitions are not enforced by a formal state machine; the UI/components carry the logic.
  • Status change has cascading finance and TMS effects.
  • TMS-task-close timing is sensitive to external dependencies.

16. Source Code Evidence

  • app/Plugin/projects/Model/{Task, TaskLog, TaskRejection}.php.
  • app/Controller/TmsController.php.
  • app/Controller/Component/AutomationComponent.php (auto-planning).

← Deep dives index