Repository navigation
Workflow Branching Developer Guide 3 Safety and Tests
Part 1: the engine Β· Part 2: the canvas editor Β· Part 3 of 3 Β· Workflow branching - design Β· GH #364
Branching changed the shape of a column that a dozen pieces of code read. This page lists every one of them, shows the two that would have broken quietly, the save-time rules, how "existing workflows are unchanged" was proved rather than assumed, and the tests. If you are about to change anything that reads workflows.actions, read section 1 first.
Before writing any engine code, every place that reads or writes workflows.actions (and a form's own action lists, which share the shape) was found with a search for ['actions'], "actions" and actions LIKE. Each had to be one of: taught about branches, safe because it calls the engine, or safe because it only searches text.
| Reader | Before | Now |
|---|---|---|
WorkflowEngine::executeActionList() |
flat loop | branches go to executeBranch(); recursion handles nesting (part 1) |
| Switched-off module check (GH #217) | inside the loop | applies inside paths automatically - same loop |
api/workflow/save.php |
each top-level type checked against the catalogue |
validateActionTree() + normaliseActionTree()
|
REST POST /workflows, PATCH /workflows/{id}
|
apiValidateWorkflowActions(), catalogue only |
also accepts BRANCH_TYPES, then the same tree rules |
webhookEncryptActions() / webhookDecryptActions()
|
top level only |
webhookMapWebhooks(), every depth - section 4
|
api/workflow/get.php (the editor's copy) |
own top-level loop |
webhookMapWebhooks() - section 4
|
Forms' "when submitted" lists (includes/services/forms.php, api/forms/get_form.php) |
use the webhook helpers | fixed by the same helper fix; the form editor does not offer branches |
| Execution log, editor's Recent runs | flat step log | recurse through steps (part 2) |
Feature Bingo cards, the job registry (actions LIKE '%send_webhook%') |
text search |
unchanged and still right - LIKE finds text at any depth |
api/workflow/list.php, REST actions_count
|
do not walk actions / count the top level | unchanged; a branch counts as one step |
"It shouldn't change anything" is a claim; this is how it was checked. A script dry-runs every workflow in the test database with a fixed payload, through the engine loaded from a given folder - once from the live code (freeitsm-app, before branching) and once from the new code (freeitsm-prtest) - and writes each run's full result (status, step log, error) to a file:
// br_regress.php <engine-root> <out.json> - the test install's DATABASE, the given folder's ENGINE
require $root . '/workflow/includes/engine.php';
$payload = ['ticket' => ['id' => 0, 'subject' => 'Printer urgent', 'requester_email' => 'ann@abc.com',
'priority_id' => 4, 'status_id' => 1, 'category_id' => 1, 'assigned_team_id' => 1], ...];
foreach ($c->query('SELECT id FROM workflows ORDER BY id')->fetchAll(PDO::FETCH_COLUMN) as $id) {
$r = WorkflowEngine::manualFire((int)$id, $payload, true); // dry run: nothing written but the run row
unset($r['execution_id']);
$out[$id] = $r;
}
$c->exec("DELETE FROM workflow_executions WHERE id > $maxBefore"); // and that row is removedThe workflows compared:
- all 27 starter templates, created as inactive copies;
-
Ed's 4 real workflows - their definitions read with a
SELECTfrom his install and copied to the test install as inactive rows (nothing written to his install); - run twice: as stored, and again with every copy's conditions cleared, so that workflows whose conditions did not match the sample payload still had every action previewed.
| Pass | Workflows | Identical | Action previews compared |
|---|---|---|---|
| As stored | 32 | 32 | 22 + condition checks |
| Conditions cleared | 32 | 32 | 42 |
The only difference in either pass was the branching demo itself, which the old engine cannot run at all (Unknown action type: branch_switch) - as it should. The copies were deleted afterwards.
tests/workflow-branching.php - run from a test install, never a real one:
php tests/workflow-branching.php
It creates ZZ workflows made of Log a message actions whose text names the path, fires them with WorkflowEngine::manualFire(), and reads which messages were logged at any depth:
/** The messages the run logged, in order, at any depth. */
function messages(array $steps): array
{
$out = [];
foreach ($steps as $s) {
if (($s['kind'] ?? '') === 'action' && isset($s['result']['message'])) $out[] = $s['result']['message'];
if (($s['kind'] ?? '') === 'action' && ($s['status'] ?? '') === 'dry_run') $out[] = 'DRY:' . ($s['would_args']['message'] ?? '');
if (($s['kind'] ?? '') === 'branch') $out = array_merge($out, messages($s['steps'] ?? []));
}
return $out;
}Fixtures go in through the same validateActionTree() β normaliseActionTree() β webhookEncryptActions() chain save.php uses, and are removed - with their runs - in a finally block. Log a message writes nothing but the run history, so the test touches no tickets.
| Section | Checks |
|---|---|
| 1. If / Otherwise | first matching branch; contains ignores capitals; else-if with any matching on its second condition; nothing matching β Otherwise; every branch tried is logged |
| 2. Choose by value | contains (abc.com in ann@abc.com); several values; no match β Default (no_match); missing field β Default (missing), run still succeeds; equals matches number 4 to saved "4"; an empty Default is still logged as taken |
| 3. Default always there | a Choose saved without Default gets one; an If without Otherwise gets one; comma-separated values become a list; a list without branches is stored exactly as it was |
| 4. Results | after a branch, {{steps.N}} / {{last}} are the path's last result; a nested action never overwrites a top-level step
|
| 5. Nesting | two deep runs both paths; inner Default; four deep refused with a message; three deep allowed |
| 6. Dry run, failure | dry run decides for real, previews only the path; a failing action inside a branch fails the run and stops it |
| 7. Validation | no branches, no conditions, no field, an unknown action type inside a path - each refused; plain actions still pass |
| 8. Webhooks | a URL inside a case and inside Default is encrypted at rest; decrypts back to exactly what was saved |
| 9. Control | a workflow with no branches runs as before, results chained; unmatched conditions still give skipped
|
38 checks. And the test was itself tested - each guard removed, the suite run, the guard put back:
| Removed | Result |
|---|---|
the $depth === 0 guard round mergeStepResult()
|
2 checks fail (the nested-overwrite checks) |
| Otherwise / Default never being taken | the run crashes before the summary - caught |
The rest of the workflow suite was run against the new code as well: workflow-company-scope (87), workflow-category-routing (24), workflow-task-actions (23), webhook-delivery-settings (23), workflow-attach-checklist-scope (13), workflow-ticket-note (11), form-webhook-full-record (9), workflow-form-fanout (7), workflow-set-ticket-field (7), workflow-full-record (4), workflow-contains - all pass.
The editor was checked by scripts driving a headless browser: load the demo, add a Choose from the toolbar, + Action and + If inside a case, try to delete Default (refused, lane count unchanged), add and remove a case, Save - then read the stored JSON back. A separate round trip loads a branched workflow and saves it untouched; the stored JSON (positions aside) was byte-identical.
A webhook action's URL and signing secret are encrypted at rest. The helper that did it looked only at the top level:
// before - includes/webhook_delivery.php
function webhookEncryptActions(array $actions): array {
foreach ($actions as $i => $a) {
if (!is_array($a) || ($a['type'] ?? '') !== 'send_webhook') continue;
...A webhook inside a branch would therefore have been stored in plain text. Worse, the editor's loader (api/workflow/get.php) had its own top-level-only decrypt loop - so if a nested webhook had been encrypted, the editor would receive it still encrypted, show the ciphertext as the URL, and the next save would encrypt the ciphertext again. The webhook would stop working, silently, the first time anyone saved the workflow.
Both now use one walker:
/**
* Every send_webhook action in a list through $fn - at ANY depth (GH #364).
*
* TRAP: a workflow's actions can hold branches (branch_if / branch_switch) with their own
* action lists. A walker that looks only at the top level stores a webhook inside a branch
* in plain text, and - worse - the editor gets it back still encrypted and the next save
* encrypts it again, so the webhook silently stops working. Self-contained on purpose
* (this file is loaded without the workflow engine); the shape matches
* WorkflowEngine::mapActionTree().
*/
function webhookMapWebhooks(array $actions, callable $fn): array {
foreach ($actions as $i => $a) {
if (!is_array($a)) continue;
$type = $a['type'] ?? '';
if ($type === 'send_webhook') { $actions[$i] = $fn($a); continue; }
if ($type !== 'branch_if' && $type !== 'branch_switch') continue;
$args = is_array($a['args'] ?? null) ? $a['args'] : [];
foreach (['branches', 'cases'] as $listKey) {
foreach (is_array($args[$listKey] ?? null) ? $args[$listKey] : [] as $j => $path) {
if (is_array($path['actions'] ?? null)) $args[$listKey][$j]['actions'] = webhookMapWebhooks($path['actions'], $fn);
}
}
foreach (['otherwise', 'default'] as $k) {
if (is_array($args[$k]['actions'] ?? null)) $args[$k]['actions'] = webhookMapWebhooks($args[$k]['actions'], $fn);
}
$actions[$i]['args'] = $args;
}
return $actions;
}
function webhookEncryptActions(array $actions): array {
return webhookMapWebhooks($actions, function (array $a): array {
foreach (['url', 'secret'] as $k) {
if (isset($a['args'][$k]) && $a['args'][$k] !== '') $a['args'][$k] = webhookEncrypt((string)$a['args'][$k]);
}
return $a;
});
}// api/workflow/get.php - the editor's copy, decrypted (or hidden from a reader who cannot edit) at every depth
$canEdit = !empty($wf['can_edit']);
$wf['actions'] = webhookMapWebhooks($wf['actions'], function (array $a) use ($canEdit): array {
foreach (['url', 'secret'] as $k) {
if (isset($a['args'][$k]) && $a['args'][$k] !== '') $a['args'][$k] = $canEdit ? webhookDecrypt((string)$a['args'][$k]) : '(hidden)';
}
return $a;
});At run time nothing changed: action_send_webhook() decrypts its own url / secret at the point of use, so an encrypted value works at any depth.
{{steps.N}} is written by position, and a position inside a path is not a position in the workflow. See part 1, section 7.
Both save routes run the same two calls on the whole tree:
// api/workflow/save.php
// GH #364: at every depth - a branch's paths hold actions too - and every branch gets
// its Otherwise / Default, so an unexpected value always has somewhere to go.
if (($treeError = WorkflowEngine::validateActionTree($actions)) !== null) {
echo json_encode(['success' => false, 'error' => $treeError]);
exit;
}
$actions = WorkflowEngine::normaliseActionTree($actions);// api/v1/resources/workflows.php - apiValidateWorkflowActions()
if (!isset($catalogue[$type]) && !in_array($type, WorkflowEngine::BRANCH_TYPES, true)) {
apiError(422, 'invalid_field', "actions[{$i}]: unknown action type '{$type}'. See GET /workflow-actions.");
}
...
if (($treeError = WorkflowEngine::validateActionTree($out)) !== null) {
apiError(422, 'invalid_field', $treeError);
}
return WorkflowEngine::normaliseActionTree($out);Recursive; returns the first problem as a sentence that names where it is, or null:
public static function validateActionTree($actions, int $depth = 0, string $where = 'actions'): ?string
{
if (!is_array($actions)) return "{$where} must be a list.";
$catalogue = self::availableActions();
foreach (array_values($actions) as $i => $a) {
$at = "{$where}[{$i}]";
...
if (isset($catalogue[$type])) continue;
if (!in_array($type, self::BRANCH_TYPES, true)) return "Unknown action type: {$type}";
if ($depth + 1 > self::MAX_BRANCH_DEPTH) return "{$at}: branches can only go " . self::MAX_BRANCH_DEPTH . ' deep.';
if ($type === 'branch_if') {
$branches = $args['branches'] ?? null;
if (!is_array($branches) || !$branches) return "{$at}: an If needs at least one branch.";
foreach (array_values($branches) as $bi => $br) {
$n = $bi + 1;
if (!is_array($br) || !is_array($br['conditions'] ?? null) || !$br['conditions']) return "{$at}: branch {$n} needs at least one condition.";
foreach ($br['conditions'] as $c) {
if (!is_array($c) || trim((string)($c['field'] ?? '')) === '') return "{$at}: branch {$n} has a condition with no field.";
if (!isset(self::availableOperators()[(string)($c['op'] ?? 'equals')])) return "{$at}: branch {$n} has an unknown operator.";
}
if (($e = self::validateActionTree($br['actions'] ?? [], $depth + 1, "{$at} > branch {$n}")) !== null) return $e;
}
if (($e = self::validateActionTree($args['otherwise']['actions'] ?? [], $depth + 1, "{$at} > otherwise")) !== null) return $e;
} else {
... // a field, at least one case, then each case's and Default's actions
}
}
return null;
}So an unknown action deep inside a path is refused with its address - e.g. actions[1] > case 2 > .... Over the API:
POST /api/v1/workflows {"actions":[{"type":"branch_switch","args":{"field":"","cases":[]}}], ...}
422 {"error":{"code":"invalid_field","message":"actions[0]: Choose by value needs a field."}}
Checked over HTTP on the test install with a temporary key: that request got exactly that reply; a valid branched workflow sent with "values": "abc.com, abc.co.uk", no Default and a webhook inside its case was stored with values as a list, an empty Default added, and the webhook URL encrypted.
Writes back only the keys the engine reads, gives every branch its fallback, turns "a, b" into ["a","b"], and keeps x / y on top-level entries. A plain action passes through untouched ($out[] = $a), which is why a workflow with no branches is stored byte-for-byte as before - a check in the test file.
The engine-side twin of webhookMapWebhooks(), for any future code that must touch every plain action at any depth:
$actions = WorkflowEngine::mapActionTree($actions, function (array $action): array {
// ... change and return it
return $action;
});Adding a third branch type (say, "run every path"): add it to BRANCH_TYPES; teach executeBranch(), validateActionTree(), normaliseActionTree() and mapActionTree() its shape; add its list keys to webhookMapWebhooks() (which deliberately does not depend on the engine); then the editor's branchFromStored() / branchToStored() and the run history's branchTakenText(). The test file's section 8 is the one that catches a forgotten walker.
Offering branches in a form's action list: the engine already runs them (runActionList() goes through executeActionList()). What is missing is the form editor's UI, and includes/services/forms.php validating the tree with validateActionTree().
Letting the AI co-author write branches: api/workflow/ai_compose.php describes the catalogue to the model; branches would need describing separately, and the AI's proposal validated with validateActionTree() before Apply.
-
TRAP: never
foreachover the top level of an actions list when you mean "every action". UsewebhookMapWebhooks()/WorkflowEngine::mapActionTree(). Listed on Code traps and in the engine guide. -
TRAP: inside a branch, never call
mergeStepResult()- see part 1. -
A branch is not in
availableActions(). Code that validates "is this a known action?" against the catalogue alone will reject every branched workflow - checkBRANCH_TYPESas well, as the REST API now does. -
The fallback is the last lane. The editor relies on it (
splice(length - 1, 0, ...));branchFromStored()always pushes it last, so it cannot drift. -
Lookup values are text. The editor saves
"4"; the engine compares as text; keep it that way. -
step_lognests. A tool that readsstep_logand expects a flat list of actions will miss every action inside a branch - walksteps, as the run history and the test'smessages()do. (The Watchtower "needs a look" check searches the JSON text for"attention":, so it still finds a note left by a nested action.)
Workflow branching - design Β· Workflows Β· Workflow engine - Developer Guide Β· Code traps
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