Bulk Register Screen
Component Detail
User Interface
medium complexity
mobile
0
Dependencies
0
Dependents
1
Entities
0
Integrations
Description
Mobile screen used by coordinators to register one activity for multiple peer mentors in a single submission. Provides activity template fields, a multi-select peer mentor picker, and a confirmation summary before fanning out the records.
bulk-register-screen
Sources & reasoning
Matrix row 101 places bulk at SHOULD HAVE / Fase 2 (= Core Product). §2.4 explicitly calls out "samlet for faste aktiviteter" and the 380-registrations anecdote justifies the volume-reduction motive. Depends on proxy-reporting since each bulk row is logically a proxy entry.
-
docs/source/likeperson.md · line 50-51registrere 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 13En likeperson hadde 380 enkeltregistreringer på ett år.
-
docs/source/likeperson.md · line 101Bulkregistrering / proxy-rapportering | ✓ | ✓ | - | ✓ | ✓ | SHOULD HAVE | 2
Responsibilities
- Capture activity template fields (type, date, duration) for the group session
- Present a searchable multi-select list of peer mentors with selection counters
- Validate input completeness and selected mentor count before submission
- Show a confirmation summary listing the activity and all selected mentors
- Submit the bulk payload to the Bulk Registration Service and surface per-mentor success or failure results
Interfaces
renderBulkRegisterForm(coordinatorId): void
selectPeerMentors(mentorIds): void
submitBulkRegistration(payload): BulkRegistrationResult
showResultSummary(result): void