Files
portal/runs/permits-plan-2026-09-30/site/questions/front_desk/logged-objection.yaml
T
Bendik Aagaard LynghaugandClaude Fable 5.1 3dabcf7c58 build: one page holds every need that answers a record; runs: the kommune planned again by Opus
Two needs about the same record wrote the same page, and the last won.
The record's page now holds one form per answering need, under
words["forms"][need].

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
2026-09-30 08:58:55 +02:00

44 lines
1.2 KiB
YAML

followup: false
name: Logged objection?
description: ''
responsible:
name: Solveig Hauge
contact: byggesak@vestmark.example
alternatives:
- name: To put the objection on the right case straight away, instead of stapling it to a folder
description: For The front desk, when an objection comes in on paper or over the counter.
action: /front_desk/logged-objection-sent
consequence:
- Send
record_as: paper_objections
features:
- name: What happens next
description: It is received, then registered on the case, then answered by the applicant, and ends addressed in the decision.
icon: lucide:route
- name: Who reads it
description: Case officers. Questions go to Solveig Hauge at byggesak@vestmark.example.
icon: lucide:users
- name: Details
requirements:
- name: application_reference
label: Application reference
type: text
- name: name
label: Name
type: text
value: '{user.name}'
- name: objection
label: Objection
type: textarea
- name: received_on
label: Received on
type: date
- name: your_property
label: Your property
type: text
optional: true
- name: phone
label: Phone
type: tel
optional: true