Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words: Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example: API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way: if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad: Business data is trappe...
Introduction: In Salesforce, interacting with external systems often requires the use of access tokens for authentication and authorization. To ensure secure and uninterrupted interactions, it is essential to handle token generation and refresh token functionality properly. In this blog post, we will explore Apex code examples for generating access tokens and implementing a refresh token mechanism to maintain secure and continuous communication with external systems. 1. Generating Access Tokens: To generate access tokens for interaction, you can use the OAuth 2.0 authentication protocol. The following Apex code demonstrates the generation of an access token using the Username-Password Flow: public class TokenGenerator { public static String getAccessToken(String clientId, String clientSecret, String username, String password, String endpointUrl) { HttpRequest request = new HttpRequest(); request.setEndpoint(e...