cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to define hide the global "Advanvced filter"-button

Request

With the introduction of "Custom pages" in model-driven apps, it would be great if developers had the ability to hide the global "Advanced filter"-button - either as a setting on a "per entity"-basis (preferably), "per app"-basis, or "environment"-basis.

 

Reason

We would like to restrict the user from interacting with tables/entities, which should only be accessible from a "Custom page" or embedded canvas app.

 

AS-IS / current functionality

Users have the ability to access model-driven views and forms of all entities through the global "Advanced find"-button. This potentially leads to compliance violation scenarios, in which users are allowed to interact with data in an unintended way (i.e. outside the "rules" that a developer have otherwise defined within a custom page or embedded canvas app).

Status: New
Comments
CharlesS
Advocate IV

Excellent idea!

 

Indeed, the current functionality could expose data that should remain confidential.

 

In addition, it would be great if we could control the visibility of views per security role, just like forms.