User Interface medium complexity mobilefrontend
0
Dependencies
0
Dependents
1
Entities
0
Integrations

Description

Full-screen form allowing a coordinator to submit an activity on behalf of a selected peer mentor. Presents the same activity fields as the standard logging screen but with a clear visual indicator that the submission is a proxy entry. Validates all required fields before delegating submission to the service layer.

Feature: Coordinator Proxy Reporting

proxy-registration-screen

Sources & reasoning

Lines 83-84 define proxy reporting as a shared coordinator need for NHF, HLF, and Barnekreftforeningen, explicitly motivated by peer mentors who will not or cannot use the app. Line 151 places the requirement at SHOULD HAVE in Phase 2 (Fase 2), which maps to v1.0 by ordinal position. The blueprint also assigns [v1.0] to this feature, confirming the target release.

  • docs/source/likeperson.md · line 83-84
    Koordinatorer må ha mulighet til å registrere aktivitet på vegne av sine likepersoner, enten enkeltvis eller samlet for faste aktiviteter (f.eks. ukentlig trening med mange deltakere).
  • docs/source/likeperson.md · line 151
    | Bulkregistrering / proxy-rapportering | ✓ | ✓ | - | ✓ | ✓ | SHOULD HAVE | 2 |

Responsibilities

  • Render activity input form prefilled with proxy context (selected peer mentor name and ID)
  • Display prominent proxy-mode banner so the coordinator cannot mistake the submission context
  • Validate form inputs and surface field-level error messages
  • Dispatch proxy submission to ProxyActivityService and handle success or error responses
  • Navigate back to the peer mentor roster or confirmation screen after successful submission

Interfaces

render(mentorId: string): void
onSubmit(activityData: ActivityFormData): void
onCancel(): void

Related Data Entities (1)

Data entities managed by this component