Salesforce Playground | Architecture, Agentforce, Commerce and AI

Salesforce custom labels can be used across different Salesforce technologies, including Apex, Visualforce, Aura components, and Lightning Web Components (LWC). Here's how you can use custom labels in each of these contexts: Apex : In Apex, you can access custom labels using the System.Label global variable. Custom labels are referenced by their developer name. String labelValue = System.Label.MyCustomLabel; Visualforce : In Visualforce pages, you can reference custom labels using the $Label global variable. <apex:outputText value="{!$Label.MyCustomLabel}" /> Aura Components: In Aura components, you can access custom labels using the $Label global value provider. <aura:component>     <aura:attribute name="labelValue" type="String" default="{!$Label.MyCustomLabel}" /> </aura:component> Lightning Web Components (LWC): In Lightning Web Components, you can import and reference custom labels using the @salesforce/label scop...

Skinny tables in Salesforce are custom tables that contain a subset of fields from a standard or custom object. They are designed to improve report and query performance by having a narrow width; in other words, they include fewer fields, which reduces the number of joins needed during a query execution on large objects. Skinny tables are handy when dealing with huge data volumes. Here are some critical points about skinny tables: Performance Improvement: Skinny tables can significantly speed up the performance of read-only operations, especially for complex queries and reports that do not need to access all fields of an object. Creation by Salesforce: Salesforce must enable skinny tables for your organization, and they are created, maintained, and managed by Salesforce upon your request. Supported Objects: Skinny tables are supported for Account, Contact, Opportunity, Lead, Case, and custom objects. Field Types : They can contain commonly used fields, such as checkboxes, dates, em...

Salesforce custom labels are custom text values that can be used in Apex, Visualforce, Lightning components, and formulas. They provide a convenient way to manage and centralize text that appears throughout your Salesforce application. Here are some common use cases for Salesforce custom labels: Localization and Multilingual Support: Custom labels allow you to store text in multiple languages, making it easier to support users in different regions. Salesforce automatically displays the appropriate language based on the user's language settings. Static Text and Messages : Custom labels are commonly used to store static text, such as field labels, button labels, error messages, help text, tooltips, and other user interface elements. Storing these values as custom labels centralizes them and makes it easier to update them across your application. Dynamic Text and Merge Fields : Custom labels support merge fields, allowing you to include dynamic data in your text. This can be useful f...

Salesforce executes a sequence of events in a specific order when saving a record with an insert, update, or upsert statement. Prior to this, the browser performs JavaScript validation for dependent picklist fields, restricting them to their available values. No other client-side validation takes place. Order of Execution To see the diagram of the order of execution, visit the Order of Execution Overview on the Salesforce Architects site. Please note that the diagram may differ from the information given here as it is specific to the indicated API version. The Apex Developer Guide page provides the latest information on the order of execution for this API version. Access different API versions through the version picker in the Apex Developer Guide.

Bell Notification is a feature that provides users with real-time updates and notifications about various activities and events happening within the Salesforce platform. It is represented by a bell icon in the Salesforce interface's top right corner. The bell icon displays a badge indicating the number of unread notifications when there are new notifications, such as mentions, comments, tasks, approvals, or any other relevant updates related to records or processes. Clicking on the bell opens a dropdown menu listing these notifications, allowing users to review and take action quickly. Bell Notifications help users stay informed and engaged with essential activities in their Salesforce org, ensuring timely responses and efficient collaboration. Users can customize their notification settings to receive alerts for specific events or activities according to their preferences and roles within the organization. Create a Custom Notification Detail View of Custom Notifications Fill in t...

In Salesforce, restriction rules are used to restrict the visibility of sensitive data based on specific conditions or criteria. These rules help organizations comply with privacy regulations and ensure that sensitive information is only accessible to authorized users. Restriction rules let you enhance your security by allowing certain users to access only specified records. They can prevent users from accessing records that can contain sensitive data or information that isn’t essential to their work. Restriction rules are available for custom objects, external objects, contracts, events, tasks, time sheets, and timesheet entries and can be configured in the Object Manager or through the Tooling or Metadata API. Restriction Rules Considerations Restriction rules for external objects don’t include organization-wide defaults or sharing mechanisms. Only external objects created using the Salesforce Connect: OData 2.0, OData 4.0, and Cross-Org adapters support restriction rules. External o...

You can freeze a User account instead of deactivating them. This is intended to be used in situations where the User account requires more work before deactivating it. It is also possible to freeze multiple Users at once, by using the latest version of Data Loader . The User property 'Frozen' is controlled in the object 'UserLogin' by the field 'IsFrozen.'  IsFrozen is a boolean field so it is either 'true' (frozen) or 'false.'  System Administrators can use Data Loader to export and update the  UserLogin   object. 1. Run an Export using Data Loader from the  UserLogin  object ( Note:  Select the  Show all Salesforce objects  checkbox). 2. Select the  Id ,  UserId ,  IsFrozen  fields and complete the export. Query example:  Select UserId, Id, IsFrozen FROM UserLogin Note:  It's not possible to export additional user details such as Full Name, Username, or Email on export of UserLogin records. It's recommende...

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...