Sugar Developer Guide Version 5.1

Publishing and Uploading Packages

Once the user has created the appropriate fields, layout and relationships for the Custom Modules, this new CRM functionality can be deployed. Clicking the “Deploy” button will deploy the package to the current instance. This is the reccomended way to test your package while developing. If you wish to make further changes to your package or custom modules, you should make those changes in ModuleBuilder, and simply hit the deploy button again. Selecting the “Publish” generates a zip file with the Custom Module definitions. This is the mechanism for moving the package to a test environment and then ultimately to the production environment. The “Export” button will produce a module loadable zip, similar to the “Publish” functionality, except that when the zip is installed, it will load the custom package into Module Builder for further editing. This is a good method for storing the custom package in case you would like to make changes to it in the future on another instance of SugarCRM.

Figure 8: Publishing Packages creates a zip file for the new Custom Module.

Once the new package has been published the administrator must commit the package to the Sugar system by visiting ‘Module Loader’ within the Sugar Administration console. The user uploads the files and commits the new functionality to the live application instance.

 

Figure 9: Module Loader allows users to install third-party extensions and packages to the live Sugar instance.