Repository navigation
Workflow Branching Developer Guide 1 Engine
Part 1 of 3 Β· Part 2: the canvas editor Β· Part 3: safety, saving and tests Β· Design and decisions: Workflow branching Β· GH #364 Β· 5.8.0
This page follows a workflow with branches from the database row to the run history: how a branch is stored, how the engine picks a path, what it writes to the step log, and how results flow on. Every snippet is quoted from the code as it ships.
Before 5.8.0 a workflow was a straight line: trigger β conditions β action, action, action. A branch is a fork in that line. It is one more entry in the same list of actions, so:
- a workflow without a branch is stored, loaded and run exactly as before - nothing in the old path changed shape;
- a branch holds its own lists of actions, one per path, and the engine runs the chosen list with the same loop it runs the top level with - so every rule that applies to an action (switched-off modules, dry run, failure stops the run,
{{merge codes}}) applies inside a branch for free.
There are two kinds, and both always have a path for "none of the above":
| Type | Editor name | Picks a path by | Fallback |
|---|---|---|---|
branch_if |
If / Otherwise | each branch's own conditions, matched all or any | otherwise |
branch_switch |
Choose by value | one field's value, matched equals or contains against each case's values | default |
| File | What it holds |
|---|---|
π£ workflow/includes/engine.php
|
BRANCH_TYPES, MAX_BRANCH_DEPTH, executeBranch(), switchCaseMatches(), evaluateOneCondition(), validateActionTree(), normaliseActionTree(), mapActionTree(), the depth-aware executeActionList()
|
π£ includes/webhook_delivery.php
|
webhookMapWebhooks() - credentials encrypted at every depth (part 3) |
π£ api/workflow/save.php, api/workflow/get.php, api/v1/resources/workflows.php
|
The save and load routes (part 3) |
π‘ assets/js/workflow-editor.js, assets/js/workflow-executions.js
|
The canvas and the run history (part 2) |
π§ͺ tests/workflow-branching.php
|
38 checks (part 3) |
No new table and no new column: the branch lives in the JSON the workflows.actions column already held.
-- database/freeitsm.sql (unchanged by branching)
CREATE TABLE IF NOT EXISTS `workflows` (
...
`conditions` TEXT NULL, -- JSON array of {field, op, value}
`actions` TEXT NOT NULL, -- JSON array of {type, args}
...An ordinary action is {type, args}. A branch is the same shape, with its paths inside args. This is the demo workflow from the test install - route new tickets by the requester's company, with a nested If inside one case:
[
{ "type": "log_message", "args": { "message": "New ticket {{ticket.id}}" }, "x": 220, "y": 200 },
{ "type": "branch_switch", "x": 220, "y": 340, "args": {
"field": "ticket.requester_email",
"compare": "contains",
"cases": [
{ "label": "ABC Ltd", "values": ["abc.com"],
"actions": [ { "type": "log_message", "args": { "message": "Route to Team A" } } ] },
{ "label": "XYZ Group", "values": ["xyz.com", "xyz.co.uk"],
"actions": [
{ "type": "log_message", "args": { "message": "Route to Team B" } },
{ "type": "branch_if", "args": {
"branches": [ { "label": "Urgent", "match": "any",
"conditions": [ { "field": "ticket.subject", "op": "contains", "value": "urgent" } ],
"actions": [ { "type": "log_message", "args": { "message": "Page XYZ on-call" } } ] } ],
"otherwise": { "actions": [] } } } ] } ],
"default": { "actions": [ { "type": "log_message", "args": { "message": "Route to the default team" } } ] } } },
{ "type": "log_message", "args": { "message": "Routed: {{last.message}}" }, "x": 220, "y": 960 }
]Things to notice:
-
x/yonly on the top level. They are canvas positions the editor stores; the engine ignores them. Entries inside a path have no position - the path's list order is its order. -
valuesis a list of strings. The editor saves lookup ids as text ("4"), and the engine compares as text, so4and"4"match. -
The fallback is always present.
normaliseActionTree()addsotherwise/defaulton save if a caller left it out (section 6).
Finding branched workflows in SQL is a text search, because the column is TEXT:
SELECT id, name
FROM workflows
WHERE actions LIKE '%"type":"branch\_%';// workflow/includes/engine.php
public const BRANCH_TYPES = ['branch_if', 'branch_switch'];
/** A branch inside a branch inside a branch, and no deeper - past that it is two workflows. */
public const MAX_BRANCH_DEPTH = 3;BRANCH_TYPES is deliberately not part of availableActions(), the action catalogue. The catalogue feeds the editor's action-type dropdown, the REST API's GET /workflow-actions, the AI co-author's list of tools and the save routes' "is this a real action?" check. Keeping branches out of it means none of those offer "branch" as an action - each place that must accept a branch asks for it by name.
Every run - a real event, Test fire, Dry run, a form's own action list - ends up in executeActionList(). It gained a $depth parameter and one early exit:
private static function executeActionList(array $actions, array &$payload, array &$stepLog, bool $dryRun = false, int $depth = 0): array
{
foreach ($actions as $i => $action) {
$type = $action['type'] ?? '';
$args = $action['args'] ?? [];
// GH #364: a branch picks one path and runs its actions through this same loop.
if (in_array($type, self::BRANCH_TYPES, true)) {
$failed = self::executeBranch($type, is_array($args) ? $args : [], $i, $payload, $stepLog, $dryRun, $depth);
if ($failed !== null) return ['failed', $failed];
continue;
}
// ... the ordinary action, exactly as beforeNothing below that if changed for a plain action, with one exception - where its result is stored (section 7).
private static function executeBranch(string $type, array $args, int $index, array &$payload, array &$stepLog, bool $dryRun, int $depth): ?string
{
$entry = ['kind' => 'branch', 'index' => $index, 'type' => $type, 'depth' => $depth];
if ($depth >= self::MAX_BRANCH_DEPTH) {
$entry['status'] = 'failed';
$entry['error'] = 'Branches can only go ' . self::MAX_BRANCH_DEPTH . ' deep.';
$stepLog[] = $entry;
return "Action {$index} ({$type}): " . $entry['error'];
}The depth check is a second line of defence: the save routes already refuse a tree deeper than three (section 6), so this only fires for a row written some other way. It fails the run loudly rather than recursing without limit.
$path = null; // ['key' => 'branch:0' | 'case:1' | 'otherwise' | 'default', 'label' => .., 'actions' => [..]]
if ($type === 'branch_if') {
$entry['checked'] = [];
foreach (array_values(is_array($args['branches'] ?? null) ? $args['branches'] : []) as $bi => $br) {
if (!is_array($br)) continue;
$match = ($br['match'] ?? 'all') === 'any' ? 'any' : 'all';
$conds = array_values(array_filter(is_array($br['conditions'] ?? null) ? $br['conditions'] : [], 'is_array'));
$results = [];
$ok = $match === 'all'; // all: true until one fails; any: false until one passes
foreach ($conds as $c) {
$r = self::evaluateOneCondition($c, $payload);
$results[] = $r;
if ($match === 'all' && !$r['passed']) { $ok = false; break; }
if ($match === 'any' && $r['passed']) { $ok = true; break; }
}
if (!$conds) $ok = false; // a branch with no conditions never matches - it would hide Otherwise
$entry['checked'][] = ['branch' => $bi, 'label' => (string)($br['label'] ?? ''), 'match' => $match, 'conditions' => $results, 'passed' => $ok];
if ($ok) { $path = ['key' => 'branch:' . $bi, 'label' => (string)($br['label'] ?? ''), 'actions' => $br['actions'] ?? []]; break; }
}
if ($path === null) $path = ['key' => 'otherwise', 'label' => '', 'actions' => $args['otherwise']['actions'] ?? []];- Short-circuit both ways. all stops at the first failing condition, any at the first passing one - the same cost as the workflow's own conditions.
-
A branch with no conditions never matches. An empty
allwould otherwise be vacuously true and swallow every run, hiding Otherwise forever. The save routes refuse such a branch anyway; this is belt and braces. -
Every branch tried is logged (
checked[]), not just the winner - so the run history can show why branch 1 was skipped before branch 2 ran.
evaluateOneCondition() is the body of the old evaluateConditions() loop, lifted out unchanged so the workflow's own conditions and a branch's conditions are tested by one implementation - including the category rule (a category condition also matches its subcategories, GH #298):
private static function evaluateOneCondition(array $cond, array $payload): array
{
$field = (string)($cond['field'] ?? '');
$op = (string)($cond['op'] ?? 'equals');
$value = $cond['value'] ?? null;
$actual = self::dotGet($payload, $field);
$tested = $value;
$withSubs = false;
if (in_array($field, self::CATEGORY_FIELDS, true) && in_array($op, ['in', 'not_in'], true) && self::categoryMatchIncludesSubcategories()) {
$tested = self::categoryIdsWithDescendants($value);
$withSubs = true;
}
$out = ['field' => $field, 'op' => $op, 'value' => $value, 'actual' => $actual, 'passed' => self::evaluateOperator($op, $actual, $tested)];
if ($withSubs) $out['includes_subcategories'] = true;
return $out;
}π Proving the refactor changed nothing: every template and every workflow on Ed's install was dry-run through the old engine and the new one with the same payload, and the two step logs compared byte for byte (part 3).
} else {
$field = (string)($args['field'] ?? '');
$compare = ($args['compare'] ?? 'equals') === 'contains' ? 'contains' : 'equals';
$actual = self::dotGet($payload, $field);
$entry += ['field' => $field, 'compare' => $compare, 'actual' => $actual];
$missing = $actual === null || $actual === '' || $actual === [];
if (!$missing) {
foreach (array_values(is_array($args['cases'] ?? null) ? $args['cases'] : []) as $ci => $case) {
if (!is_array($case)) continue;
if (self::switchCaseMatches($field, $compare, $actual, $case['values'] ?? [])) {
$path = ['key' => 'case:' . $ci, 'label' => (string)($case['label'] ?? ''), 'actions' => $case['actions'] ?? []];
break;
}
}
}
if ($path === null) {
$path = ['key' => 'default', 'label' => '', 'actions' => $args['default']['actions'] ?? []];
$entry['reason'] = $missing ? 'missing' : 'no_match';
}
}A missing field goes straight to Default, with reason: missing. That is the whole point of Ed's rule - "the logic should always have a default path so unexpected inputs don't break it". A payload with no requester email, a field renamed by a later version, an empty value: none of them can throw, and the log says which it was.
private static function switchCaseMatches(string $field, string $compare, $actual, $values): bool
{
if (is_string($values)) $values = array_map('trim', explode(',', $values));
if (!is_array($values)) $values = [$values];
$values = array_values(array_filter($values, fn($v) => $v !== null && trim((string)$v) !== ''));
if (!$values) return false;
if ($compare === 'contains') {
foreach ($values as $v) if (self::textContains(is_scalar($actual) ? (string)$actual : null, (string)$v)) return true;
return false;
}
if (in_array($field, self::CATEGORY_FIELDS, true) && self::categoryMatchIncludesSubcategories()) {
$values = self::categoryIdsWithDescendants($values);
}
return self::value_in_list($actual, $values);
}It reuses the engine's existing comparisons rather than writing new ones: textContains() (ignores capitals and the spaces round a typed value - GH #214) and value_in_list() (string-cast equality, so a numeric id matches the saved "4"). A case with no values never matches - an unfinished case cannot catch everything.
$entry['taken'] = $path['key'];
if ($path['label'] !== '') $entry['taken_label'] = $path['label'];
$actions = array_values(array_filter(is_array($path['actions']) ? $path['actions'] : [], 'is_array'));
$entry['nothing_to_do'] = $actions === [];
$inner = [];
$before = $payload['last'] ?? null;
unset($payload['last']);
[$status, $error] = self::executeActionList($actions, $payload, $inner, $dryRun, $depth + 1);
$entry['steps'] = $inner;
$entry['status'] = $status === 'failed' ? 'failed' : ($dryRun ? 'dry_run' : 'success');
$stepLog[] = $entry;- The path runs through
executeActionList()itself, one level deeper - recursion, so a branch inside a path is handled by the same code with no special case. - The path's steps go into their own array (
$inner) and are nested under the branch's entry assteps. The top-level log keeps one entry per top-level item; the history draws the nesting (part 2). -
nothing_to_dorecords an empty Otherwise / Default being taken - it ran nothing, but it was the path, and the run history says so.
The log entry as stored in workflow_executions.step_log - this is the real run #488 on the test install (dan@XYZ.co.uk, subject "URGENT printer"):
{
"kind": "branch", "index": 1, "type": "branch_switch", "depth": 0,
"field": "ticket.requester_email", "compare": "contains", "actual": "dan@XYZ.co.uk",
"taken": "case:1", "taken_label": "XYZ Group", "nothing_to_do": false,
"steps": [
{ "kind": "action", "index": 0, "type": "log_message", "status": "success", "result": { "message": "Route to Team B" } },
{ "kind": "branch", "index": 1, "type": "branch_if", "depth": 1,
"checked": [ { "branch": 0, "label": "Urgent", "match": "any",
"conditions": [ { "field": "ticket.subject", "op": "contains", "value": "urgent",
"actual": "URGENT printer", "passed": true } ],
"passed": true } ],
"taken": "branch:0", "taken_label": "Urgent", "nothing_to_do": false,
"steps": [ { "kind": "action", "index": 0, "type": "log_message", "status": "success", "result": { "message": "Page XYZ on-call" } } ],
"status": "success" }
],
"status": "success"
}| Key | Meaning |
|---|---|
taken |
branch:N / case:N (zero-based) / otherwise / default
|
taken_label |
the path's name, when it has one |
checked[] |
If only: every branch tried, its conditions with actual and passed
|
field, compare, actual
|
Choose only: what was compared |
reason |
Choose only, when Default was taken: missing or no_match
|
nothing_to_do |
the path taken had no actions |
steps[] |
the path's own step log, same shapes, nested |
status |
success, failed or dry_run
|
step_log is TEXT, but MySQL 8's JSON functions read it. Which path did each run of a workflow take?
SELECT e.id, e.started_datetime, jt.taken, jt.reason
FROM workflow_executions e,
JSON_TABLE(e.step_log, '$[*]' COLUMNS (
kind VARCHAR(20) PATH '$.kind',
taken VARCHAR(40) PATH '$.taken',
reason VARCHAR(20) PATH '$.reason')) jt
WHERE e.workflow_id = 143
AND jt.kind = 'branch'
ORDER BY e.id;488 | case:1 | NULL
489 | default | no_match
490 | case:0 | NULL
491 | default | missing
(That reads top-level branches; a nested one is inside its parent's steps, at $[*].steps[*].)
-
Dry run decides for real. Deciding only reads the payload, so a dry run takes the same path a real run would, and only the path's actions are previewed (
status: dry_run,would_run,would_args). That is the useful answer to "what would this do for this ticket?". -
A failing action inside a path fails the run. The inner
executeActionList()returns['failed', ...],executeBranch()returns the message, and the outer loop returns['failed', $failed]- nothing after the branch runs, exactly as when a top-level action fails. The message names the branch:Action 1 (branch_if): Action 0 (set_ticket_priority): ticket_id is required.
Since #95 every action's result is merged into the payload so later actions can use it:
| Merge code | Means |
|---|---|
{{last.message}} |
the action just before this one |
{{steps.2.message}} |
the action numbered 2 on the canvas (one-based) |
mergeStepResult() writes steps[$i + 1]. Inside a path, $i counts within the path - so the first action in a path would write steps[1], overwriting the result of the workflow's first top-level action. Every {{steps.1...}} after it would silently read the wrong thing.
// executeActionList(), for a plain action
// TRAP (GH #364): inside a branch only {{last}} moves - $i counts within the
// branch, so writing steps[$i + 1] would overwrite a top-level action's result.
// The branch puts its last result in its own top-level slot when it ends.
if ($depth === 0) self::mergeStepResult($payload, $i, $result);
elseif (is_array($result) && $result !== []) $payload['last'] = $result;And when the branch ends, what its path produced last becomes the branch's own result:
// What the path produced is the branch's result: in its own slot at the top level,
// so an action after the branch can use {{steps.N...}} whichever path ran.
if (array_key_exists('last', $payload)) {
if ($depth === 0) $payload['steps'][$index + 1] = $payload['last'];
} elseif ($before !== null) {
$payload['last'] = $before; // a path that produced nothing leaves {{last}} as it was
}
return $status === 'failed' ? "Action {$index} ({$type}): " . ($error ?? 'failed') : null;So in the demo, the last action's Routed: {{last.message}} reads "Route to Team A", "Page XYZ on-call" or "Route to the default team" - whichever path ran - and {{steps.2.message}} (the branch is item 2) reads the same.
unset($payload['last']) before the path runs is what lets the code tell "the path produced something" from "it produced nothing": an empty path puts the old {{last}} back rather than pretending the branch produced it.
The test
a nested action never overwrites a top-level stepfails when the$depth === 0guard is removed - checked by removing it (part 3).
dispatch('ticket.created', payload)
ββ run() β runInner()
ββ evaluateConditions() workflow's own conditions (unchanged)
ββ executeActionList(actions, depth 0)
ββ log_message steps[1], last
ββ branch_switch β executeBranch(depth 0)
β ββ requester_email "dan@XYZ.co.uk" contains "xyz.co.uk" β case:1
β ββ executeActionList(case 1 actions, depth 1)
β ββ log_message last only
β ββ branch_if β executeBranch(depth 1)
β ββ subject contains "urgent" β branch:0
β ββ executeActionList(branch 0 actions, depth 2)
β ββ log_message last only
β (branch_if ends: depth 1, so no steps slot)
β (branch_switch ends: steps[2] = last)
ββ log_message "Routed: {{last.message}}" steps[3], last
Continue: Part 2 - the canvas editor.
FreeITSM β an open-source IT Service Management platform Β· github.com/edmozley/freeitsm Β· MIT licence
- Installation
- β° Scheduled tasks (cron jobs)
-
Architecture
- β³ π§Ή Root folder tidy (URL routing)
- β³ π Database Integrity (FKs & constraints)
- β³ π οΈ Database Verification β Developer Guide
- β³ π§© Service Layer (UI + API share code)
- β³ πͺ€ Code traps (the TRAP: comments)
- β³ π Commenting for the Engineering wiki
- β³ π οΈ Engineering wiki scanner - Developer Guide
- β³ π Service-Layer progress
- π€ Contributing (read before a pull request)
- π§ͺ Developer tests
- π PDF exports moved to PDFKit (#254)
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- π Date & Time Formats
- π± Currencies
- π§ The sidebar (optional module rail)
- π§© Preference templates
- π Display order (modules, Watchtower cards) β Developer Guide
- Theming & Dark Mode
- ποΈ Recent β getting back to what you were doing
- β¨οΈ Command palette (βK)
- π Searching inside tickets
- π Attached documents
-
MobileβFriendly
- β³ π« Mobile: Tickets
- β³ π» Mobile: Assets
- β³ π Mobile: Calendar
- β³ π Mobile: Knowledge
- β³ π¦ Mobile: Service Status
- β³ πΌ Mobile: Watchtower
- β³ π§© Mobile: Problem Management
- β³ π Mobile: Change Management
- β³ πΏ Mobile: Software
- β³ β Mobile: Tasks
- β³ π Mobile: Forms
- β³ π Mobile: Contracts
- β³ π Mobile: Domains
- β³ π Mobile: People
- β³ π Mobile: Projects
- β³ ποΈ Mobile: Files
- β³ π Mobile: LMS
- β³ πΊοΈ Mobile: CMDB
- β³ πΊοΈ Mobile: Network Mapper
- β³ π§ Mobile: Process Mapper
- β³ βοΈ Mobile: Workflow
- β³ π₯οΈ Mobile: System
- β³ π Mobile: Reporting
- β³ π Mobile: System Wiki
- β³ π Mobile: Self-Service Portal
- β³ π§° Mobile: Techniques & Tricks
-
Security
- Layer 1 β which modules you can enter
- β³ π§© Module Access Control
- β³ π οΈ Module Access β Developer Guide
- β³ π Switching modules off
- β³ π οΈ Module availability β Developer Guide
- β³ π Module availability β design (#217)
- Layer 2 β what you can administer
- β³ π Roles & Permissions
- β³ π οΈ Roles β Developer Guide
- β³ π€ Why capabilities are constants
- Layer 3 β the System module
- β³ π Admin Access Control
- Hardening
- β³ π Security review response 2026-08
- β³ π‘οΈ Security hardening 2026-08
- β³ π οΈ Security hardening 2026-08 β Developer Guide
- β³ π‘οΈ Round three β plain English
- β³ π οΈ Round three β Developer Guide
- β³ π‘οΈ CSRF protection (S4) β Developer Guide
- Single Sign-On (SSO)
- ποΈ LDAP & Active Directory
-
π¦ Microsoft Entra ID
- β³ π₯ Importing people and groups
- β³ π» Intune: assets to their primary user
- β³ π’ Organisation chart
- β³ π οΈ Entra directory sync β Developer Guide
- β³ π οΈ Entra import - review (#235)
- β³ π οΈ Entra follow-ups - review (#237-#240)
- β³ π οΈ Intune primary user - review (#236)
- β³ π οΈ Intune after an Entra import - review (#334)
- β³ π οΈ Intune primary user history - review (#338)
- β³ π οΈ Intune asset types - review (#339)
- β³ π οΈ Intune scheduled syncs - review (#344)
- β³ π οΈ Microsoft 365 in Integrations - review (#352)
- β³ π οΈ Organisation chart - reviews (#242, #265)
- π CardDAV contact sync
- Browser Extension
- API Reference
-
π REST API β how it works
- β³ π Script library (PowerShell + Python)
- β³ π Proposal: custom fields, inventory import and change evidence (#194)
- β³ π οΈ Custom fields, evidence + inventory - review (#195-#197)
- β³ π οΈ Long forms in a task's Work view - review (#198)
- β³ π οΈ Empty Procedures fold - review (#247)
- β³ π« REST API: Tickets
- β³ π» REST API: Assets
- β³ π΄ REST API: Problems
- β³ π REST API: Changes
- β³ π REST API: Knowledge
- β³ β REST API: Tasks
- β³ ποΈ REST API: CMDB
- β³ π REST API: Contracts
- β³ ποΈ REST API: Calendar
- β³ πΏ REST API: Software
- β³ π REST API: Domains
- β³ π¦ REST API: Service Status
- β³ βοΈ REST API: Morning Checks
- β³ π REST API: Forms
- β³ βοΈ REST API: Workflow
- β³ π·οΈ REST API: Cost centres
- β³ π’ REST API: Companies
- β³ π REST API: Chart of accounts
- β³ π REST API: Projects
- β³ π‘οΈ API threat protection
- β³ π§βπΌ REST API: Analysts
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ Reply subject and replying to one message
- β³ π Live updates
- β³ π οΈ Watching a ticket - Developer Guide (1 of 2)
- β³ βοΈ Ticket address suggestions - Developer Guide
- β³ π οΈ CSAT delay and reminder - Developer Guide
- β³ π οΈ Ticket checklist step types - Developer Guide (1 of 2)
- β³ π οΈ Right-click Attach checklist - Developer Guide
- β³ π οΈ Checklists in the REST API - Developer Guide
- β³ π A ticket's related block and attachments - Developer Guide
- β³ π οΈ Inbox.js map β Developer Guide
- β³ π οΈ Floating windows & the file viewer β Developer Guide
- β³ π οΈ Tickets settings β Developer Guide
- β³ π Simpler ticket and task forms - design (#218)
- β³ ποΈ The ticket workspace
- β³ π Forms on tickets
- β³ π The ticket table
- β³ π Rota copy and paste β Developer Deep Dive
- β³ β Checklists & SOPs
- β³ βοΈ Mandatory fields
- β³ π§Ύ Custom ticket fields
- β³ π·οΈ Ticket categories
- β³ π§Ύ A type for every new ticket
- β³ π₯ Assigning tickets to a team, and escalation
- β³ π’ One board across every company
- β³ π Many companies: searchable lists (#358)
- β³ π Ticket dashboard β Developer Guide
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ βοΈ Emailed reports
- β³ π Attachment size limits and large emails
-
β³ Basic IMAP mailboxes
- β³ π Basic IMAP without the PHP extension (#257)
- β³ π οΈ Basic IMAP client β Developer Guide
- β³ π§ͺ Basic IMAP client β Testing and verifying
- β³ π οΈ Basic IMAP - Sent copy - Developer Guide (#270)
- β³ π€ PR #400 Sending through a relay without a login
- β³ π οΈ Verifying a mail folder β Developer Guide
- β³ π οΈ Mailbox providers β Developer Guide
- β³ π οΈ How Gmail mail collection works β Developer Guide
- β³ Email rendering & images
- β³ SLA Management
- β³ WhatsApp channel
-
β³
βοΈ Telegram channel - β³ β CSAT company scope and filters β Developer Guide
- β³ π₯ Microsoft Teams channel
- β³ π¨οΈ Mattermost channel
- β³ π¬ Web chat channel
- β³ π£ Slack channel
- β³ π Linking tickets
- β³ β Record previews
- β³ π Ticket notes: internal or shared
- β³ ποΈ Canned responses
- β³ βοΈ Limiting replies to particular senders
- β³ π¨ Telling the analyst a ticket is theirs
- β³ βοΈ Email signatures
- β³ π The public web address
- β³ π’ Ticket numbering
- β³ π Raising a ticket for someone else
- β³ π Merging tickets
- β³ π Confidential tickets
- β³ π₯ Portal managers
- β³ π Who has seen a ticket
- β³ π Reading long tickets
- β³ β¨ Reply Cleanup prompt and history
- β³ β Splitting tickets
- β³ β Selecting several tickets
- β³ ποΈ The folder pane
- β³ π½ Just my tickets, or no closed ones
- β³ π οΈ Snoozing tickets β Developer Guide
- β³ π₯ Collision detection
- β³ β±οΈ Time tracking
- β³ π Case reports - a ticket and its work as one PDF
- β³ π Scheduled work in your own calendar
- Problem Management
-
Tasks
- β³ π οΈ Task ID and hover card - review (#405)
- β³ π οΈ Task board and subtasks β Developer Guide
- β³ π§βπ€βπ§ People on a task ("Involved")
- β³ π Repeating tasks
- β³ π’ Moving a task between companies
- π Projects
-
Assets
- β³ π οΈ Asset list by type - review (#340)
- β³ π’ Moving an asset between companies
- β³ π Shared asset locations
- β³ π§βπΌ Assigning assets to analysts
- β³ π Warranty and lease alerts
- β³ π Leases
- β³ π Saved table views
- β³ π¨οΈ Recording anything, and importing it
- β³ π§© Asset type layouts
- β³ π Inventory freshness
- β³ π Linked configuration item
- β³ π Connected assets
- β³ π Asset review
-
β³ π·οΈ QR asset labels
- β³ π οΈ QR asset labels β Developer Guide
- β³ π Asset label designer - design (#229)
- β³ π· Asset scanning β Developer Guide
- β³ π οΈ Asset tag numbering β Developer Guide
- β³ π οΈ Asset reconciliation β Developer Guide
- β³ π οΈ Reconciliation, tags + labels - review (#164)
- β³ π Who holds what, and handover documents
- β³ π₯οΈ The inventory agent (PowerShell)
- β³ ποΈ Proxmox VE servers
- β³ βοΈ VMware Cloud Director servers
- β³ πͺ Hyper-V and Failover Clusters
- β³ π Linking equipment to tickets
- β³ βοΈ Follow-up tasks on a ticket
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
-
Forms
- β³ π¨ The form designer β Developer Guide
- β³ π Layout & the grid β Developer Guide
- β³ ποΈ Collections β grouping submissions
- β³ π Submissions as PDFs
- β³ β‘ What happens next β a form's own actions
- β³ π οΈ Sections & conditional logic β Developer Guide
- β³ π οΈ Lookup fields β Developer Guide
- β³ π‘οΈ Catalogue request approvals
- People
- Starters & leavers
- Domains
- ποΈ Files
- Contracts
- Service Status
- π Notifications
- π¨ War Room
-
Self-Service Portal
- β³ π¨ Branding the portal
- β³ π What people can do
- β³ π Help Centre
- β³ πͺ Landing page
- β³ π¨ Login screen designer
- β³ π οΈ Back to your page after sign-in - review (#407)
- β³ π Request catalogue
- β³ π Portal privacy
- β³ π₯ Portal managers
- β³ π Contact details
- β³ π οΈ Developer guide
- LMS
- Process Mapper
-
CMDB
- β³ π§± Designing your CMDB
- β³ π οΈ CMDB β Developer Guide
- β³ π οΈ Impact analysis β Developer Guide
- β³ π οΈ Data quality β Developer Guide
- β³ π οΈ Record references β Developer Guide
- β³ π οΈ CMDB assistant - Developer Guide
- β³ π Linked assets
- β³ π Linking an asset to its CI - design (#201)
- β³ π Discovery and redundancy-aware impact - design (#199)
- β³ π οΈ Relationship wording - review (#297)
- Network Mapper
-
Workflows
- β³ π Branches: If / Otherwise and Choose by value
- β³ π οΈ Workflow engine β Developer Guide
- β³ π οΈ Workflows for tasks β Developer Guide
- β³ π οΈ Workflow notes on a ticket β Developer Guide
- β³ π οΈ Workflow category routing β Developer Guide
- β³ π Workflows in order, child tickets - design (#304)
- β³ β° Time-Based Triggers
- β³ πͺ Webhooks
- β³ π¬ Webhook Message Formats
- β³ π HTTPS Certificates & CA Bundles
- β³ π οΈ SSL Verification β the Global Setting
- β³ π Workflow & Webhook Pitfalls
- Issue trackers (Jira, Azure DevOps)
- π‘ Zabbix (monitoring)
- π¬ Microsoft Teams alerts
- π 3CX (phone system)
-
System
- β³ π οΈ System cards by topic - review (#347)
- β³ π¦ Microsoft 365 (Entra ID and Intune)
- β³ π οΈ Preferences β Developer Guide
- β³ π§Ή Maintenance
- β³ πΎ Storage usage
- β³ βοΈ Emailed reports
- β³ π Finding people in the Analysts list
- β³ πͺ When an analyst leaves
- β³ π οΈ System β Branding β Developer Guide
- β³ π©Ί Page health (D019) β Developer Guide
- β³ β Feature Bingo
- β³ π Locations
- β³ π·οΈ Cost centres
- β³ π Chart of accounts
- β³ π· Photo Album
- β³ Demo Data
- β³ π οΈ Demo Data β Developer Guide
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ One company supporting another
- β³ π’ One board across every company
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)
- What this is
-
π Bugs resolved
- β³ π #413 Reading pane too narrow on tablets
- β³ π± #412 Sign-in card cramped on phones
- β³ π§ #411 Header buttons out of reach
- β³ π± #386 Project stuck in an old currency
- β³ π₯οΈ #393 Header ran off the screen
- β³ π±οΈ #395 Ticket flyouts ran off the bottom
- β³ π PR #401 Change editor used hardcoded priorities
- β³ π Knowledge drafts could not be published
- β³ π§© #392 Project dialogs shared element ids
- β³ πΌοΈ #391 Knowledge images from your computer
- β³ π #375 REST API wall-clock times
- β³ π #374 Calendar popup ran off the screen
- β³ π’ #373 All companies: Changes, CMDB, Starters
- β³ π’ #356 Assets People and All companies
- β³ π #366 LMS demo data would not import
- β³ π #362/#365 Team handover showed only a name
- β³ π #365 The bell credited the wrong person
- β³ ποΈ #369 Inbox empty until Database Verification
- β³ πͺ #360 Links opened inside the ticket
- β³ π #354 Workspace Links missed tasks
- β³ π Task company checks in the API (5.5.0)
- β³ π Asset holders through the API (5.4.0)
- β³ π Files folder delete did not check inside (5.4.0)
- β³ π The Intune tab did not check the company
- β³ π #332 Files viewer would not open
- β³ π #333 Note attachments downloaded
- β³ πͺ #326/#327 Form webhook Full record
- β³ π #325 Form PDF download failed
- β³ π Small fixes in 5.1.0
- β³ π CMDB relationships read backwards (5.1.0)
- β³ π #301 CSAT delay was never applied
- β³ π #281 Comments imported from Jira never arrived
- β³ π #288 A change failed to open with Enforce approvals on
- β³ π Long non-Latin articles never got an embedding
- β³ π« #280 Email lookups scanned the whole table
- β³ β #266 Dragging a task told nobody
- β³ π #255 Article previews showed HTML codes
- β³ π #252 A link to a Knowledge article did not open
- β³ π #254 PDFs could not print Polish
- β³ π #250 Clicking a folder left the open article on screen
- β³ π« #260 The dashboard cog did nothing
- β³ π« #248 A department rule never matched on four routes
- β³ π A directory account could be matched to someone else
- β³ π« #244 Reply went to the assigned analyst
- β³ π Mailbox sign-in was not checked
- β³ π Four weaknesses around signing in
- β³ π A lookup answer could name any record
- β³ π« #227 A mailbox could not be deleted
- β³ π« #226 A picture on a note could not be closed
- β³ π» #222 The Assets page never loaded in 4.3.0
- β³ βοΈ #214 A "contains" condition did not match capitals
- β³ βοΈ #216 A workflow email from a chosen mailbox always failed
- β³ π³ The Docker image was missing PHP extensions
- β³ π A failed DNS lookup read as a missing record
- β³ π A link could change data
- β³ π Access outlived its removal
- β³ π Knowledge articles could run scripts
- β³ π Knowledge writes ignored permissions
- β³ π Company boundaries (Oct 2026)
- β³ π Smaller gaps (Oct 2026)
- β³ π Escaped text could leave its attribute
- β³ π Task descriptions were not cleaned
- β³ π Task documents ignored company scope
- β³ π Repeating tasks ignored company scope
- β³ π¬ #183 Mailbox checks overlapped
- β³ π #188 Transfer lock shown off when unknown
- β³ β #184 Subtask names and Overdue
- β³ π§© #186 Teams: the buttons did nothing
- β³ π Text in a change could run script
- β³ π AI settings changed without the AI permission
- β³ πͺ #178 Deleting an analyst failed
- β³ π« A team with no departments showed 0 tickets
- β³ π Projects: adding a phase did nothing on Save
- β³ π Leavers could still sign in
- β³ πΌοΈ Logo and courses broke on Apache with PHP-FPM
- β³ π’ Chat tickets ignored your ticket numbering
- β³ π Dates shown as a dash, or in server time
- β³ π Assets β Users showed people from other companies
- β³ π Restricted analysts could read other modules' data
- β³ πΌοΈ Replies with a picture in the thread failed to send
- β³ π Reply attachments never reached the customer
- β³ π οΈ Outbound email attachments β Developer Guide
- β³ π A global SSO provider was missing from the portal
- β³ π Behind a proxy, the SSO redirect said http
- β³ βοΈ The portal tagline moved when you saved it
- β³ π¨ The portal settings screen forgot what you saved
- β³ π‘οΈ The approvals inbox said "Error" and nothing else
- β³ π A table's answers were missing from the PDF
- β³ β A single-select column let you tick every option
- β³ π The portal ignored a form's field widths
- β³ π The tasks board stopped taking clicks
- β³ ποΈ #121 The index list is out of date after upgrading
- β³ π #133 The calendar subscription was empty
- β³ π #131 Tasks always reopened on the board
- β³ π₯ #129 Every page returned HTTP 500 after upgrading
- β³ π³ #127 A PHP warning above the System page
- β³ π #126 Notes stamped with the server's clock
- β³ π Storing every date in UTC
- β³ πͺ The portal was down for everyone signed in
- β³ βοΈ #120 Workflow notes could never be written
- β³ βοΈ #123 Three errors when running Database Verification
- β³ π #122 The description box was a stub in the corner
- β³ π£ Demo data deleted real accounts
- β³ π #117 Sign-in redirected to the wrong address
- β³ π¨ #108 The priority dot was invisible
- β³ β±οΈ #116 Time logged from the right-click menu
- β³ π #114 API keys refused by our own guard
- β³ ποΈ #110 Assigning a task told nobody
- β³ πͺ #107 Signed out while still working
- β³ π #103 "Share with Requester" reached nobody
- β³ π #102 Search found nothing for hyphens
- β³ πͺ #101 Source code editor opened behind
- β³ βοΈ #88 Subtasks could not be ticked off
- β³ π» #84 Asset deep link selected nothing
- β³ π« #79 A new ticket arrived with no status
- β³ π§ #79 A ticket from email did not say so
- β³ π #78 Bell opened to nothing
- β³ π¬ #77 Mail only collected from Inbox
- β³ π #74 The default password could not be changed
- β³ π¦ #70 Renaming an impact level
- β³ π€ #67 App-only mailboxes could not send
- β³ π #45 Verify only ever worked for Microsoft
- β³ π #45 IMAP reported as not authenticated
- β³ βοΈ An email template stopped escaping itself
- β³ π The portal dashboard showed the wrong time
- β³ π’ The folder said 99 and the list showed 96