Manage custom configuration

Hi Enes, 

The way I would approach this to update custom config values would be the following:

• Create an admin panel to show & control the values: 
  • https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_10.0/Architecture/Extensions/Administration/
• List the current values of your custom config values:
  • https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_10.0/Architecture/Configurator/#Retrieving_Settings
• Create Input or Select fields where the Admin can change the values and store those using the Configurator class: 
  • https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_10.0/Architecture/Configurator/#Creating_Updating_Settings

Please also note the Considerations at the end of the Configurator class article, that only longterm config changes should be used with that. For more dynamic config changes the Administration class allows to store those in the config table, so it depends a bit what you want to change and how often. 

Hope that helps for an initial overview :) 

Dennis

We had the exact same requirement and we, as part of Seven Tunes labs created a Config Manager package which exactly does what you need - we exported the package and provided details in our blog  - check it out - https://seventunes.com/updating-sugarcrm-configuration-on-the-fly/

The package follows exactly what Dennis has suggested - creates an Admin page which allows you to search/update config. But - I would suggest to use it carefully, maybe change the "DENY_LIST" to "ALLOW_LIST" so that someone doesn't update wrong configuration by mistake. Be extremely cautious if you're using it in production! I would suggest modifying the code to ALLOW_LIST for production uses.

We've also added a default password which should be sent for every update - that is presently hardcoded in the package, which could be moved to config_override or Admin dbconfig table.

Please let me know if you have any questions!

Hi Neeraja,

While I like in principle the idea, you would have to be careful as some configuration changes are not allowed in SugarCloud. Also, a small syntax error on the config file would bring down your Sugar system as the config file is a core component of the application.

How about a simple module loadable package that does just that instead?

Thanks for the review and suggestion, Enrico! I totally agree, I've changed the package defaults to "ALLOW_LIST" instead of "DENY_LIST" so that others doesn't update a wrong flag by mistake. 

Dear Dennis,

Thanks for your answer. 

In fact I tried what you explained on your answer, creating a specific route on the admin menu, getting the configuration list with excluding the keys I estimate forbidden to change (for example the db configuration), then display them on a custom view.

Have a nice week !!

Best regards,

Enes

Hello Neeraja,

I like the way you did it, searching for a value and editing it according to a password. I could take that as an idea to improve my POC.

Here is what it look like for the moment:

I created a specific API which first gets the values excluding from an array the forbidden values, and a second one which saves the values. 

Thanks for your answer too and best regards !

Enes

Glad to know it helped!