epic-11-notifications

Real-time in-app investor notifications are automated by listening to event-driven triggers like DividendDistributedEvent, WithdrawalRequest events, and ContractSignedEvent. The system uses a Notification entity, repositories, and event handlers to generate alerts for investors.

A notification center for an investor portal is structured using a Notification entity and NotificationType enum for backend persistence. The frontend integrates a bell widget and drawer with pagination, read-status updates, and ActionUrl navigation.

Unread counts are tracked and notifications are marked as read using application layer service interfaces and API endpoints. The frontend store updates read statuses and timestamps directly through these dedicated notification CRUD APIs.

The notification system supports internationalization by providing text templates with variants for both zh-CN and en-US. This ensures investor alerts for dividends, withdrawals, and contract signings are localized correctly.

Event-driven architecture automatically triggers contract signing notifications by listening to ContractSignedEvent. Event handlers process this domain event and generate a notification entry, which is then fetched and displayed via the API endpoints.

Backend event handling for investor withdrawal status updates is set up by listening to WithdrawalRequest domain events. Event handlers capture these events, apply text templates, and persist notifications to the repository for frontend retrieval.