Warn when deploying objects without profile settings
I build a VF page, test it, deploy it and discover much later that I forgot to add profiles other than system admin to the page. Users can't see the page and get a permissions denied error.
So, the suggestion is to have a an optional analyzers that warns when deploying a new VF page to a target org where the only permission is System Admin. While this could be legit in some use cases, in most use cases, this is a self-inflicted omission.
Anonymous
shared this idea
-
Kris Goncalves
commented
I'd add that some of the major configuration options would be great to add to this and specifically for "new" components. Especially for source control purposes as forgetting associated profile permissions is our #1 miss (as apex tests wouldn't fail and neither would validation)
These common ones:
new custom field
new layout
new object
new tabIt's rare that any of those (plus the VF page mentioned in this idea) should be deployed with no permissions (admin-only). I would consider this a good use case for a warning-only problem analyzer as it would be a problem to deploy as is.
-
This is a great suggestion Eric, I'm going to make a few edits to the suggestion just to make this one really concrete and allow others to vote on it. If you have any suggestions for other common mistakes then absolutely suggest them as that is exactly the kind of thing we want the problem analyzers to help with.
