Release Notes — 15 May 2026

Eight new phases of the P15 Workflow Management system shipped:

Phase G — Checklists, Subtasks & Case Lifecycle
Each workflow step can now have a checklist of subtasks. Cases (workflow instances) have a full lifecycle: open → in-progress → on-hold → closed → reopened. Lifecycle transitions are logged in the IX audit table.

Phase H — Decision Tables & Rule Versioning
Decision tables map input conditions to output actions (e.g. “if Priority = Critical AND Type = Bug → assign to Senior Developer”). Rules have version history — previous versions are retained and can be restored. See admin/decision-tables.php, admin/decision-table-edit.php.

Phase I — Workflow Versioning, Cloning & JSON Import
Workflow definitions are versioned. Workflows can be cloned to create a variant. JSON import/export allows workflows to be designed externally and imported, or exported for backup and migration.

Phase J — Drag-and-Drop Form Builder
Step nodes in a workflow can have a custom data capture form, built via a drag-and-drop form builder. Field types: text, textarea, select, date, checkbox, file upload.

Phase K — Bottleneck Analysis, Process Mining & Heat Maps
Analytics overlay for workflow administrators: identifies bottleneck steps (high average dwell time), renders a process-mining flow diagram showing actual vs. designed paths, and heat maps of step completion rates.

Phase L — Activity Feed, Comments & @Mentions
Each workflow case has a real-time activity feed. Users can post comments, @mention team members (triggers an in-platform notification), and attach notes to any step. Feed auto-refreshes via polling.

Phase M — Workflow Webhooks (Event Bus)
Workflow events (case created, step completed, SLA breached, case closed) can trigger outbound webhooks to external systems. Configurable per workflow, per event type.

See: Webhooks

Phase N — Shared Workflow Template Library
Organisation-level template library. Workflow administrators can publish a workflow as a template; other associations in the organisation can apply the template to create a pre-configured workflow. See admin/template-library.php.

See: Workflow Canvas

Rule-based automation for learning events (admin/lms-rules.php, migration K64). Triggers: lesson completed, quiz passed, badge earned, cohort joined, course enrolled. Actions: enrol in another course, issue a badge, send an email notification, log to xAPI, add to a cohort. Rules are configured visually and evaluated by the cron worker.

Lessons and materials now follow a formal content status lifecycle: Draft → Under Review → Published → Archived. Educators submit content for review; reviewers approve or return with feedback. Published status is required before content is visible to learners. Status transitions are logged with timestamp and actor.

Four major additions to the Collection API:

• Swimlanes (Phase I) — enableswimlanes, createitemgroup, movetogroup, archiverecord, restorerecord, listarchived, duplicaterecord
• Row-Level Security (Phase J) — enablerls, setrls, getrls, myrecords, transferownership, allocaterecord
• Bulk Create — bulkcreate batch-creates up to 500 records in one API call
• Webhooks (Phase G) — collections can emit outbound webhook events on record create/update/action

See: Building Collections · Webhooks