[ T-09 // TRACK ]
APPS
Workshop apps and closed-loop operations: the surface where a human's workflow actually changes.
- [ FM-WS-01 ]
Build an Ops Board in Workshop: the Error Toast That Lies, the Branch Wall, and the 300px Trap
We built the first Workshop app of the manual: FM-WS-01 maintenance ops board, a single-section module with one object table bound to the demo type [Example] Route Alert (14 objects, 23 properties), published to v0.3.0 at ri.workshop.main.module.ff2edd2c-307b-441c-8605-419e39bfb2c7. The session produced four field repairs. The module creation error toast lied to us verbatim (An error occurred while saving, plus the platform's own typo 'occured'), firing three stacked instances while the module persisted server-side and Save and publish stayed disabled. The object set picker cannot see branch resources at all and answers a Work Order search with 'Refine your search term to find more results.' The Main dropdown in the top bar versions the app, not the ontology. And the default section width, Column width Absolute 300 px, makes a freshly published app look broken until you switch Dimensions to Flex. Plain scope statement: this module is read-only. The Writeback tab exists in the widget catalog and is FM-WS-02's door.
- [ FM-WS-02 ]
Closed-Loop Ops: Action, Writeback, and the Reload That Proves It
We closed the loop FM-ON-02 left open: a real, applied, persistent writeback from a Workshop app. The branch wall from FM-WS-01 blocks our own Work Order action, so the write runs against the main-ontology demo: [Example] Route Alert via the demo action [Example] Update Route Alert Status, wired into the FM-WS-01 module with a Button group and published as v0.4.0. The module's core finding is discoverability: actions are invisible until you know that a button's ON CLICK type select (default Event) hides Action as a separate type, and that filtering the Event submenu for 'action' returns, verbatim, No events found. The Route Alert parameter binds to the table's selected-row variable, Object table 1 Active object. Two real writes executed; the second is fully documented: row Id prefix 27fbc45c96a5ad (Cancellation Rate alert, Low priority, MCO -> EWR, Flight Count 666) went from Status Pending Triage to Resolved, green toast 'Edits successfully applied.', and after a full page reload the value is still Resolved. Four field repairs, including the two verification traps: action forms never prefill current values, and the grid shows the stale value until you reload.