Name no values for ui-uri-type The names are agreed between a workflow module and its cockpit user interface. VanillaBP knows none of them. Whether a page is opened as it is depends on ui-uri-path: an address starting with http:// or https:// is opened unchanged, every other path gets the proxy route in front. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CUpgqpc9KNeUtRSheAYiAg (cherry picked from commit 561631cdb4986f3f0600ce2358d745848898b96f)
Plain English for what came after 1240 (story 1478) The pages got new text after the plain English pass of story 1240. Long sentences are split, a semicolon between two thoughts became a full stop, and "passed over" became "skipped" or "ignored". No key, link or statement changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BMPbYLKJQXaj22EoiKBWCR
Story 1466: drop the fetch-variables key from the wiki The Process-Engine-API adapter no longer has the key. A start which still sets it ends. Configuration lists the one key left, and Home says to read everything else from the workflow aggregate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BMPbYLKJQXaj22EoiKBWCR
The smallest configuration names an initiator source A module which reports to the cockpit does not start without `initiator-source`, so an example which leaves it out is an example which does not work. The home page is what somebody copies from, so the key stands in that example now, with `by-application` as the value, because a reader who copies it builds an application with real users. Three sentences say what each of the two values means and that the key has no default. The Configuration page promised that one boot reports every gap of the application. It does not: a missing initiator source ends the start before the one key of this half is read, so that key's own message never appears. The sentence now promises what the page can keep. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgjUTvgpirJN5h3qXssjcy
The initiator source a workflow module answers The table of a workflow module's keys left out `initiator-source`, which is the only one of them with no default. A module which reports to the cockpit and answers it nowhere does not start, so a reader who follows the page and never meets the key learns about it from a failing boot. The row says what each of the two values means and where else the key is read. A single workflow may answer it too, which is why the sentence below the table now counts four keys, and why the example of a workflow's own section shows it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DgjUTvgpirJN5h3qXssjcy
The report is built when the task is delivered The Business Cockpit used to put a report together while it sent the outbox entry. It now builds the report at the event and lets it travel inside the entry, so what the report says is what the task looked like when the engine handed it over. Home shows the new order in the sequence diagram and says what a details provider failing on the delivery thread costs. The row about a restart says what a fresh node can and cannot do, which is no longer "the report has no details" but "there is nothing to answer later questions with". Configuration says the same about the one key of this half. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0174TibVeR5rFgHncP6y46oW
Configuration page in plain English Split the long sentences of the page from story 214 into short main sentences, so that a reader of English as a second language does not have to read one twice. No key, no default and no table row changed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> (cherry picked from commit a006b74149112f40580512a188c4172edd9c287a)
Say where the cockpit's keys stand, which is where version 1 had them This integration has no version 1, but its configuration is the Business Cockpit's, and that one kept the keys version 1 read: `vanillabp.cockpit` for the whole application, the `cockpit` section of a workflow module, and the `cockpit` sections of a single workflow and of one of its user tasks. An application which comes here from another engine brings its configuration along unchanged. The transport table gains what it was missing next to the other two BPMS pages: the two switches, the basic-authentication switch, the timeouts, the proxy, the truststore and the client-credentials flow all work here, because they are the shared half's and not a BPMS'. The one key of this half says where it stands and what happens to one written below a workflow module. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YU73krA4jKHuWYB155np2X
Say that the observer bean is a stopgap, and what a module may not configure The wiki told an application to call the observer bean without saying that the bean goes once the Process-Engine-API adapter offers the seam, and it linked GAPS.md at a path on main which does not hold it. It also promised a count of gaps which the file decides, and it left out that the remembered-user-tasks setting written below a workflow module ends the boot. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YU73krA4jKHuWYB155np2X
Describe the Process-Engine-API half of the Business Cockpit Home explains what the extension does, what has to hand it a user task and why nothing of it appears in a BPMN file. Configuration names every key the cockpit reads plus the one this half adds, and the two keys of the engine adapter which change what the cockpit gets to see. There is no version-1 table because there was no version 1. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YU73krA4jKHuWYB155np2X