Salesforce Playground | Architecture, Agentforce, Commerce and AI

Here are some resources to get you started using Salesforce architecture diagrams. Salesforce Architects | How to Build Salesforce Diagrams Salesforce Architects | Documentation and Implementation Diagrams The concept of using levels to convey different kinds of detail is common to many frameworks, including the C4 model which is used to visualize software architectures. The C4 model for visualising software architecture Getting Started with Salesforce Diagrams Diagramming Essentials How to Build Documentation and Implementation Diagrams | Trailhead Live Project Documentation for Salesforce B2C Commerce Functional Architects Salesforce Architecture Diagrams: Quick Look

Login using the SOAP login request and from then on use the session token for making REST API requests.In this we need to pass Username and Password as credentials.Upon invocation, the API authenticates the credentials . It then returns the  sessionId , the user ID associated with the logged-in username, and a URL that points to the Lightning Platform API to use in all subsequent API calls.If Salesforce returns a Login fault , try adding the security token at the end of the user’s password.  The limit is 3,600 calls to login() per user per hour. Exceeding this limit results in a “Login Rate Exceeded” error. After reaching the hourly limit, Salesforce blocks the user from logging in. Users can try to log in again an hour after the block occurred. Sample Code -             HTTPRequest request = new HTTPRequest();             String username = 'rpatnaik@docmation.com';            ...

In a server-to-server integration, there is no need for an user to interactively log in to provide authorization.  In this case OAuth 2.0 JSON Web Token (JWT) bearer flow can provide the authorization. Communities support all available authentication flows, except for the username-password OAuth authentication flow and the SAML assertion flow ( https://help.salesforce.com/articleView?id=networks_auth_configure_oauth.htm&type=0 ) Hence , we can use a flow like web server or user agent flow or use JWT flow. ( https://help.salesforce.com/articleView?id=remoteaccess_oauth_jwt_flow.htm&type=0 ) When we talk about JSON Web Token, it is consist of 3 parts Headers –  Which contains the algorithm which will be used to sign the request Payload –  The actual data and information about the users Signature –  Signature consists of 3 parts and the structure is given below.   Payload consist of 4 parts issuer "iss", this is the consumer key for your connected app audi...

Scenario - Sometimes we want to authorize servers to access data without interactively logging in each time the servers exchange information. For these cases, we can use the OAuth 2.0 JSON Web Token (JWT) bearer flow. This flow uses a certificate to sign the JWT request and doesn’t require explicit user interaction. However, this flow does require prior approval of the client app. Profiles will need to be pre-authorized with the connected app. There was also a requirement to make a rest call to get Salesforce data using Salesforce Community User Context. Option 1: Authenticate using the SOAP login request Option 2: OAuth 2.0 JWT Bearer Flow for Server-to-Server Integration

In Salesforce, Apex-based record sharing allows you to programmatically share records with users or groups based on specific criteria or conditions. This is useful when you need to dynamically adjust record access beyond what can be achieved through standard sharing settings or manual sharing. Create Apex Sharing Reasons Share Objects and Fields StandardObjectNameShare Example -  Let's say you want to share records with relators who belong to the "Sales" role. Here's an Apex class that uses Apex sharing to share records with users who meet the defined criteria. public class RecordSharingController {          public static void shareRecords() {         // Query records that meet the sharing criteria         List<House__c> recordsToShare = [SELECT Id FROM House__ c WHERE Status__c = 'In Market'];                  // Create a list to hold new sharing objects  ...