+ Start a Discussion
JD2010JD2010 

Centralized Configuration

Wanted to get some insight from some of the great developers on the forum here regarding an architecting challenge we're coming against. Basically, we have an app that interacts with a system other than ours based on a set of credentials (which we provide). What we want to do is, instead of having the customer installing the app have to mess with the credentials (particularly when the password gets updated), we want their configuration with their app installation to auto-update to our configuration -- effectively centralizing the configuration (and pushing updates to the customer orgs every so often). Reason for this is we don't want to add the additional load time and api call outs to our org for the config data every time something might run.

 

Does anyone have any ideas on the best way to do that, or corrections on our current logic? I was thinking of potentially doing some sort of SOAP call to our master salesforce org, but not sure if that's particularly efficient, either.

 

Thanks for your time!