Perspectives is a great addition to the application and making only certain parts of the model visible to those dashboards connected to that perspective is excellent. Adding the ability to filter th...
Hey. If we take the example of a model that contains Tickets, both Open and Closed. We have dashboards that only look at Open Tickets. So applying Security is not applicable because the users have access to both Open and Closed tickets. Creating Security would stop them seeing Closed tickets on other dashboards they have access to. Adding a locked Filter onto a dashboard doesn't look great, it can often confuse users who need explaining what a locked filter is. Further, we would then want the values available in other filters to be limited which they are not. Adding a filter at the Perspective level takes away all of this in that a perspective of data is not just the reduction of fields but also the tailoring of the dataset. I am not sure if this also has some runtime/performance advantages, e.g. if the data is limited at the model level then there is less for the dashboard, widgets and jaql (e.g. for Filter values) to have to process, this may be marginal, but may be significant in some very large models.