Blog

After writing and refactoring lots of new code, at some point you have to say you’re finished and get it into some customers’ hands and on some live systems. This can be a scary process no matter how many unit tests you have passing or how much testing you do on your own servers. As we pushed through customer testing, here a few of the unexpected things that came up as we tested on other customer systems.

If you have ever needed to move some fields around on the Target Lists module you may have done what you normally do for changing layouts and gone to Sugar's Studio tool. It makes sense as this is where you can add new fields, connect modules to other modules, and change your layouts. But when you go there you find that Target Lists is not in the module outline.

Three new webhooks have been added that we highly recommend that you take advantage of: no_license_24hours, trial_will_convert, subscription_will_renew. Learn how to take advantage of them and increase your conversions.

A lot of effort goes into launching a new product. Especially a new product that is an add-on to SugarCRM. Executing on your product idea is hard enough. You don’t need to waste additional resources on operational pieces that are not core to your business. You need to get your idea out there as soon as possible to not only prove the idea, but to help iterate on it; to find that perfect market fit.

SugarCRM has a nice feature included in its Module Loader that will display the software license included with a module. This is a simple way to ensure that users read and understand what the license agreement for using a given module is before installing it. It's really simple to add your own license to a module. Simply drop a LICENSE.txt into the root directory of your zip file and SugarCRM with automatically display the license prompt during installation. But what happens when it you can't get your license to show?