Skip to main content

Asset Notification Operations

Summary​

This page describes how asset events reach users through the notification-service. The notification-service is the confirmed consumer of the six Asset* events, mapping each to a corresponding Asset.* template. Recipient resolution follows a labor → user → AssetAdmin role chain, and delivery uses In-App and Email channels. Email requires an enriched recipient email that is null at emit time. Consumer-side duplicate handling is keyed on event identity. Broker delivery itself is not confirmed here, and no template content is reproduced.

Audience​

  • Support and QA engineers investigating missing or duplicate notifications.
  • DevOps engineers operating the messaging-to-notification path.
  • Solution architects assessing notification coupling.

Reference Content​

Event-to-template mapping​

The six Asset* events (AssetRequested, AssetAssigned, AssetReturned, AssetRejected, AssetLostOrDamaged, AssetRetired) map to six Asset.* templates on the notification-service. Template content is intentionally not included in this documentation.

Recipient resolution​

Recipient resolution follows this chain:

  1. Labor reference.
  2. User.
  3. AssetAdmin role (fallback).

Channels and enrichment​

ChannelRequirement
In-AppDelivered from the consumed event
EmailRequires an enriched RecipientEmail, which is null at emit time

Because the recipient email is null when the asset-service emits the event, email delivery depends on downstream enrichment.

Duplicate handling​

The consumer applies duplicate handling keyed on event identity, so re-delivered events are not processed twice on the notification side.

Boundaries (Requires confirmation)​

  • Broker delivery of events to the consumer is not confirmed here.
  • Ownership of templates and of the email-enrichment step is Requires confirmation.

Source References​

  • microservices/src/asset-service/Messaging/OutboxRelayHostedService.cs
  • microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
  • microservices/scripts/smoke-asset.ps1

See Also​

Keywords​

asset notifications, notification-service, event consumer, recipient resolution, email enrichment

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly