Salesforce Developer flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

18-character record ID

Case-insensitive version of a 15-character Salesforce ID; the final three characters encode a checksum, making it safe for external systems that may change letter case.

Governor limits

Per-transaction caps enforced by the multi-tenant platform, such as 100 synchronous SOQL queries, 150 DML statements, and 10,000 milliseconds of synchronous CPU time.

Permission set

Additive permission container granting object, field, and system access without changing a user's profile; a single user may be assigned many permission sets.

Sandbox types

Developer, Developer Pro, Partial Copy, and Full Copy; Full Copy replicates all org data, while Partial Copy uses a template that samples records.

Salesforce APIs

REST and SOAP handle record operations, Bulk API 2.0 handles large data volumes, Metadata API handles configuration, and Streaming API pushes event notifications to clients.

Master-detail relationship

Relationship where the child cannot exist without a parent; deleting the parent cascades to children, and the parent gains roll-up summary fields over those children.

Junction object

Custom object with two master-detail relationships that models a many-to-many relationship and can hold its own fields plus roll-up summaries from either parent.

External ID field

Custom field flagged as an external ID that stores a unique key from another system, used by upsert to match records; an object allows up to 25 of them.

Roll-up summary field

Read-only field on a master-detail parent that aggregates related child records using COUNT, SUM, MIN, or MAX, optionally filtered by criteria conditions.

Relationship query syntax

Child-to-parent queries use dot notation such as Account.Name; parent-to-child queries use a subquery on the child relationship name, such as SELECT Id, (SELECT Id FROM Contacts) FROM Account.

Data Loader upsert

Operation that matches incoming rows against an external ID or Id field, updating matched records and inserting unmatched ones to avoid creating duplicates.

Order of execution

Save sequence: before triggers, system validation, after triggers, assignment and auto-response rules, workflow rules, flows and processes, roll-up summaries, then commit and post-commit work.

@future method

Asynchronous Apex method that must be static and return void, accepts only primitives or collections, and runs later in a separate transaction with higher governor limits.

Batch Apex

Asynchronous interface with start, execute, and finish methods that processes records in chunks, defaults to 200 records per batch, and allows five concurrent jobs.

Trigger.new variable

Context variable holding the new versions of records in insert and update triggers; it is unavailable in after delete, while Trigger.old is unavailable in after insert.

Bulkification

Design pattern that gathers records into collections and performs one SOQL query and one DML call instead of querying inside a loop, keeping code under governor limits.

Queueable Apex

Asynchronous job that accepts sObject and non-primitive parameters, returns a job ID for monitoring, and can enqueue a chained child job from its execute method.

@wire decorator

Lightning Web Components decorator that binds a property or function to a reactive source such as a cacheable Apex method or a Lightning Data Service adapter.

lightning-record-form

Base component that renders create, view, or edit forms for a record, automatically honoring page layout, field-level security, and standard save behavior.

NavigationMixin

Lightning Web Components mixin that adds a navigate method for building PageReference objects and moving users to records, list views, or custom app pages.

@AuraEnabled annotation

Marks an Apex method or property as callable from Lightning components; the method must be static and declared public or global, with cacheable=true for wired calls.

SLDS

Salesforce Lightning Design System: a CSS framework of classes and design tokens that makes custom components match standard Lightning styling and behavior.

Test.startTest and stopTest

Statement pair that isolates tested logic so it runs with fresh governor limits; stopTest also forces asynchronous work such as future, queueable, and batch jobs to complete.

Code coverage requirement

At least 75 percent of Apex lines must be covered by tests, and every trigger must be covered, before code can be deployed to a production org.

@testSetup method

Annotated method that runs once before all tests in a class to create shared records; the data is visible to every test and rolled back afterward.

Test.setMock

Method that registers a mock implementation such as HttpCalloutMock so test code can simulate an external callout response without making a real request.

SeeAllData parameter

Test annotation option that grants test code access to pre-existing org records; it defaults to false so tests see only data created inside the test transaction.

Debug log levels

Severity settings ranging from NONE through ERROR, WARN, INFO, DEBUG, FINE, FINER, and FINEST, configured per category in a trace flag to control log detail.

Outbound change set

Deployment container of metadata components sent from one org to another, typically sandbox to production; it cannot delete components already present in the target.

Validation-only deployment

Deployment mode that runs all tests and dependency checks against the target org without committing any changes, used to verify readiness before a real deployment.

Execute Anonymous

Developer Console or CLI capability that runs an ad hoc block of Apex immediately and produces its own debug log and compile or runtime errors.

Checkpoint

Developer Console debugger feature that captures heap state at a chosen line while replaying a debug log, letting you inspect variables without adding debug statements.