Optional technical reference. This material is for developers, integration specialists and platform administrators. For the consultant lesson, read the practical guide.
Preserved from source baseline
d4587c7c0e073e58c2d430342f65ac55dd701bf4; source/static examples retain their stated scope. They are not new runtime verification or required consultant setup steps.
9. Glossary & troubleshooting
Diagnose the boundary that actually failed
Separate syntax/schema, typed expression/binding, missing external target, permission denial, capability outage, stale revision and uncertain publication. Each needs a different repair. A fake empty result, a repeated request or a new administrator identity is not a universal recovery mechanism.
Keep the actual draft/publication coordinate and safe error identifier. Preserve user edits and the original operation intent. Source checks can explain a branch; actual executed UI/API behavior and required evidence must be reported separately. The cases below provide a concrete first diagnostic path rather than treating every failure as a reason to retry.
Example UIAI-CH09-01 — Repair a value destination and type mismatch
Scenario and inputs. The leave form contains a Date field whose destination was copied from a Text-only example. Nadia has the owned draft and a safe synthetic value; an employee's confidential data is unnecessary to reproduce the authoring mismatch.
Procedure. Select the field and inspect its actual Store value in target and declared destination type. Use the native picker/completion to select the matching Date declaration, such as ri:startDate, rather than relying on a similar label. Inspect expression mode and scope separately from the bind path. Validate the repaired whole document, save with its current revision and reload before judging persistence.
Expected result. The typed control and destination agree, and the intended value survives the supported draft lifecycle. A display expression is not an input destination, and local scratch state is not a saved database row. Completion suggestions derive from actual declarations, not arbitrary identifier strings.
Failure and recovery. If a referenced record/schema is unavailable, resolve its actual owner and capability instead of inventing fields or converting everything to Text. Unknown namespace or result-type errors stay explicit until corrected. Do not use a privileged sample or an unadmitted source to make the expression panel show a plausible answer.
Sources. Binding grammar and catalog, typed properties, expression evaluator boundary.
Example UIAI-CH09-02 — Distinguish stale, denied and unknown publication states
Scenario and inputs. Nadia clicked Publish for an actual saved leave-form revision. In three separate fixtures, another edit changed that revision, her publication permission was revoked, or the client lost the accepted response. These are different outcomes even if the user only sees that publication did not finish normally.
Procedure. Read the actual safe error/state and current draft/publication coordinates. For a stale revision, preserve edits and review the new saved candidate. For denied access, stop protected requests and use the neutral unavailable state. For an unknown reply, preserve the original idempotency key and impact receipt and use native attempt reconciliation before considering another publication.
Expected result. The repair matches the failed boundary. A stale draft is not overwritten, a denied control is not left as a visible Retry action, and an uncertain operation is not silently classified as failed. Only an actual accepted published version establishes what release exists.
Failure and recovery. If the original outcome cannot be resolved, retain uncertainty and request the accountable service owner's action. Do not force a new key, bypass impact review, reset another author's work or turn unavailable evidence into a success claim. A screenshot or source check alone cannot resolve an unknown server effect.
Sources. Conditional save, publication/receipt routes, publication intent rules.
Glossary
| Term | Meaning |
|---|---|
| Interface | A screen your workspace presents — a Form, App Shell, or Dashboard. |
| Draft / Published version | You edit a draft; Publish creates a version users see. |
| Node / component | One item in the interface tree (a control or container). |
| Category | A node’s kind: container, input, display, action, or tracking. |
| Binding | Connecting a value to ri: (input), locals: (local), or data. (data model). |
| Expression | A computed value in a declared position, authored with ƒx; syntax-version1 uses =, with older wrapped ${…} compatibility. |
| Store value in / Store selection in | Where an input’s value is saved (its bind). |
| Data source | Where a data/tracking control gets its data (process / task / data model / API). |
| Outline | The structural tree of the interface (left of the canvas). |
| ISL | The screen-language JSON shown in the Code tab. |
Troubleshooting
A control I added isn’t visible on the canvas. If you inserted it while a data grid (Data grid / Table / Editable grid / Tree / Pivot) was selected, note those show their own data and don’t display arbitrary child controls — add the control with nothing (or a layout container) selected so it lands as a sibling.
The properties panel is empty. Nothing is selected, or you have a multi-selection with no shared properties. Select a single component, or select components of the same type.
My “Visible when” component never shows. Check the condition in the Visibility group and test it in the Preview view. A condition that’s always false hides the component.
The interface won’t render / the Code tab looks broken.
The JSON is likely invalid (a stray comma, an unclosed brace, or a non-unique id). Run
Validate; fix the reported issue. If you deleted everything in the Code tab, paste a valid
document back.
A tracking control shows sample data, not my data. Representative samples are expected on the design canvas and Interactive Preview until you bind the control. Use Bind value and the supported governed source for the scalar, object or collection it needs. Published Live does not invent sample business state; inspect the current binding, access and source state.
Changes I made aren’t showing in the running app. The designer auto-saves drafts; users see published versions. Publish to roll out changes, and make sure you’re looking at the right workspace/version.
A dropdown’s options are empty. For a Select, add options in the Value group (fixed list) or bind them to a data source. For data controls, set the Data source.
Back to the manual index.