SugarCRM’s hosting objective is to maintain the integrity of the standard Sugar functionality when we upgrade a customer instance, and limit any negative impact our upgrade has on the customer’s modifications.
Prior to Sugar 5.2.0j (Patch J), Module Loader did not have the ability to detect whether the changes being uploaded are deemed “upgrade-safe”. For example, if a customer were to upload a module that modified standard Sugar functionality, an upgrade of the instance (new patch, new release) could impact those modifications, resulting in a production problem for the customer.
Modifications using the rest of the Developer Tools section of Admin are considered upgrade-safe. This includes Studio, Module Builder, and Workflow.
New Access Controls
Sugar 5.2.0j (Patch J) introduced a new Module Loader feature, the Module Scanner. Module Scanner grants system administrators the control they need to determine the precise set of actions that they’re willing to offer in their hosting environment. This feature is available in all editions of Sugar, and is enforced in the Sugar On Demand environment. Anyone else who is hosting Sugar products will have the opportunity to take advantage of this feature as well.
For more information on package scanner, please refer to the module loader section of the developer guide specific to your release: