Some customers have been reporting that they are now "locking" their applications when they publish and push them to their tenants.
This is to prevent users from changing the application logic in triggers, adding new objects, etc.
However, they say they still need their back-office users to be able to create/edit/clone views.
It seems with a "locked" application, this ability is not available.
This new feature would allow the ability to keep an application locked (and safe for accidental changes) but still to allow end users to create views of the data.
For that point, I believe the best approach would be to use the option: Partially Locked application.
But this has introduced a new point: How to lock everything EXCEPT for the ability to create new views and clone existing views on ALL objects in the application? Is there a way of doing this? is it even possible?
So, that's where the ability for Rollbase Users to create/edit/clone views in a Locked application takes place.
In addition to the above request, the partially locked application should allow users to create new triggers to argument the existing logic to implement customizations as necessary.