Record Types & Page Layout Strategy 💬 In plain words: Record Types let one object act like different forms for different teams. Different picklist values, page layouts, and processes — same Account object. Use them for truly different business processes. Not for cosmetic layout changes. 📌 Example: One Account object, two businesses: 'Retail Customer' record type shows B2C picklist values and layout. 'Enterprise Client' shows contract fields and a different sales process. Same table, two costumes. 🧠One object, many costumes: A Record Type is a costume on the same object — different picklists and layouts, same table underneath. Concept Record Types split one object into business variants. • Each type can carry its own subset of picklist values, its own business process — Lead, Case and Opportunity stages — and its own page layout per profile. • Lightning has changed the calculus. Dynamic Forms and conditional comp...
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(endpointUrl);
request.setMethod('POST');
request.setHeader('Content-Type', 'application/x-www-form-urlencoded');
request.setBody('grant_type=password&client_id=' + clientId +
'&client_secret=' + clientSecret +
'&username=' + EncodingUtil.urlEncode(username, 'UTF-8') +
'&password=' + EncodingUtil.urlEncode(password, 'UTF-8'));
Http http = new Http();
HttpResponse response = http.send(request);
if (response.getStatusCode() == 200) {
Map<String, Object> jsonResponse = (Map<String, Object>) JSON.deserializeUntyped(response.getBody());
return (String) jsonResponse.get('access_token');
} else {
// Handle error response
return null;
}
}
}
In this example, you pass the client ID, client secret, username, password, and the OAuth endpoint URL. The method sends a POST request to the endpoint and retrieves the access token from the response.
2. Implementing Refresh Token Mechanism:
To maintain continuous interaction, it is essential to handle token expiration and implement a refresh token mechanism. The following Apex code demonstrates how to refresh an access token using the Refresh Token Flow:
public class TokenRefresher {
public static String refreshToken(String clientId, String clientSecret, String refreshToken, String endpointUrl) {
HttpRequest request = new HttpRequest();
request.setEndpoint(endpointUrl);
request.setMethod('POST');
request.setHeader('Content-Type', 'application/x-www-form-urlencoded');
request.setBody('grant_type=refresh_token&client_id=' + clientId +
'&client_secret=' + clientSecret +
'&refresh_token=' + refreshToken);
Http http = new Http();
HttpResponse response = http.send(request);
if (response.getStatusCode() == 200) {
Map<String, Object> jsonResponse = (Map<String, Object>) JSON.deserializeUntyped(response.getBody());
return (String) jsonResponse.get('access_token');
} else {
// Handle error response
return null;
}
}
}
In this example, you pass the client ID, client secret, refresh token, and the OAuth endpoint URL. The method sends a POST request to the endpoint to refresh the access token, and the refreshed token is returned from the response.
Conclusion:
Handling access tokens and implementing a refresh token mechanism are crucial aspects of securely interacting with external systems in Salesforce. By using the provided Apex code examples for token generation and refresh token functionality, you can ensure uninterrupted communication and maintain the security of your interactions.
Remember to customize the code according to your specific OAuth implementation and endpoint requirements. Proper error handling and additional security measures should be implemented to enhance the reliability and robustness of your integration.
References:
- Salesforce Developer Documentation - OAuth 2.0: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_understanding_oauth_endpoints.htm