I have a requirement on constellation to display notification on the home/portal. Additionally there is requirement that says Each Alert/Notification stays on the screen until user manually removes/acknowledges it, even if the project is closed. I am trying to use the Bell notification in portal but that does not satisfy the acknowledgement part. Any suggestions or alternatives on this.
The OOTB bell is better for lightweight notifications, but it does not support the kind of explicit per-notification acknowledgement and persistence you need.
A better design is to create a custom notification/alert data object and surface it on the home page or portal as a list/banner, with statuses such as Open, Acknowledged, and Dismissed. That way each alert remains visible until the user explicitly acts on it, even if the related project/case is already closed.
even in UI Kit the notification framework didn’t support this. As @RaviChandra has outlined, building your own notification framework would be best - extending the existing one in Constellation isn’t really an option (The Views are not configurable, so no ability to “remove/acknowledge”.
CRUD on data?
You could use data instance and CRUD actions on those data. This would achieve the ability to see a list, open a view or take action (dismiss) the notification.
Insights (Reports)?
Could you look to use Insights to surface up the important milestones to view? I find many times there is a desire to build these kind of notification frameworks, like you see on social media and collaboration platform but the reality is, as we know notifications get overlooked or overwhelming.
Using Insights, you could help surface the events that the business is in need of viewing? This gives the data, but not the overwhelming notifications and need to dismiss them.
