Workflows

Document version: 2.2 Status: Process definitions + publish to the app desktop + inspection/approval templates available (Web + mobile to-dos) Voice: For product, operations, and integrators.

Related: 工作流与合规.md, 工作区应用.md, 服务通知.md, HR platform plugin

---

1. Up front

Cadau provides a Workflows top-bar module (same level as Agents and Skills center) to:

1. Create in-workspace process definitions from platform templates;
2. Publish to the app desktop (optional);
3. Manage instances and My to-dos (including service-notice reach and handling on mobile).

Recommended templates: IWAY factory audit, blank process, simple approval. Classic “on-site compliance inspection” still works; migrating to the generic-engine template is suggested.

---

2. Four-layer model

---

3. User path

1. Top-bar feature menu → Workflows
2. Create from template → fill a name → optional “publish to the app desktop after create” (default not published)
3. Suite is chosen only at publish: ungrouped (straight onto the desktop), an existing suite, or a new suite; you may not publish and only use it in the Workflows module
4. In My processes, open to start an instance: fill the start-node form; if the form has an org-department multi-select field, tick departments (from HR); when needed pick approver/handler (employees already bound to a Cadau account)
5. Publish / unpublish / archive
6. Front-line people enter handling from the Apps desktop (if published), My to-dos (to-do / submitted by me / handled by me), or Service notices (Web / phone)

Start-page copy and fields all come from process design (start-form node title/description/submit-button copy and field list). Platform templates (factory audit, simple approval) only prefill these parameters at create time; they do not hard-code the UI at runtime by template.

Org-data convention:

• Departments and employees follow the HR system-level plugin; do not create new “department / plant” workspace apps, and the start side no longer uses a “plant” concept.
• Handler resolve is still a Cadau user_id: the UI picks from HR employees and writes their mindlink_user_id.
• Old processes that still carry a historical departments_app_id fall back to that only when HR is unavailable.

---

4. HTTP API (/workspaces/{id}/workflows)

Workspace business duties (collaboration API, not /workflows prefix): GET/POST /workspaces/{id}/duties, plus PATCH/DELETE of …/duties/{dutyId}, members and pack-grants.

Compliance-specific: /frameworks, /compliance/knowledge-status still exist.

Conversation tools (work assistants): workflow_list / workflow_create / workflow_start.

---

5. Implementation mapping

---

6. Later (P3)

• [ ] To-do due reminders (scheduled scan)
• [ ] Multi-level approval chains and automatic routing by workspace role
• [ ] Hard delete after archive / export an audit pack