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.
Current model-key correction — 8 November 2026. The preserved examples below contain historical camelCase record-type/field keys. Do not copy those keys into the current editor or API: use record type leave_request and the lowercase field keys in the current model worksheet, including request_id, employee_id, manager_id, start_date, end_date, requested_days and decision_comment. Form, rule and case input names are separate declarations; map them explicitly rather than mechanically renaming every input. The preserved body remains historical source material, not a current executable model payload.
Current product update — 10 November 2026. App Chat is an implemented optional App Shell setting with approved source/action bindings, separate from the account and notification placement controls described in the preserved guide below. Configure it in the current App Shell and App Chat lesson. This notice does not claim the historical tutorial's app was published or runtime-verified with chat.
Build the Leave requests form and App Shell
This tutorial assembles a reader-created application using current Form, App Shell, rule and task contracts. It does not install a built-in HR product. The shared story uses people-ops, Mohammad(employee), Sara(manager) and Nadia(builder). Resolve their actual accounts/grants through the identity lab. Use identity milestones1–4 first, then prepare the model/rules through leave data and rules. Build this tutorial through milestone7 before continuing vacation workflow and human work milestones1–4; the manager task does not need to exist during initial form/shell authoring.
The teaching business key is leave-2026-014, dates2026-12-14 through2026-12-18, requestedDays5 and initial statusPENDING. A business key, database record identity, screen key, publication version, draft revision, task ID and actor ID are different coordinates. Keep a worksheet of actual returned values. Choose a fresh owned fixture: if an earlier tutorial already created014, inspect/edit that admitted record or choose a new unique teaching key. Do not submit the same create twice or delete another person's fixture to reset the story.
These are source-reviewed instructions. Product/browser/provider/runtime execution and new recording evidence are NOT_RUN for this documentation. Existing source/data/runtime/provider/CI/human holds remain. Preview can run admitted reads/actions; it is not automatically an isolated sandbox.
flowchart LR
Model[Published model and APPLIED destination] --> Rules[Actual admitted record/rule actions]
Rules --> Form[Generated or explicitly mapped Form]
Form --> Release[Reviewed published interface]
Release --> Shell[App Shell pages and navigation]
Task[Actual manager task and pinned task form] --> Viewer[Native TaskViewer]
Viewer --> Shell
Staged reading order
| Stage | Work and handoff |
|---|---|
| Foundation | Identity milestones1–4, then data/rules. Retain actual IDs and published rule/model coordinates. |
| Interface authoring | This tutorial milestones1–7: employee form, shell and separately published manager decision form. |
| Workflow authoring | Workflow milestones1–4: capture the manager form/actions, publish and inspect the actual release. |
| Start wiring and admission | Return here for milestones8–9, then identity milestone6 for reviewed application contributions/grants. |
| Ordinary work | Workflow milestones5–8, then this tutorial milestone10 and identity milestone7 for ordinary-user checks. |
Each return uses the preceding stage's actual outputs. The instructions do not require a complete workflow or complete application grant before the artifacts they depend on exist.
Milestone 1 — Prepare real coordinates and the intended actor boundary
Inputs. Use the actual people-ops workspace, admitted builder session, model/type/destination and rule coordinates from the prerequisite tutorials. Prepare normal Mohammad/Sara sessions only with their authorized permissions. The model's employeeId and managerId are business data, not access tokens.
Procedure. Record actual workspace ID/key, model ID, leaveRequest type, APPLIED publication, returned record action/rule keys and versions, and the intended owning business function. Confirm which actor can create/read/act on the teaching record. Keep user-facing labels separate from server-issued IDs. Decide whether014 is a fresh create or an existing admitted record before building its submit path.
Expected result. The application has explicit dependencies and a qualified actor boundary. Giving an input a hidden/default employee ID does not establish row ownership; the actual service/domain policy must enforce the intended restriction before the form is offered to an employee.
Failure and recovery. Resolve missing grants, unavailable sources and unqualified row restrictions through their owner. Continue an operator-only synthetic lesson if that is the admitted boundary, and say so. Do not borrow root, inject an actor header or advertise ordinary-user isolation that the fixture has not established.
Sources. Authoring command and ownership, native binding catalog, authorization visibility policy.
Milestone 2 — Create the Form and declare the input contract
Inputs. Nadia owns a permitted business-function placement and knows the actual required model/rule fields. The minimal ISL leave form illustrates dates/reason; a complete create needs every required record field, not just those three controls.
Procedure. Start New interface, choose Form, complete Placement/Details/Review and retain the returned draft ID/key/revision. Prefer the native data/record form generation flow for the current model when that produces the intended contract; otherwise declare and map every required input explicitly. Use a structural Form root with meaningful sections. Inspect Code to understand which values are inputs, local state and record members.
Expected result. A draft contains actual typed destinations for its intended operation. Creating a screen draft does not create a leave record or a running case. Business-function ownership is handled by the native command/context, not by pasting an obsolete root field into closed ISL.
Failure and recovery. Resolve a key collision through the supported wizard rather than force-creating a duplicate. A Form with a Stack root fails its Form-specific schema requirement; use the structural Form root. Preserve conflicting draft edits and their actual revision.
Sources. Wizard kinds and steps, current complete-document schema, create/save routes.
Milestone 3 — Configure usable typed fields and validation
Inputs. The draft exposes Date startDate/endDate, Integer requestedDays, stable requestId, required employee identity and the actual admitted status contract. Use the demonstration dates/five days explicitly; calendar/holiday arithmetic is a separate authored policy, not a guaranteed difference between two dates.
Procedure. Choose typed Date/Integer/Text or actual record-bound controls. Set labels, help, declared destinations and required validation through the native property editor. Keep machine values such as PENDING separate from translated display text. Exercise a missing required value and an invalid date order using supported validation before the valid fixture. When a reason field is included, map it only if the actual model has that field; otherwise label it as UI-only rather than silently discarding it.
Expected result. The form clearly explains what the employee enters and how errors are repaired, while the intended data contract remains explicit. A disabled business-state choice may have a reason; a permission-denied action remains absent. Capturing a field value alone is not persistence.
Failure and recovery. Fix unknown destinations or wrong value types through declarations/native builders. Do not coerce every value to Text, store translated labels as keys, or use visibility to replace authorization. Keep user edits when correcting a field rather than clearing the whole form after one error.
Sources. Property types/modes, typed bind targets, screen expression boundary.
Milestone 4 — Wire the admitted create or update operation
Inputs. Use the actual generated/native record action or published rule from the data tutorial, its input signature and the intended record identity. A create for a fresh014 differs from editing an already created014; a case-start step remains separate unless a deliberately authored trigger defines it.
Procedure. In Automations, choose the native supported action and map its actual declared fields. For a generated rule call, retain the actual ruleKey/ruleVersion, stable actionId, explicit args and local result destination. Review a mapping worksheet: requestId is the business key; employee/manager IDs come from the admitted context; dates use typed values; requestedDays is5 for this fixture; status starts PENDING. Preserve every other required field from the actual model. Inspect the accepted native result before offering a case-start handoff.
Expected result. One deliberate submission produces the actual admitted result, or a real refusal. A local result value or success toast is not a generic receipt, and record creation does not automatically start a lifecycle unless that integration was authored separately.
Failure and recovery. A duplicate key, incompatible argument or denied record effect needs its native supported recovery. Reconcile uncertain outcomes before repeating a consequential create. Never fabricate a record/task ID from the business key or convert the workflow into client-side arbitrary code.
Sources. Native event-action shapes, automation catalog, current authoring behavior.
Milestone 5 — Review and publish the form
Inputs. The intended fields/actions are saved in an actual draft revision. Nadia has native publication permission and the exact dependency coordinates. The tested fixture and current publication impact must refer to that saved content.
Procedure. Save pending edits conditionally, re-read the resulting revision, validate and inspect the native impact review. Publish through the normal UI and retain its original intent, applicable receipt and returned publication version. Inspect the actual supported published target with the intended actor; Preview and published Open Live have different purposes.
Expected result. A definite published interface exists. Its native result and actual runtime behavior are distinct evidence; a schema-valid document does not establish an employee flow by itself. The editable draft can change later without rewriting that version.
Failure and recovery. A stale save/publication requires re-reading and reviewing the actual changed candidate. Preserve the original publication identity after an unknown reply and reconcile it instead of minting a second operation. Do not bypass impact review or infer acceptance solely because a button stopped spinning.
Sources. Conditional save, publication and impact, intent body.
Milestone 6 — Assemble the shell and its page semantics
Inputs. The actual form screenKey exists and is published. Nadia creates an App Shell in the admitted placement. The shell's page binding follows the latest published interface for its screenKey; the deprecated binding.version is ignored, so do not describe it as an exact version pin.
Procedure. Follow Shell template/Options/Details/Review as shown by the chosen entry point. Add an overview canvas page and a request bind page using the actual form key. Give pages distinct stable IDs/urlStubs. Configure header/navigation/account/notification placement through supported shell options. Add a ContentOutlet only where target-area routing is intended, respecting main/secondary region and opaque-child rules. Compare the complete schema-qualified shell example.
Expected result. Persistent chrome and page intent are explicit. The bound page responds to the target's actual latest published release; it does not use an invented stored-version pin. The separately planned floating application chat is not an implemented shell setting in this tutorial.
Failure and recovery. Resolve a missing/inaccessible target, invalid page stub or unsupported region value through its owner. Do not add guessed raw properties, expose denied pages, or put arbitrary child content in a runtime-owned outlet to simulate a successful target render.
Sources. App Shell schema, latest-bound-page validation, published shell runtime.
Milestone 7 — Build and publish the separate manager decision form
Inputs. Nadia has the admitted authoring placement and creates a second Form, titled Manager leave decision with a unique key such as leave-manager-decision. This is separate from the employee request-entry form. The intended workflow outputs are Boolean approved and Text decisionComment; the original dates/request reference are mapped task context, not trusted caller identity.
Procedure. Declare the two output inputs. Add a Checkbox bound to ri:approved and a TextArea bound to ri:decisionComment, then two authored submit actions. In the native action editor, make Approve and Decline submit to the calling process, and retain their distinct actual generated node IDs from Code. The sample below uses approve and decline to make the two identities readable; the visual inspector does not let an author overwrite the generated Component ID. Set Business outcome to Approved/Declined and Reason from form field to decisionComment. Their onClick actions set the same approved output to the fixed Boolean true/false, so the selected submit action and the saved route value agree. Use FULL submission: OUTCOME_ONLY does not support this reason-binding contract. The Checkbox makes the Boolean field explicit; the selected action writes the final value, and the server validates the actual captured action rather than trusting a freely supplied Boolean.
The following complete current-schema ISL illustrates that authored contract. Its document version1 is a teaching value; after native save/validation/impact review/publication, retain the actual screenKey and returned publication version.
{
"id":"leave-manager-decision",
"version":1,
"screenKind":"form",
"title":"Manager leave decision",
"inputs":{
"approved":{"type":"Boolean"},
"decisionComment":{"type":"Text"}
},
"body":[{
"id":"manager-decision-form",
"type":"Form",
"children":[
{"id":"approved-answer","type":"Checkbox","label":"Approved","bind":"ri:approved"},
{"id":"decision-comment","type":"TextArea","label":"Decision comment","bind":"ri:decisionComment"},
{"id":"approve","type":"Button","label":"Approve","action":"submit","taskSubmitPolicy":"FULL","taskDecision":"Approved","taskCommentBind":"ri:decisionComment","onClick":{"do":[{"action":"setValue","target":"ri:approved","value":true}]}},
{"id":"decline","type":"Button","label":"Decline","action":"submit","taskSubmitPolicy":"FULL","taskDecision":"Declined","taskCommentBind":"ri:decisionComment","onClick":{"do":[{"action":"setValue","target":"ri:approved","value":false}]}}
]
}]
}
Continue with workflow milestones1–4. In the human task's Bind a task form picker, select this published interface and retain its exact version. That native picker sets ISL_SCREEN; map the form outputs approved and decisionComment to the declared case fields. Record the actual IDs of the Approve/Decline nodes, output allowlist and publication in the worksheet. Do not replace the output allowlist with arbitrary completion JSON.
Expected result. The workflow can capture a genuine published manager form and its actual submit actions. The native task host reads the task's pinned key/version and projects a PinnedTaskForm. The older /api/forms catalog uses CreateFormDefinitionCommand/FormSchema and returns FormDefinitionVersion; it is a distinct legacy-form path, not an automatic conversion of an ISL employee form. This tutorial deliberately uses the current published-interface picker and ISL_SCREEN authority.
Failure and recovery. Publish the decision form before selecting it: a draft-only candidate cannot be bound. If a different interface is selected, review fresh mappings; the native picker drops incompatible old mappings. A missing pin, mismatched version or foreign provenance remains unresolved rather than falling back to legacy authority. Reconcile uncertain publication before creating another version. Static schema acceptance here does not prove the task completed in a browser.
Sources. Native picker and exact version capture, outcome/reason/FULL properties, actual submit action ID and intent, server action and fixed-route extraction, pinned authority/output classification, runtime projection, distinct legacy create command, legacy version.
Milestone 8 — Return from workflow publication and wire its start action
Inputs. Workflow milestones1–4 have produced the actual saved/published lifecycle key/version and a qualified Review task/form mapping. Keep those real coordinates and the actual initial case-input signature. Do this before reviewing application-user contributions and before Mohammad's ordinary-user start.
Procedure. Return to the employee Form's Automations, choose Start a lifecycle, select the actual published leave lifecycle/version and map every required input. Use the admitted values for dates, requestedDays5, business reference and selected participants; retain server-issued actor/directory identities separately. Store the returned result in a declared local result, if needed. Review the supported idempotency/correlation fields for this native action and preserve one unchanged intent after uncertain delivery. Save, validate, review impact and publish the revised employee Form. Because the shell's bind page follows the latest published screenKey, record this new target publication explicitly in the application worksheet.
Expected result. The employee form now has a real published lifecycle-start action. Earlier record creation remains a separate effect unless the authored sequence intentionally includes both. The release/resource set reviewed for application access includes this exact lifecycle and relevant form/task dependencies. Configure the task-host composition in milestone9, then continue identity milestone6 for actual application contributions/grants. Execute workflow milestones5–8 for ordinary-user start and manager response, followed by this tutorial's milestone10 and identity milestone7 checks.
Failure and recovery. If the lifecycle is unpublished or its inputs changed, repair the actual selection/mappings before release; do not insert a guessed version1. Reconcile an uncertain start using the native original intent and returned coordinates before another click. A returned process ID is not the leave record key, and a record-save toast alone does not establish case start.
Sources. Native Start a lifecycle action contract, action catalog label, closed start action schema, publication boundary.
Milestone 9 — Add manager work through the native task surface
Inputs. Configure this composition after the workflow release exists but before application contribution review. Use the actual supported current-actor task source metadata and an admitted host; no customer case/task instance is required for authoring. A real task ID arrives later from an authorized task source after workflow milestone5 creates a task. It is never constructed from leave-2026-014 or the record's database ID.
Procedure. Connect a supported current-actor task list and place one TaskViewer in the admitted composition. Declare a Text taskId input and use the native row-open/selection automation to map the source's actual task identity into it; configure the viewer's taskId expression through its supported editor. The host supports reactive declared-input synchronization, so a future selected task can supply this ID without hardcoding a nonexistent one. Verify that the chosen source actually offers that identity/action mapping; a generic business record source does not. Choose perform/readOnly deliberately, review summary/comments/attachments options, then save/validate/publish this host before application scope review. Let the authenticated host select the pinned form and current participants. Execute its live load/complete/receipt checks only after workflow milestones5–8 produce an actual eligible task.
Expected result. Task discovery, human response and case progression use their native contracts. An app author cannot override workspace, identity, form version or output allowlist through TaskViewer properties. A completed event carries safe task coordinates, not permission for an unrelated business mutation.
Failure and recovery. Preserve a revoked/unavailable task as unavailable; do not mount a guessed form or create a second interactive viewer to avoid host constraints. Claim, stale edit, shared-step quorum and uncertain completion require their actual native action/receipt recovery. A model's recommendation is never substituted for Sara's task response.
Sources. TaskViewer authoring contract, reactive declared-input synchronization, authenticated native host, guarded navigation/work.
Milestone 10 — Inspect the application as each intended user
Inputs. Use the actual published shell/form and separately admitted Mohammad/Sara sessions. Keep fixture/build/source coordinates and expected permissions. A builder/admin success cannot establish employee or manager behavior.
Procedure. Check navigation, field labels/order, responsive widths, direction, validation and ordinary-user data/task visibility. Confirm denied controls and their unauthorized requests are absent. Exercise native dirty-work navigation decisions rather than forcing route changes. Follow the workflow tutorial's actual request/response outcome and compare its canonical receipt with the record/case state before reporting business success.
Expected result. Each observed result belongs to the exact actor/build/fixture and native operation. The documentation's source checks remain separate from actual UI/API/DB evidence. The whole application is not called verified merely because the shell loaded or every JSON fence parsed.
Failure and recovery. Preserve failed workflow assertions and user edits. Resolve the specific model/rule/form/task/authorization boundary instead of widening all roles or replacing real data with samples. If runtime execution or required recording/delivery is unavailable, report that evidence NOT_RUN and retain accountable next work.
Sources. Current visibility rule, published task/form leave guard, actual control contract.
Continue and maintain
Use the node reference for exact current property/default/event keys, screen language for document/action boundaries and workspace deployment for release movement. When the model, rule input, page binding or task form changes, revisit the affected handoff rather than assuming a new latest release is interchangeable everywhere.