Service Layer medium complexity backend
1
Dependencies
3
Dependents
1
Entities
0
Integrations

Description

Backend service providing CRUD operations for notification_scenario_templates, enforcing per-org isolation and validating scenario definitions before persistence. Exposes the active scenario registry to the event evaluator for runtime lookups.

Feature: Notification Scenarios

scenario-configuration-service

Sources & reasoning

Required by blueprint. Manages template lifecycle and enforces per-org isolation described in implementation notes to prevent cross-tenant leakage of scenario configuration.

No source references — this artifact was included based on reasoning alone (see above).

Responsibilities

  • Create, read, update, and delete notification scenario templates per organization
  • Enforce tenant isolation so templates from one org are never visible to another
  • Validate trigger conditions, target role filters, and channel configurations on write
  • Provide active template lookup filtered by event type for the evaluator at runtime

Interfaces

getScenarios(orgId)
getActiveScenarios(orgId, eventType)
createScenario(orgId, config)
updateScenario(id, config)
deleteScenario(id)
toggleScenario(id, enabled)

Relationships

Dependencies (1)

Components this component depends on

Dependents (3)

Components that depend on this component

Related Data Entities (1)

Data entities managed by this component