Notifications for MaUI
Driver | Approver | Contributors | Stakeholder |
---|---|---|---|
@Sergio Piazza (Deactivated) | Â | @David Silva @Frank Timmerbeil @Francisco Briceno (Deactivated) | @Sebastian Koch |
Objective | Develop Notifications for MaUI |
Due date | End of Q2 |
Key outcomes | |
Status | NOT STARTED |
Problem Statement
Notifications is a key feature to our clients and our marketing team, which means we need to develop new and improved notifications.
Scope
Must have:
Needs to work for existing site controllers
Notifications via email
Dev Todos & Ideas
Update sensor only to need the sensor id (remove PLC device ID)
incoming events are compared against notification rules by the notification-service
if a unknown sensor is received a new sensor config is created in the cloud and stored in PSQL
sensor configs can be tied notifications rules - frank pls write better thx
UX: the user home page should mention if events have been received but dont have a ntfc configured, 98 out of 112 events have notification rules
Where do things happen
 | MQTT | azeti Site Controller | azeti Cloud |
---|---|---|---|
Event triggers | X | X | Â |
Event configuration | Â | X | X (requires cfg deployment from cloud to SC) |
Notification configuration | Â | Â | X |
Notification delivery | Â | Â | X |
User flow and (new???) components
Wizard: Get data into cloud (this highly depends on the device)
I have a SC
I dont have an SC but want one
I send data via MQTT
X: Configure event rules for my existing sensors
Create trigger
Define severity
Define message
X: Configure which sensors should create a notifivation
When to send
Who shall receive it
How to send the notification
Â
Question to UX: Should we decouple the device setup from the events+notification setup?
Nice to have:
Not in scope:
Events
Where does the event come from
Timeline
Milestones and deadlines
Milestone | Owner | Deadline | Status |
---|---|---|---|
 |  | NOT STARTED | |
 |  |  |  |
 |  |  |  |