Salesforce Simplified Was Built Without a Backend Browser extensions have a trust problem. They can potentially see a lot. So when an extension is designed for something as sensitive as a Salesforce org, the architecture matters as much as the features. Salesforce Simplified takes a deliberately different approach: There is no server belonging to the extension. Your Salesforce data stays between your browser and your Salesforce org. No account required Salesforce Simplified doesn't require you to create an account. There is no Salesforce Simplified cloud account storing your organizations. There is no dashboard hosted somewhere else. There is no profile database. You install the extension and use it with Salesforce. Salesforce queries go to Salesforce The extension's primary job is to interact with the Salesforce org you are already working in. Metadata queries, debug-log information, setup information and other Salesforce data are retrieved from your org. They are not sent t...
Stop Going to Setup for Every Small Salesforce Question If you work in Salesforce long enough, you develop a familiar routine. You are working on an Apex class. Something doesn't look right. You need to know what changed. So you leave the page. Open Setup. Find the right section. Search. Check the component. Go back to what you were doing. Five minutes later, you've answered a question that should have taken thirty seconds. That is the problem Salesforce Simplified is designed to solve. The Setup round trip Salesforce Setup is incredibly capable, but it is not always the fastest interface for answering small operational questions. Developers and architects regularly need answers like: What Apex changed today? Which Flow was modified? Who changed this validation rule? Where is that custom field? What did another developer deploy? Which debug logs were generated? What is consuming our API limit? Is Salesforce currently experiencing an incident? Can I retrieve these components?...