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:

Road map for the notification service:

...

Create frontend for fims-web-app

...

Notification micro service on Apache's GitHub account

...

Portfolio Event Listener

...

Implement SMS and Email functionality

...

Message Template

...

Incorporate notification micro service into demo-server

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! 

1. Repository
2. Drive Containing Relevant documents

Service Roadmap/Feature

1. Implement basic SMS and Email integration
   1. Interface with Twilio
   2. Gmail integration
2. Incorporate notification microservice into demo-server to enable testing.
3. Basic Message Templating
4. Rest API
   1. Documentation

5. Add support for FINCN Mobile

   1. Implement FCM push notification with a multi-tenanted approach
      1. Resources: Official FCM Documentation, FCM implementation in Java, 
6. Replicate SMS/Email/Push Notifications functionalities for Portfolio/Office/Group/Employee Event Listener
7. OTP through Push Notifications, SMS and Email
8. Message Localisation
9. Disable

...

Message Localisation

...

1. SMS and Email for specific users by using a custom field in customer
2. Tenant Reputation Management
   1. Notification subscription and unsubscribe feature via

...

1. 1. SMS and email
2. Message Templating

   ...

   1. 1. Bulk SMS

   ...

   Cloud Messaging (Firebase)

   1. 1. /Email/Push Notification
         1. Customized Bulk SMS
         2. Generic SMS
      2. Customized Messaging
         1. Templating
   2. Assess the feasibility of third-party integration with other messaging services
      1. Amazon SES Multitenant Solution
   3. Final test plan

   Objectives for ongoing

   ...

   Iteration

   Feature/Class	To Do: Features

   Comment and DescriptionCustomer and Portfolio Event ListenerAdd more events

   Status
   Rest Controller and Notification Manager	Add fetch operations	Completed
   Email Service	Allow configuration of

   service of service

   service after instantiation	Completed
   Email Configuration Repository and schema	More query for update and delete	Completed
   SMS and Email Service	Allow

   configuration

   reconfiguration of service after instantiation	Completed
   SMS configuration Repository and schema	More query for update and delete	Completed
   Commands for SMS and Email Config and handlers	Update and delete commands	Completed
   Rest Controller and Notification Manager	Restructure API Naming Conventions	Completed
   Templating Feature	Create basic HTML templating feature with thymeleaf	Completed
   Create frontend in fims-web-app	More query for update and delete	Completed
   Authentication	Implement Permitted Feign Client Authentication	Completed

   
   

   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.

   1. Building scalable multitenant email sending programs