function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
Inna KersmanInna Kersman 

Publishing managed packaged without being a partner

I've created a managed package that uses Apex and which I need to install into a Professional edition org. The only way to do so (that I'm aware of) is to become a partner, go through the security review and publish it on AppExchange. But it's really just a button and a tiny piece of code. It's just not worth the hassle but I need to install it somehow. Is there any other way at all?
Raj VakatiRaj Vakati
You can install it without using the package .. 

means 

Export the metadata from your source org
and import the same metadata in target org  

If you don't want to do this , you create create a managed package 
Inna KersmanInna Kersman
I'm not sure I understand what metadata has to do with this? I've got some Apex triggers and Visualforce in the package. Can you please explain?
Raj VakatiRaj Vakati
This is the steps you need to do .. 

Download the apex class, trigger and pages etc using the eclipse or workbench and deploy them into another org using eclipse or workbench .. 

Refer this videos 

https://www.youtube.com/watch?v=CyWSAeQbANQ

https://www.youtube.com/watch?v=YW9aPrxvK3A



https://www.simplysfdc.com/2016/12/salesforce-deployment-with-unmanaged.html


https://www.salesforcetutorial.com/workbench-salesforce-using-workbench/

https://www.forcetalks.com/blog/how-to-use-workbench-with-salesforce/
https://www.redargyle.com/blog/how-to-pull-a-metadata-backup-from-workbench/
Inna KersmanInna Kersman
Thanks for the resources but as far as I'm aware Eclipse or Workbench can't be used with Professional edition. Is this incorrect?
Raj VakatiRaj Vakati
My bad Inna .. 

you are correct .. 

Your app can contain business logic such as classes, triggers, email services, etc. written in Apex. As a general rule, Apex is not supported in GE/PE, so it will not run in these editions. However, Apex developed as part of an ISV app and included in a managed package can run in GE/PE, even though those editions do not support Apex by default.
  1. You must be an eligible partner with salesforce.com and your app has to pass the security review. The appropriate permissions will automatically be enabled after you pass the security review.
  2. Here are some important considerations for using Apex in GE/PE.
  3. GE/PE customers can’t create or modify Apex in your app; they can only run the existing Apex.
  4. Your Apex code should not depend on features and functionality that exist only in DE, EE, UE, or PXE, or your app will fail to install.
  5. Make sure to use REST if you plan to expose an Apex method as a Web service. Apex classes that have been exposed as a SOAP Web service can’t be invoked from an external web app in GE/PE.
  6. Using Apex to make Web service callouts is allowed in GE/PE. For instance, if you’re planning to make a Web service callout to an external Web service, as long as the managed package is authorized, these classes will function in GE/PE.


https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/dev_packages_apex_ge_pe.htm