Journey Academy · 3 / 5
Carry the job into the handoff
Declare read-only launch context so the process knows which job it concerns.
YOUR TASK
Make this happen
Add a required resource launch input keyed job with resourceType job; attach it through the document inputs list.
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.
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_form.details, 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 = "Prepared by {{ $.state.operator }}: {{ $.state.notes }}"
}
answers.cococo
journey_field "operator" {
key = "operator"
kind = "text"
label = "Your name"
required = true
}
journey_field "notes" {
key = "notes"
kind = "multiline"
label = "Handoff notes"
required = true
}
journey_form "details" {
kind = "form"
id = "details"
title = "Prepare the handoff"
fields = [journey_field.operator, journey_field.notes]
}
context.cococo
journey_input "job" {
# TODO: add key — see the task above.
kind = "resource"
# TODO: add resourceType — see the task above.
label = "Job to hand over"
# TODO: add required — see the task above.
}
Supplied supporting files
Reference: journeys · getting-startedjourneys · bindingsjourneys · formsjourneys · schema-formsjourneys · conditionsjourneys · completionjourneys · go-live