How to write code for SugarCloud webinar Q&A

Document created by Michael Shaheen Employee on Jul 17, 2019Last modified by Matt Marum on Jul 19, 2019
Version 5Show Document
  • View in full screen mode

At the end of the July 16, 2019 "How to write code for SugarCloud" webinar, we opened the discussion for questions. This is a curated list of the questions we received and their answers.



On the cloud when updating a module, how can we delete/remove old unused files?

Instead of upgrading package versions, I recommend uninstalling the previous version and then installing the new one. Uninstalling will remove all existing files and give you a clean slate for the install of the new module.

Is it possible to add some files directly outside custom folder? e.g. validation domain (txt file and CNAME) from AWS console, SES service

Checked with SugarCloud and Sugar Support team. No, this is not feasible within SugarCloud today. Updated

How can we access your Sugar unit testing?

If you are a SugarCRM Partner or Customer, then simply send a request to Please include your Github username.

Is there an example script for generating Module Loadable Packages?

There are several examples in different SugarCRM open source repositories. Specifically, the Professor M project contains a script and instructions for this. See

Does the SugarCloud Module Loader accepts "post-install" scripts, for example to launch a QRR after install?

It does. See post_execute $installdef action. 

What was that git hub repo again, the one for Professor M's School

Professor M's School for Gifted Coders is available on Github at

What are the minimum Sugar system requirements?

Here is a list of our Supported Platforms

This page of additional resources on the Support site may be of further help to you:

What are VARs and ISVs? Is one of them a partner?

Value Added Reseller (VAR) partners - This is a type partner that sells Sugar to end customers while also providing added services that include Sugar customization and integration for end customers.

Independent Software Vendor (ISV) partners - This is a type of partner that integrates their own software applications with Sugar to create a combined solution.


For more details on the different SugarCRM partnerships see:

Can you share that presentation with us/me?

The video recording and a pdf version of the slide deck have been posted to the Developer Community:

How to write code for SugarCloud (Recording)

How to write code for SugarCloud (Slides)

Is bulk limit to 20 req/s per user or per instance?

The 20 requests per second limit is per Sugar instance.

Is it possible to develop a project locally and provide you with the whole code package and Database and you upload on the cloud?

Yes, you can migrate a locally developed Sugar instance to the SugarCloud. Your customizations will need to comply with Package Scanner and the Sugar Cloud Policy Guide to be accepted. If you are already using Module Loadable Packages then this will make it a lot easier. Please contact Sugar Support for assistance with migration. Updated

I uploaded a package with a PHP error by mistake which broke my test environment. How can I fix this?

For now, this would have to be addressed by contacting Sugar Support. We plan to provide access to the PHP error logs in the future. This should help with remedying the issue when it happens.

Where can you find the the demo instance builder?

The demo Builder is available to all VAR partners. If you are part of a VAR organization, see your administrator for access. ISV partners can request access via a form in the ISV Partner Portal.

Is there a list of PHP functions that cannot be used in the cloud available somewhere?

Please see the Module Loader Restrictions page in the Sugar Support Documentation. There is also an article regarding Module Loader Restriction Alternatives that may be helpful.