Salesforce IdeaExchange

Managed Package Visual force

What we have discovered lately that manage packaging visual force components in our SFDC implementations does not sheild them from the users of the application. In managed package the apex classes, triggers and only the controller part of the application are hidden from the user rest is exposed, though one cannot modify but surely can replicate.
What's the solution for this?

mtbclimber
11/09/08

The majority of your IP should be in Apex. Like S-controls, which are also not obfuscated, if you are doing a significant amount of Javascript in your pages/components there is no point in hiding it because it's always in clear view to the browser.

Yes there is a difference for Visualforce as it is a server-side solution but again, the logic should be shielded in your controller.

Given there is currently no mechanism for customer customizations to be included in your page the choice to not obfuscate pages was done so they can see your page and clone it. Of course if your controller is not global they will not be able to do this and for that reason we want to move to an obfuscation approach for pages that is driven off of the controller access modifier, i.e. only show pages that are tied to global custom controllers or standard controllers. Can we update this Idea to reflect that end-state?

That being said if you want to hide your implementation from your customers you can do so by moving to custom Visualforce components today as they are always obfuscated.

track comments for this idea

Please log in to post a comment

recently promoted by:

craskulinecz
balraj_singh
shweta_singh
prateek_gupta
ejw
amit_kumar
AlexCRMmanager
isaha@navatargroup.com

Resources

Ideas Under Consideration

Successforce.com

Managed Package Visual force - Salesforce IdeaExchange

Salesforce IdeaExchange

Managed Package Visual force

Search Community

Categories

1-800-NO-SOFTWARE | Privacy Statement | Security Statement