# Slice 7 (deferred) — a module with workflow

> **STUB. DEFERRED.** Activiti is wired into the codebase (`xlyFlow` module,
> `act_*` schema, two Activiti versions in `xlyPersist`/`xlyFlow`), but in
> this dev DB (`xlyweberp_saas_ai`) every workflow table is empty:
> `act_re_procdef`, `act_ru_task`, `act_hi_procinst`, `biz_flow`,
> `biz_todo_item`, `gdsmoduleflow`, `sysflowsendtointerface` — all zero rows.
> No process is deployed; no task is running. Workflow is dormant in this
> environment.
>
> Originally this was Slice 2; the slot was reassigned to
> [multi-tenancy](02-multi-tenancy.md), which IS observable here. This slice
> will be filled when a DB with active flows is available, OR when we choose
> to document Activiti as a code-derived hypothesis only.
>
> Outline (when ready):
>
> 1. A module with an approval/review step (e.g., quotation → review →
>    sales order).
> 2. The Activiti tables: `act_re_*` (definitions), `act_ru_*` (running),
>    `act_hi_*` (history); the version skew (5.17 in `xlyPersist`, 6.0 in
>    `xlyFlow`).
> 3. xly's wrapper layer: `biz_flow`, `biz_todo_*`, `gdsmoduleflow`,
>    `CheckFlowController`.
> 4. The end-to-end trace from "click submit" → process instance start →
>    task assignment → approver action → process complete.