The notification service can be described as a messenger service responsible for handling email and SMS transactions. It enables an organisation's members (Staff and Customers) to get notified of events occurring on their accounts.
Navigation:
Children Display |
---|
To Do:
Setting up
Description
The notification service can be described as a messenger service responsible for handling email, push notifications and SMS transactions. It enables members (Staff and Customers) of a tenant to get notified of events occurring on their accounts.
It uses JMS Listeners to subscribe to event topics registered the system's message broker (ActiveMQ).
Once the message has been received, it determines the template, the gateway and the builds the content of the message.
Please consider contributing!
Service Roadmap/Feature
...
- I
mplement basic SMS and Email integrationInterface with TwilioGmail integration
Incorporate notification microservice into demo-server
...
Notification Development
- Implement Increment 1: Customer Event Listener
- Implement APIs
- Re
- Implement SMS Service
- Implement SMS Gateway Configuration repository
- Implement Email Service
- Implement Email Gateway Configuration repository
...
Persistence Development
- Design Database Schema
- SMS configuration entity
- Email configuration entity
...
Frontend Development
- Create Frontend for fims-web-app
Notification service for Mobile App
- Firebase Cloud Messaging integration into Mobile App
to enable testing.Basic Message TemplatingRest APIDocumentation
Add support for FINCN Mobile
- Implement FCM push notification with a multi-tenanted approach
- Resources: Official FCM Documentation, FCM implementation in Java,
- Implement FCM push notification with a multi-tenanted approach
- Replicate SMS/Email/Push Notifications functionalities for Portfolio/Office/Group/Employee Event Listener
- OTP through Push Notifications, SMS and Email
- Message Localisation
- Disable SMS and Email for specific users by using a custom field in customer
- Tenant Reputation Management
- Notification subscription and unsubscribe feature via SMS and email
- Message Templating
- Bulk SMS/Email/Push Notification
- Customized Bulk SMS
- Generic SMS
- Customized Messaging
- Templating
- Bulk SMS/Email/Push Notification
- Assess the feasibility of third-party integration with other messaging services
- Amazon SES Multitenant Solution
- Final test plan
Objectives for ongoing Iteration
Feature/Class | To Do: Features | Status |
---|---|---|
Rest Controller and Notification Manager |
|
|
Email Service |
|
|
Email Configuration Repository and schema |
|
|
SMS and Email Service |
|
|
SMS configuration Repository and schema |
|
|
Commands for SMS and Email Config and handlers |
|
|
Rest Controller and Notification Manager |
|
|
Templating Feature |
|
|
Create frontend in fims-web-app |
|
|
Authentication |
|
|
Objectives for 3rd Iteration
Completed |
---|
Implement SMS and Email functionality |
Incorporate notification microservice into demo-server |
Message Template |
Create Rest API Documentation |
Testing of SMS and Email from the web interface |
Other Resource
Building a notification service in a multi-tenanted service-oriented architecture can be very complex. Here are a few resources to help assess some of the complexities involved.