137 docs tagged with "notification"

Notification template, failure, retry and audit administration.

Operational notification metrics and dashboard views.

Employee notification inbox and read-state journey.

Verified Leave notification intent resolution and delivery boundary.

Source-backed business documentation for HR Suit notifications.

Source-backed detail of the native message, attempt, retry, failed-queue, idempotency, audit and statistics endpoints of the Notification Service.

Source-backed administrator journey — the Notification Center operations console, template administration and the retry action.

Source-backed authentication posture of the Notification API, covering the anonymous native surface and the authorized compatibility controllers.

Source-backed authorization posture of the Notification API, including ownership checks on the compatibility surface and their absence on the native surface.

Source-backed API documentation for the HR Suit Notification native, administrative, template, test, operational and compatibility HTTP surfaces.

Source-backed error handling on the Notification API, including the absence of an exception handler and problem-details responses.

Verified Notification API limitations grouped by authentication, authorization, validation, gateway, compatibility, delivery, testing and versioning.

Source-backed Minimal API organization, route groups, operational endpoints and gateway participation of the Notification HTTP surface.

Source-backed request flow through the Notification API from middleware to response, including the dispatch and publish paths.

Source-backed catalog of the response patterns the Notification API returns, including entity serialization, anonymous projections and status codes.

Verified traceability from every Notification API documentation topic to the backend and frontend source files that evidence it.

Source-backed handling of tenant identity across the Notification HTTP surface, endpoint by endpoint.

Source-backed API test coverage for Notification — the smoke script and manual request collection — separated from recommended coverage.

Source-backed catalog of route, request, domain and persistence validation on the Notification API, and the validation that is verifiably absent.

Verified absence of HTTP API versioning on the Notification surface, and the two internal version concepts that do exist.

Verified application-layer services, abstractions, request flow and dependency graph of the Notification Service.

Verified module architecture, runtime composition and technical maturity of the Notification Service.

Source-backed persistence of the NotificationAuditLog table — the append-only stage trail, its 13 stages and its unbounded growth.

Verified authentication and authorization posture of the Notification Service, including the absence of in-service enforcement.

Verified hosted event consumer, broker binding and per-message execution model of the Notification Service.

Source-backed broker topology for Notification — exchange, queue, bindings, prefetch, connection resilience and the unwired dead-letter names.

Known source-backed gaps, risks and transitional boundaries.

Business scope, value and operating model of HR Suit notifications.

Authoritative source-backed notification business-rule catalog.

Verified channel sender abstraction, registry and per-channel implementations of the Notification Service.

Business behavior and readiness of notification channels.

Verified write operations of the Notification Service and the absence of a formal command object model.

Verified gateway routing toggle, legacy monolith coexistence and portal integration surface of the Notification Service.

Privacy, access, audit and retention considerations for notifications.

Verified absence of concurrency control in Notification persistence and the specific race windows the unique indexes do and do not close.

Source-backed reference of every Notification configuration option, its section, default and operational effect.

Consolidated source-backed reference of Notification routes, operational endpoints, configuration sections, logs, diagnostics and supporting scripts.

Authoritative source-backed inventory of all 42 integration event types the Notification Service consumes, with template keys, channels and recipients.

Source-backed description of the single hosted consumer — its lifecycle, scoping, acknowledgement behavior and failure handling.

Source-backed notification tiles on the executive dashboard, the sources they read and their unavailable-state handling.

Verified absence of retention, cleanup and archival in Notification persistence, and the unbounded growth characteristics that follow.

Source-backed Notification persistence documentation covering the NotificationDb schema, entities, mappings, indexes, query patterns, transactions, migrations and seeding.

Verified Notification database limitations grouped by persistence, concurrency, tenant isolation, transactions, retry, testing, governance, retention and schema evolution.

Source-backed overview of Notification persistence: the owned database, schema, table count, index count and current maturity.

Verified traceability from every Notification database documentation topic to the backend source files that evidence it.

Source-backed tenant isolation in Notification persistence — the absent global filter in the extracted service versus the query filters in the monolith.

Source-backed database test coverage for Notification — smoke-script persistence assertions only, with no mapping, migration or repository tests.

