2025-06-21 - Consolidated notification messages
Revision as of 14:19, 21 June 2025 by Sven the Barbarian (talk | contribs) (Created page with "Service - Search Results = Triggering processing of consolidated notifications = * Eventbridge for one off events * Use for notificationGroups that have a recurring schedule * Not for notificationGroups that consolidate when x number of messages received * When a recurring group is processed, add it's schedule to the old schedule timeframe so that the time processed is standard (eg processes every day at the same time) = Processing notificationGroups after x number...")
Triggering processing of consolidated notifications
- Eventbridge for one off events
- Use for notificationGroups that have a recurring schedule
- Not for notificationGroups that consolidate when x number of messages received
- When a recurring group is processed, add it's schedule to the old schedule timeframe so that the time processed is standard (eg processes every day at the same time)
Processing notificationGroups after x number of messages
- This is handled each time a message comes in, count the number of consolidated notifications waiting to send
Limits
- Maybe hardcode a const max frequency or number of consolidated messages a group can handle, perhaps deactivating groups that process too many
- Hardcode a max number of consolidated messages to list in one message
Message content
- triggers match to flowSteps so we know the possible params of each message
- Each notificationGroup sets up for each message type whether to show aggregate or detailed list of the messages (can show both)
- Must show something for each triggerGroup
- Both aggregate and detailed can choose which params to show
- params can be an array which orders the params in the message output
- add these settings to ?versionedData
Notes
- consolidated maybe have ttl setting to auto remove? Or could clean up each time a group is processed