Notification Service
The notification service provides message sending, notification dispatch, and notification receiving functionalities.
Message Sending
When service modules in Flow2 need to send messages, they do so through queues or interfaces. When pushing notifications, the following message information should be included:
P.S. The following types are only for supporting Flow 2 requirements; the notification service's inherent logic is not reflected here.
- Message Source Including Workspace information (ID, Name, Type), Project information (ID, Name), Repository information (ID, Name), User information (User who triggered the information, if any) (ID, DisplayName)
- Message Type Including regular messages and system messages
- Message Content Including the message title and message body
Message Receiving
System Messages
System notifications, such as system maintenance notifications, new feature release notifications, and other system messages, have no difference between LCMS and TMS perspectives.
Business Notifications
LCMS Perspective
If a message's source Workspace type is LCMS, it should be displayed in the UI in the form of Workspace/Project/Repository. If the source Workspace type is TMS, it should only display the Workspace in the UI. These types of messages support filtering by Vendor list, which comes from the notification service, obtaining the information list of all Workspaces of TMS type in the current user's notification list.
TMS Perspective
If a message's source Workspace type is TMS, it should be displayed in the UI in the form of Workspace/Project. If the source Workspace type is LCMS, it should only display the Workspace in the UI. These types of messages support filtering by Client, with the Client list coming from the notification service, obtaining the information list of all Workspaces of LCMS type in the current user's notification list.
Message Categories (Items marked with * indicate TMS as the receiver)
System Messages
- System maintenance notification
- New feature release notification
Within Workspace
Quotation
- Quote generation (push) (including initial quotes and subsequent new quote pushes)
- Quote failed
- Quote confirmed* (the pusher is a person with the Owner role in the TMS Workspace)
- Request for new quote* (the pusher is a person with the Owner role in the TMS Workspace)
- Order delivered
- Order accepted*
- Order closed* (messages are only pushed when a vendor has been selected, the pusher is a person with the Owner role in the TMS Workspace)
- Order pending payment
- Order paid*
- Receipt uploaded
Content
- Import task completed
- Import task failed
- Export task completed
- Export task failed
Localization Project Management
- Translator task delivered*