Verified inventory of every persistence context that maps Notification data, its DbSets, filtering and save behavior.

Verified gap between configured dead-letter names and the queue declaration in Notification — configured but not wired.

Recipient, preference, template and channel delivery decisions.

Verified per-message delivery pipeline of the Notification Service, including attempt recording and failure handling.

Source-backed persistence of the NotificationDeliveryAttempts table — the append-only per-attempt record and its truncation behavior.

Source-backed seeding behavior for Notification — the idempotent global default-template seeder, its coverage and its configuration toggle.

Source-backed diagnostic surfaces for Notification — audit trail, attempts, idempotency lookup, statistics and the test hooks.

Verified absence of a domain-event model in the Notification Service and the direct-mutation approach used instead.

Source-backed inventory of every verified Notification request and response data-transfer type across the native and compatibility surfaces.

Authoritative source-backed catalog of every verified Notification HTTP endpoint across the native service, the monolith compatibility controllers and the gateway.

Source-backed fluent mapping configuration for Notification entities — table names, lengths, required flags, column types and what is deliberately not configured.

Verified absence of declared relationships in the Notification model and the logical associations that identifier columns imply instead.

Source-backed event-driven architecture of Notification — publisher and consumer responsibilities, broker participation and delivery flow.

Source-backed compatibility posture of the Notification event surface — contract coupling models, orphan templates and the legacy path that bypasses events entirely.

Source-backed correlation identifier flow through Notification event processing, including activity propagation and the effective-correlation gap.

Source-backed structure of the NotificationEventEnvelope, how it is built from AMQP properties and headers, and which fields are unused.

Source-backed description of the single resolver that maps consumed events to notification intents, and the dispatcher that executes them.

Source-backed duplicate detection in Notification — the processed-event ledger, the staleness guard and the verified failure windows.

Verified Notification event limitations grouped by publishing, consumption, broker, retry, dead-letter, ordering, idempotency, versioning and testing.

Verified traceability from every Notification event documentation topic to the backend source files that evidence it.

Source-backed event test coverage for Notification — direct and broker smoke modes and the forced-failure hook — separated from recommended coverage.

Source-backed event schema versioning in Notification — the version field is carried end to end but never branched on.

Source-backed Notification event documentation covering consumed integration events, the message envelope, broker topology, correlation, idempotency, retry and versioning.

Source-backed overview of the Notification event surface — consumption-only participation, counts and current maturity.

Source-backed reference for the exchange, queue, routing keys and binding set declared by the Notification Service.

Source-backed answers to common Notification questions covering delivery, channels, templates, preferences, retry and operations.

Source-backed gateway route configuration, feature toggle, shadow route and legacy monolith compatibility surface for Notification.

Source-backed detail of the health-check endpoint registered by the Notification Service and the checks it does and does not include.

Source-backed health surface for Notification — the health endpoint with no registered checks, and what it does and does not prove.

Message, attempt, audit and read-state history.

Verified absence of lifecycle notification HTTP calls and the internal exit-approval notification boundary.

Source-backed persistence of the ProcessedIntegrationEvents table — the idempotency ledger, its unique constraint and its check-then-write race window.

Source-backed behavior of the employee notification inbox screen and the header bell widget — filters, actions, polling and categorisation.

Source-backed detail of the native in-app inbox and read-state endpoints of the Notification Service.

Authoritative source-backed inventory of all 14 Notification indexes, the 4 unique constraints and the constraint types that are absent.

Source-backed inventory of the integration event contract types Notification deserializes — shared contracts and service-local payload records.

Business events, consuming modules and channel integration boundaries.

Verified dependency direction between the API, application, channel, domain, infrastructure and messaging layers of the Notification Service.

End-to-end business lifecycle for event-driven notifications.

Verified logging, tracing, correlation, audit and health surfaces of the Notification Service, separated from recommended improvements.

Source-backed catalog of every log statement the Notification Service emits, its level and its operational meaning.

Verified absence of ordering guarantees in Notification event consumption and the factors that break sequential processing.

Source-backed persistence of the NotificationMessages table — columns, indexes, lifecycle and the absence of referential constraints.

Source-backed migration inventory for Notification — one migration, one snapshot, a design-time factory and automatic startup migration.

