Idea for model "Alerts"

  • 2
  • Idea
  • Updated 3 years ago
  • Under Consideration
In addition to fields, conditions, and actions, model alerts would be useful. If certain criteria is met by records returned in a query, those rows get highlighted, marked, or shown in a pop up. For example, if a row contains a priority field equal to "urgent", the font would turn red and get underlined. If a new record was created by another user and assigned to the currently logged in user, a pop up would appear on page load to alert them that a record had been assigned. It would be nice to be able to aggregate alerts of the same model so that the alert could say "You have 5 new messages". At least some of this is possible with conditions and actions now, but I think there would be efficiency in a specific tool for modifying fonts/backgrounds/highlights, etc.... based on queries.
Photo of Skuidward Tentacles (Raymond)

Skuidward Tentacles (Raymond), Champion

  • 17,224 Points 10k badge 2x thumb

Posted 3 years ago

  • 2
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,006 Points 20k badge 2x thumb
Raymond.  lots of interesting ideas here.  But they go lots of different ways,  some which I think you can already deliver. 

1.  Conditional Formatting:  We have had this idea on our drawing board since we first did conditional rendering.  

2.  New Record Warning:  This could be accomplished today with a model that queried for the new records.  We have also built solutions that do polling, so that a model gets its new records as they are saved, and then elements on the skuid page are exposed. 

3.  Aggregated numbers:   You can do a few things here.  You can use merge syntax  {{$Model.myModelName.data.length}} to retrieve the number of rows.  Or you can create an aggregate model that returns the count of rows that match your criteria. 

So yes... 

But thanks for your creative ideas here - keep them coming. 
Photo of Skuidward Tentacles (Raymond)

Skuidward Tentacles (Raymond), Champion

  • 17,224 Points 10k badge 2x thumb
Thanks for your response. Ultimately I would like the end user to be able to select any field on any object I allow and choose query conditions that would trigger alerts. That would put a great deal of power in the hands of the end user that would be hard to recreate if you had to have the developer create a bunch of models and actions every time a user wants to be alerted when a custom field is updated to a certain value for a particular customer. The tools are probably all there and with enough time, patience, and creativity, it could probably be built, but having that functionality built in as part of the managed package seems like s huge value add.
Thanks