Salesforce Admin Exam Guide

 In Salesforce, besides Production and various Sandbox Environments , there are a few additional environments and tools designed to support specific use cases, such as development, testing, integration, and staging. Here’s a more comprehensive list of all environments available in Salesforce: 1. Production Environment Purpose: Live environment for real business operations with actual data. Audience: End-users and live business workflows. Customization: Only changes that are fully tested and approved in the sandbox should be deployed here. 2. Sandbox Environments Salesforce offers different types of sandbox environments for development, testing, and staging: Developer Sandbox For coding and unit testing. Contains only metadata (no real data) from production. Small data storage limits (~200MB). Developer Pro Sandbox Similar to Developer Sandbox but with larger storage (~1GB). Suitable for larger testing datasets and development projects. Partial Copy Sandbox Includes metadata an...

  Global Actions Actions not tied to any specific object. Accessible across Salesforce (e.g., log a call, create a task, display a Visualforce Page ,  , Display a Custom Canvas ). Best for universal tasks. Object-Specific Actions Actions tied to a specific object (e.g., create a case for an Account). Context-aware and available on object record pages. Best for object-related workflows. Action Layout Editor Tool to customize the layout of Global and Object-Specific Actions. Lets you add, remove, or rearrange fields for better usability. Key Difference: Global Actions work everywhere, while Object-Specific Actions are tied to specific objects. The Action Layout Editor customizes how fields appear in these actions. where to define who will be able to see a Global or object action ChatGPTThe visibility of Global Actions and Object-Specific Actions in Salesforce depends on page layouts , profiles , and permissions 1. For Global Actions Defined In: Global Publisher Layouts : Dete...

  difference between Lightning App Builder and App Manager  ChatGThe Lightning App Builder and the App Manager 1. Lightning App Builder The Lightning App Builder is primarily a visual drag-and-drop tool used for designing and customizing the user interface (UI) of Salesforce apps, pages, and components. Key Features: Allows you to create custom pages for Lightning Experience and Salesforce Mobile App. Supports building different types of pages: App Pages : Custom pages for a Lightning app. Home Pages : Custom home pages for specific profiles or the org as a whole. Record Pages : Custom layouts for record details (e.g., Accounts, Opportunities). Provides a drag-and-drop interface for adding Lightning components, standard components, or custom components. Focuses on enhancing the user experience (UX) with page layouts, visibility rules, and responsive design . Does not manage app-level settings like branding, tabs, or permissions. Use Case: To create a custom record page ...

  APP BUILDER ----> DYNAMIC INTERACTIONS is like IPC between Lightning Web Component TO  Lightning Web Component / Aura Component ALSO  While creating the Pages from App Builder or App from App Manager you need to define the FORM FACTOR (which states whether the app is just for DESKTOP or also for MOBILE APPs) + A tab for a page is automatically created when that page is Activated  ----------

  Salesforce Admin Exam - Quick Revision Guide for Configuration and Setup 1. Company Information Company Settings: Default Locale, Time Zone, and Currency affect how data is displayed. Fiscal Year: Standard fiscal years follow the Gregorian calendar; custom fiscal years allow non-standard start dates. Business Hours: Critical for support processes like case escalation and SLA tracking. Licenses: Always monitor the allocation and utilization of licenses to avoid service interruptions. 2. User Setup User Roles and Profiles: Roles determine record-level visibility in role hierarchies; Profiles define permissions for objects, tabs, and apps. Permission Sets: Layer additional permissions on top of profiles to ensure flexibility without creating new profiles. Login IP Ranges and Hours: Use to enhance security by limiting user access based on location and timing. 3. Security and Access Organization-Wide Defaults (OWD): Dictate the default visibility of records across the org. Shar...