Source-backed monitoring surface for Notification — what can be observed today, and the verified absence of metrics and alerting.

Source-backed operational shape of the Notification Service — startup sequence, dependencies, lifecycle and failure posture.

Source-backed operational procedures for Notification — verifying consumption, re-driving failures, changing templates and channels, and recovering from a broker outage.

Capabilities and implementation status of HR Suit notifications.

Verified persistence model of the Notification Service and the absence of a repository abstraction.

Source-backed persistence architecture of Notification, covering ownership boundaries, access path and the absence of a repository layer.

Source-backed persistence of the NotificationPreferences table — the opt-out model, wildcard rows and the absence of any write path.

Verified absence of any notification preferences user interface, and the enforcement-only preference model that exists behind it.

Verified end-to-end event processing pipeline of the Notification Service, from idempotency to audited completion.

Verified folder layout and responsibilities of the Notification Service source project.

Verified absence of published business events in the Notification Service and the single test-only publish path that exists instead.

Source-backed description of the shared event-bus publisher available to Notification and the single test-only path that uses it.

Verified read operations of the Notification Service and the absence of a formal query object model.

Source-backed catalog of every Notification persistence query — tracking behavior, predicates, ordering and result limits.

Source-backed persistence of the NotificationRecipients table — the upsert-merge directory keyed by tenant, type and external reference.

Source-backed distinction between in-process delivery retry and broker-level redelivery in Notification, and the unbounded requeue behavior.

Source-backed persistence of retry state in Notification — attempt counters, attempt rows and the absence of a retry queue or dead-letter table.

Verified bounded exponential-backoff retry schedule and its boundaries in the Notification Service.

Verified startup, dependency-injection registrations and hosted services of the Notification Service.

Authoritative source-backed schema reference for Notification — every verified table, its columns, constraints and indexes, each appearing exactly once.

Verified anatomy of the Notification Service dispatcher, its collaborators and the event coverage it resolves.

Source-backed detail of the shared-kernel service-information endpoint exposed at the Notification Service root, including its response envelope.

Traceability from business documentation to notification source files.

Verified absence of a statistics table in Notification and the computed count queries that serve statistics instead.

Source-backed Notification Service architecture, processing pipeline, channels, templates, delivery, retry, security, observability and testing documentation.

Verified technical limitations of the Notification Service, grouped by architecture, delivery, retry, processing, authorization, validation, compatibility and testing.

Verified traceability from Notification technical topics to their backend and frontend source files.

Verified template model, version precedence, rendering and default seeding of the Notification Service.

Source-backed detail of the native template list, create, update and test-render endpoints of the Notification Service.

Source-backed behavior of the notification template administration screen — event selection, editing, channel toggles, preview and reset.

Source-backed persistence of the NotificationTemplates table — versioning, the global-default convention and the uniqueness constraint.

Verified tenant scoping model of the Notification Service, applied per query without a global filter.

Source-backed detail of the native dispatch and publish test hooks of the Notification Service and the forced-failure flag.

Verified test coverage of the Notification Service — a smoke script and in-service test hooks — separated from recommended coverage.

Source-backed save boundaries in Notification — the many-small-saves pattern, the absence of explicit transactions and its partial-failure consequences.

Source-backed troubleshooting for Notification covering missing notifications, delivery failures, broker connectivity, template, health, startup and configuration issues.

Verified Notification limitations grouped by UI, administration, monitoring, operations, configuration, troubleshooting, diagnostics and user experience.

Verified traceability from every Notification UI and operations documentation topic to the frontend and backend source files that evidence it.

Source-backed overview of every Notification screen, route, navigation entry and the portal each belongs to.

Source-backed Notification user interface, administrator experience, operational configuration, monitoring, troubleshooting and consolidated reference documentation.

Source-backed employee journey through notifications — discovery, reading, acting and the verified gaps in feedback.

Verified input validation and guard clauses in the Notification Service and the absence of a validation framework.

Verified absence of value converters, owned types and JSON columns in the Notification model, and the plain-string convention used instead.

Automatic and manual notification retry behavior.

Business lifecycle and governance of notification templates.

Feature-flagged recruitment workflow behavior and verified notification boundaries.