Journey Academy · 2 / 5

Collect and reuse useful answers

Capture a name and notes, then show their current values on completion.

YOUR TASK

Make this happen

3 steps

Add required operator text and multiline notes fields to a form between start and finish. Make the completion body read Prepared by {{ $.state.operator }}: {{ $.state.notes }}.
Keep the working capabilities from the previous lesson and connect the new pieces to the same solution.
Check the complete solution, then inspect any unmet requirements.

THE IDEA BEHIND IT

What this step adds

Add required operator text and multiline notes fields to a form between start and finish. Make the completion body read Prepared by {{ $.state.operator }}: {{ $.state.notes }}.

Files to work in

main.cococo, stages.cococo, answers.cococo. Other files are the working baseline. New files include named resource skeletons and TODO guidance. Complete their fields and connect them using the objectives, schema completion and reference guide.

Answers become state

Each field writes its answer under its key. Completion prose reads that state when displayed, so returning to edit an answer should update the final summary.

Plain text stays plain text

Journey body text is not an HTML injection mechanism. The runner must display user-authored markup literally. Local model checks do not simulate rendering.

Local checks validate typed virtual models, composition and the lesson requirements. They do not run queries, render the platform UI, publish versions or prove server authorisation. Complete the platform compiler and preview checks before publishing.

Files to change: main.cococo, stages.cococo, answers.cococo

What you’re building: Guide an operator through a job handoff: collect the right details, show extra instructions only when needed, and finish with a useful summary.

This step starts with the earlier solution and one new challenge. Each lesson keeps its own draft.

Read the starter files

main.cococo

journey_document "handoff" {
  id = "job-handoff"
  title = "Job handoff"
  icon = "job"
  estimatedMinutes = 3
  summary = "Prepare a clear handoff for the next operator."
  steps = [journey_info.start, journey_done.finish]
}

stages.cococo

journey_info "start" {
  kind = "info"
  id = "start"
  title = "Before you hand over"
  body = "Check the current job and prepare your handoff notes."
  checklist = ["Know which job you are handing over."]
}
journey_done "finish" {
  kind = "done"
  id = "finish"
  title = "Handoff prepared"
  body = "Your handoff is ready to share."
}

answers.cococo

journey_field "operator" {
  # TODO: add key — see the task above.
  kind = "text"
  label = "Your name"
  # TODO: add required — see the task above.
}

journey_field "notes" {
  # TODO: add key — see the task above.
  kind = "multiline"
  label = "Handoff notes"
  # TODO: add required — see the task above.
}

journey_form "details" {
  kind = "form"
  id = "details"
  # TODO: add title — see the task above.
  # TODO: add fields — see the task above.
}

Supplied supporting files

Reference: journeys · getting-started journeys · bindings journeys · forms journeys · schema-forms journeys · conditions journeys · completion journeys · go-live