Platform App Builder cheat sheet

Custom objects use the __c suffix and custom fields use __c in API names; standard object API names cannot be changed.

Profiles set baseline object permissions, field permissions, app visibility, and tab settings; permission sets add permissions without altering the profile.

Organization-wide defaults set baseline record access per object; role hierarchy and sharing rules can widen access beyond that baseline.

A Lightning app is a set of tabs and navigation items; users see an app only when it is assigned through their profile or a permission set.

Record types pair picklist values with page layouts to support different business processes on the same object; profiles assign record types.

Setup Audit Trail records configuration changes and retains the most recent 180 days of entries.

Delegated administrators can manage specified users, objects, and settings without receiving full system administrator privileges.

The Salesforce mobile app uses compact layouts and mobile cards; Lightning Experience pages and Classic pages can differ per app.

Master-detail relationships make the child dependent on the parent, inherit sharing, support roll-up summaries, and cascade delete to the child.

Lookup relationships allow the child to exist without the parent and do not inherit parent sharing or support roll-up summary fields.

External ID fields store unique identifiers from other systems and enable upsert operations; they can also link records during data import.

Formula fields calculate at display time and are not stored; roll-up summary fields aggregate child records on a master-detail relationship.

Field-level security controls view and edit access; page layouts only control whether a field is placed on a page.

Validation rules are formulas that prevent a save when they return true and can show a custom error message.

Data Import Wizard supports up to 50,000 records per import for supported objects; Data Loader handles larger volumes and more objects.

Matching rules identify duplicate records, and duplicate rules decide whether to block or allow duplicates during create and edit.

Before-save flows update the triggering record without an extra save; after-save flows can create or update related records.

Workflow rules can trigger field updates, email alerts, tasks, outbound messages, and time-dependent actions, but cannot create records.

Process Builder can create records, update records, launch flows, submit for approval, and post to Chatter.

Approval processes define entry criteria, approval steps, approvers, and final approval or rejection actions.

Time-dependent workflow actions require a time trigger and fire after the rule criteria remain true for the specified delay.

Scheduled flows run at a set time and process records in batches; autolaunched flows have no user interface.

Roll-up summary fields recalculate when a child record is saved, and they require a master-detail relationship.

Bulk-safe automation uses collections rather than one-record DML inside loops to stay within governor limits.

Lightning App Builder creates app, home, and record pages from standard and custom components.

Record pages can be assigned by app, record type, and profile; the most specific assignment takes precedence.

Page layouts control fields, related lists, buttons, and sections but do not control field-level security.

Compact layouts choose fields for record highlights, related-list hover cards, and mobile record cards.

Object-specific actions appear on record pages; global actions appear in the global header and create records without a source record.

Dynamic forms show or hide fields and sections based on record attributes without creating multiple page layouts.

The utility bar provides persistent tools at the bottom of Lightning Experience and is configured per Lightning app.

Custom object tabs, Lightning component tabs, and Visualforce tabs expose different content types in an app's navigation.

Change sets move metadata between connected orgs and do not include record data.

An outbound change set is created in the source org, uploaded to the target org, and deployed inbound on the target.

Unmanaged packages are one-time installs; managed packages have a namespace and support versioned upgrades.

Scratch orgs are disposable environments configured from a definition file and used with source tracking and Salesforce CLI.

Production deployments require at least 75 percent Apex code coverage across the org.

Deployment test levels include NoTestRun, RunSpecifiedTests, RunLocalTests, and RunAllTestsInOrg.

Change sets cannot delete components; destructive changes require the Metadata API with a destructiveChanges.xml file.

Sandbox types include Developer, Developer Pro, Partial Copy, and Full; Partial Copy uses a data template to select records.