Salesforce in Action (Andy White)（Z-Library）

【One-Line Pitch】 A hands-on administrator’s field guide to running Salesforce day to day—configuring objects and pages, locking down access, automating routine work, and reporting on it—written for new or self-taught admins who need to operate a real org, not just pass a certification. 【Book Arc】 - **Opening (~0%–10%)**: Orients you inside the platform—Classic versus Lightning, the Setup menu, global versus setup search, profile settings, and collaboration features like activities and Chatter—so you can navigate before you configure. - **Early (~10%–30%)**: Moves into core administration: user and license management, page layouts in both Classic and Lightning, custom fields and useful field features (history tracking, validation, dependent picklists, encryption, geolocation), plus a first look at big objects and custom metadata. - **Early–Middle (~30%–40%)**: Introduces automation with Flows—building, activating, and testing flows, collecting related records, using Einstein-assisted flow prompts, and triggering flows from buttons or quick actions. - **Middle (~40%–50%)**: Dedicates serious space to the security model—org-wide defaults, role hierarchy, sharing rules and groups, permission-set caution, and compliance tools like MFA and Shield—framed as a layered “security pyramid” you configure and then test. - **Middle–Late (~50%–60%)**: Turns data into visibility: report types (tabular, summary, matrix, joined), buckets and conditional formatting, folders and sharing, and dashboards aimed at everyone from front-line users to senior management. - **Late (~60% onward)**: Closes with productivity and technical-debt topics—AppExchange and admin tools, org health checks, duplicate management, and pointers toward Apex and Lightning Web Components (excerpts do not cover the later chapters in detail). 【Key Takeaways】 - **Lightning is the default, but Classic knowledge still pays** (Opening): configuration is often easier in Classic and some Lightning areas still use classic interfaces, so admins should be comfortable switching per user. - **User access is a lifecycle, not a one-time setup** (Early): creating users correctly (license, locale, permission sets, password notification), adding them in bulk via sandbox or developer org practice, and deactivating versus freezing to reclaim licenses. - **Field-level features protect data quality** (Early): history tracking, validation rules, dependent picklists, and encryption are configured per field, so they belong in your object-design routine rather than as afterthoughts. - **Flows let Salesforce do the routine work** (Early–Middle): build, test, and activate flows; prefer quick actions over custom buttons for a smoother in-page experience; Einstein prompts can draft flows for you. - **Security is layered and must be tested** (Middle): org-wide defaults set the baseline, the role hierarchy grants upward access, and sharing rules are exceptions—keep them few, audit them, and avoid broad permissions like View All Data or Modify All Data. - **Report choice follows the question** (Middle): tabular for lists, summary for grouped totals, matrix for two dimensions, joined for cross-object comparisons; buckets and conditional formatting sharpen the message. - **Dashboards are a communication tool** (Middle): organize reports into shared folders first, then assemble dashboards for the audience—including executive-facing views. - **Check for technical debt before you build** (Late): tools like Org Check (and more advanced scanners) reveal bad configuration in inherited orgs; AppExchange tools handle cross-object deduplication beyond native duplicate rules. 【Reading Tips】 - Deep-read the security chapters (5 and 7) and the Flows chapter—these are where most real-world admin mistakes and most of the book’s practical value sit. - Skim the click-by-click figure walkthroughs on a first pass; return to them as lab exercises in a developer org or sandbox rather than reading passively. - Treat the end-of-chapter multiple-choice questions as self-checks; they signal which concepts (e.g., “Controlled by Parent” object security) the author considers exam- and job-critical. - Keep the tools chapter as a reference shelf—note Org Check, deduplication options, and the Graphics Pack, then look them up when a specific problem appears. - If you inherit an old org, read the health-check and sharing-rule audit material before changing anything in production. 【Coverage Limits】 These excerpts concentrate on the opening through middle chapters (setup, users, layouts, fields, flows, security, reporting); later material on Apex, Lightning Web Components, and advanced tooling is only gestured at, so this guide cannot assess those chapters in depth.