Salesforce Playground | Architecture, Agentforce, Commerce and AI

Sandbox Management and Best Practices An overview of different types of sandboxes, top use cases for each type, and what is included with each when the sandbox is created or refreshed. There are 4 types of sandboxes and some are only included in certain Salesforce Editions or purchased for an additional cost, please contact your Salesforce Account Executive for details. Common use cases for each type of sandbox and recommended best practices Developer - may be refreshed every day, does not include any data automatically but allows 200 MB of data to be imported or created. The most agile and plentiful sandbox type for proof of concept, metadata-specific development, or just playgrounds for Developers and Admins to run through potential setup changes to review impact. Developer Pro - may be refreshed every day, does not include any data automatically but allows 1GB of data to be imported or created. Same idea as the Developer but with a higher storage limit for the purpose of creating or...

Properly classifying sensitive data in Salesforce is of utmost importance for any organization to implement effective data management policies and ensure compliance with global privacy regulations such as GDPR, CCPA, HIPAA, and others. By categorizing data based on its sensitivity level, companies can apply appropriate security measures, access controls, and data handling practices to reduce potential risks and safeguard sensitive information. Here's how sensitive data can be classified to support data management policies in Salesforce: Compliance Categorization The compliance acts, definitions, or regulations that are related to the field’s data. Default values: CCPA—California Consumer Privacy Act COPPA—Children's Online Privacy Protection Act GDPR—General Data Protection Regulation HIPAA—Health Insurance Portability and Accountability Act PCI—Payment Card Industry PersonalInfo—Personal information. For use with the Enhanced Personal Information Management feature. Only ava...

When setting up a Salesforce sandbox environment, it is essential to consider specific factors to ensure adequate testing and development while maintaining data integrity and security. Here are some key considerations: Servers and IDs Each sandbox and production org has a unique org ID. When a sandbox is created or refreshed, Salesforce creates an org, and the org ID changes each time. In places where the org ID is used, such as metadata and text values, Salesforce replaces the old sandbox org ID with a new one. To find the org ID for the current org, you can go to Setup and search for "Company Information" in the Quick Find box. A hardcoded org ID should be updated with the current ID for the sandbox to ensure that scripts or processes, such as test scripts or Web-to-Lead, work properly. Salesforce creates sandbox orgs on multiple instances, and when a sandbox is created or refreshed, it is assigned to a specific instance, which can cause sandboxes to appear on different URL...

Sandboxes create copies of your Salesforce org in separate environments. Use them for development, testing, and training, without compromising the data and applications in your production org.  Sandboxes: Staging Environments for Customizing and Testing Sandboxes are isolated from your production org, so operations that you perform in your sandboxes don’t affect your production org. Sandbox Types Developer Sandbox – A Developer sandbox is intended for development and testing in an isolated environment. A Developer Sandbox includes a copy of your production org’s configuration (metadata). Developer Pro Sandbox – A Developer Pro sandbox is intended for development and testing in an isolated environment and can host larger data sets than a Developer sandbox. A Developer Pro sandbox includes a copy of your production org’s configuration (metadata). Use a Developer Pro sandbox to handle more development and quality assurance tasks and for integration testing or user training. Partial ...

A sitemap typically refers to a navigational structure or hierarchy that defines the layout and organization of pages within a Community (Experience Cloud). It provides a roadmap for users to navigate through the various pages and components of the application, ensuring a cohesive and intuitive user experience.  Make it easy for guest users to find new products in web searches. After you perform an incremental update to your sitemap, third-party search index crawlers can find newly added, publicly available products. New products are picked up in manual and scheduled incremental updates to your sitemap. Where : This feature is available in Lightning Experience, in Enterprise, Performance, Unlimited, and Developer editions. How : To manually update your store sitemap, make your store available to the public in Experience Builder | Settings | General, and select Public can access the site. Then open the SEO tab, and click Generate Sitemap. SEO ' sitemap.xml ' feature is not autom...

The two standard objects:  AuthSession ,  LoginGeo don’t store the login information of a Guest User. Using a VF Page  <apex:page showHeader="false" sidebar="false" controller="userIPAddressController"  action="{!getUserIPAddress}">  <script>     setTimeout(function(){         var message = '{!ip}';         parent.postMessage(message, window.top.location.origin);               }, 3000);  </script>  <apex:form >      {!ip}  </apex:form> </apex:page> Controller public class userIPAddressController{     public string ip {get;set;}     public pageReference getUserIPAddress() {                  // True-Client-IP has the value when the request is coming via the caching integration.         ip = ApexPages.currentPage().getHeaders()...

For a variety of purposes, including displaying items, sending texts, and other security-related tasks, tracing IP addresses is necessary. Logged in User IP Address Getting IP Address for logged in user is relatively simple as Salesforce stores this information in two standard objects:  AuthSession ,  LoginGeo . List<AuthSession> auth = [SELECT Id , IsCurrent, SessionType, CreatedDate, LoginGeoId, NumSecondsValid FROM AuthSession WHERE UsersId =: Userinfo.getUserID()]; if(auth.isEmpty() == false && auth[0].IsCurrent ){ system.debug('yes, it is current user session'); }else{ system.debug('No, it is not current user session'); } List<LoginGeo> lg = [SELECT Id,City, Country, PostalCode, Subdivision, Latitude, Longitude,LoginTime FROM LoginGeo WHERE Id =: auth[0].LoginGeoId]; Alternatively, you can use  Auth.SessionManagement  Class as well as below: Auth.SessionManagement.getCurrentSession().get('LoginGeoId'); getCurrentSession() re...