Asset Notifications

Reference Content

Trigger	Producer and timing	Coverage boundary
Request submitted	Asset Service after request creation	Resolver recognizes AssetRequested.
Assignment completed	Asset Service after issue/workflow approval	Resolver recognizes AssetAssigned.
Return completed	Asset Service after return	Resolver recognizes AssetReturned.
Request rejected	Asset Service after rejection	Resolver recognizes AssetRejected.
Damage or loss marked	Asset Service after either action	Resolver recognizes shared AssetLostOrDamaged.
Retirement	Asset Service after retirement	Resolver recognizes AssetRetired.

The aggregate creates a transactional outbox message in the same save as lifecycle state. A hosted relay publishes pending messages and retains retry state. Notification Service resolves recognized lifecycle signals into notification intent. Channel delivery, template text, final recipient enrichment, and provider retry are owned outside Asset Management; no delivery guarantee is claimed.

No source-backed signals exist for return-due reminders, overdue returns, transfer, maintenance, repair, warranty expiry, theft, recovery, disposal, document upload, or availability. Recipient policy and escalation require confirmation.

Related Articles

• Integrations
• Lifecycle

See Also

• Known limitations
• Business rules

Keywords

• Lifecycle notifications
• Asset events

Revision Information

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

Source References

• microservices/src/asset-service/Infrastructure/AssetDbContext.cs
• microservices/src/asset-service/Messaging/OutboxRelayHostedService.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs