Contributing to an Open Source Salesforce Managed Package

Use Case: Volunteers for Salesforce

Some Salesforce managed packages provide developers in the community the opportunity to contribute with code and features. Packages such as the Non Profit Starter Pack or Volunteers for Salesforce are open source software, which means developers can contribute to the code on GitHub (https://github.com/) resulting into new features or improvements to the software. These features are then packaged into the managed version being upgraded.

University of New Hampshire engaged Daizy Logik to develop several enhancements to Volunteers for Salesforce that were then incorporated back into the package. Based on this work we developed this step-by-step technical guide on how to successfully contribute to an open source Salesforce managed package. The process described here uses Volunteers for Salesforce as an example but could be more generally applied to any open source managed package.

Development Environment Setup

To facilitate the setup of your development environment we recommend using these freely available utilities that should be available on both Mac and PC. 

Salesforce Push Upgrade – How To

Creating a Patch for a Managed Package and Doing a Push Upgrade

Posted by Nineta Martinov

Recently I had to create a Patch for one of my clients’ managed package in order to make a minor change and push it out to all the client organizations using the package. For the most part the Salesforce documentation is fairly accurate in guiding one through the process. However, I could not find any help with screenshots documenting the end-to-end process so I put this together.

Remember that a Patch should only be created if no new components are being added to the managed package. For example, if you want to change the wording in a Visualforce page you would want to use a Patch.

Step1. Log into the main development org. This is where you developed the managed package. Go to Create -> Packages and click on the Managed package name.