Notification Scenarios

Description

Notification Scenarios defines the rule engine that determines when and to whom notifications are sent, based on domain events such as assignment creation, activity approval, certification expiry, or inactivity thresholds. The NotificationScenarioEngine evaluates configured scenarios against incoming events and triggers the appropriate delivery channels. Scenarios are persisted in NotificationScenarioRepository and configurable per organization to match specific operational workflows and the follow-up protocols each organization requires.

Sources & reasoning

Line 116 explicitly calls for "scenariobaserte push-meldinger" to address HLF's follow-up gap. Blueprint marks notification-scenarios [v1.0]. Second phase ordinal = v1.0. The scenario engine is the mechanism that makes scenario-based delivery possible.

docs/source/likeperson.md · line 116

Oppfølging av likepersoner: 40 % var ikke fornøyd med oppfølgingen i spørreundersøkelse. Scenariobaserte push-meldinger og kalendersynkronisering.

Analysis

Business Value

Manual follow-up is a documented pain point: HLF's survey found 40% of peer mentors were unsatisfied with follow-up quality. Scenario-based notifications automate the prompts that coordinators previously had to send manually, reducing workload and ensuring consistent follow-up regardless of coordinator availability. For organizations with certification requirements (HLF, Barnekreftforeningen), expiry reminder scenarios prevent lapsed certifications and the associated administrative burden of reactivating peer mentors who missed renewal deadlines.

Implementation Notes

The NotificationScenarioEngine is a backend service that subscribes to domain events (activity created, assignment dispatched, certification expiry approaching) and matches them against stored scenario rules. Each scenario specifies trigger conditions, target audience (role, organization), delivery channel (push, email, SMS), and message template. Scenarios are organization-configurable within a fixed set of trigger types. The engine enforces idempotency to prevent duplicate notifications on retry. Module toggle integration ensures scenarios for disabled modules are never triggered.