Platform App Builder flashcards
Platform App Builder · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Custom object API suffix
- Custom objects and custom fields use the __c suffix in their API names; standard objects do not, and their API names cannot be changed.
- Profile versus permission set
- A profile defines baseline object and field permissions, app visibility, and tab settings; a permission set grants additional permissions without changing the user's profile.
- Organization-wide defaults
- Organization-wide defaults set the baseline record access for each object, such as private, public read-only, or public read-write, before sharing rules widen access.
- Role hierarchy effect
- The role hierarchy lets users above a role see records owned by users below them when organization-wide defaults are private or public read-only.
- Lightning app definition
- A Lightning app is a collection of tabs and navigation items that gives users access to objects, pages, and tools; users need the app assigned through profiles or permission sets.
- Record type purpose
- Record types let one object support different business processes by pairing picklist value sets with page layouts; they are assigned through profiles.
- Setup Audit Trail
- The Setup Audit Trail records configuration changes in the org, including who changed what and when, and retains the last 180 days of entries.
- Master-detail relationship
- A master-detail relationship tightly couples a child record to a parent; the child cannot exist without the parent, inherits sharing, supports roll-up summaries, and is deleted with the parent.
- Lookup relationship
- A lookup relationship loosely links two objects; the child can exist without the parent, does not inherit parent sharing, and does not support roll-up summary fields.
- External ID field
- An external ID is a custom field that stores a unique identifier from another system; it enables upsert operations and can be used to relate records during imports.
- Validation rule logic
- A validation rule is a formula that blocks a save when it returns true; it fires before the record is committed and can display a custom error message.
- Dependent picklist requirement
- A dependent picklist shows values based on a controlling picklist; the controlling field must be a picklist or checkbox, and a multi-select picklist cannot control another field.
- Data Import Wizard limit
- The Data Import Wizard can load up to 50,000 records for supported objects and includes duplicate matching; Data Loader is used for larger volumes.
- Field-level security
- Field-level security controls whether a user can view or edit a field; page layouts only control whether the field appears on a page.
- Before-save flow
- A before-save flow runs before the record is saved and can update fields on the same record without causing an additional save transaction.
- After-save flow
- An after-save flow runs after the record is committed and can create or update related records using separate database operations.
- Approval process
- An approval process defines entry criteria, approval steps, approvers, and final approval or rejection actions; it routes records for formal approval.
- Time-dependent workflow
- A time-dependent workflow action fires at a specified time after a workflow rule's criteria are met, such as sending an email three days after creation.
- Scheduled flow
- A scheduled flow runs at a configured time and can process a batch of records; it is used for recurring automation without a user interface.
- Roll-up summary field
- A roll-up summary field on a master record calculates count, sum, min, or max from related detail records and requires a master-detail relationship.
- Lightning App Builder
- Lightning App Builder builds Lightning pages for apps, home pages, and record pages using standard and custom components; pages are assigned by app, record type, or profile.
- Page layout scope
- A page layout controls field placement, related lists, buttons, and sections on a record page; it does not grant or restrict field-level access.
- Compact layout purpose
- A compact layout selects the key fields shown in record highlights, related-list hover cards, and mobile record cards for an object.
- Global action
- A global action appears in the global header and creates a record without starting from an existing record; object-specific actions appear on record pages.
- Dynamic forms
- Dynamic forms on Lightning record pages show or hide fields and sections based on record attributes, reducing the need for multiple page layouts.
- Utility bar
- The utility bar provides persistent tools at the bottom of Lightning Experience, such as notes, history, or a flow, and is configured per Lightning app.
- Change set
- A change set is a bundle of metadata sent from a source org to a connected target org; it moves configuration, not record data.
- Outbound change set
- An outbound change set is created in the source org, uploaded to the target org, and then deployed inbound on the target.
- Unmanaged package
- An unmanaged package is a one-time collection of metadata that can be installed in another org but cannot be upgraded like a managed package.
- Managed package
- A managed package has a namespace, can be listed on AppExchange, and supports versioned upgrades while protecting its code and metadata.
- Scratch org
- A scratch org is a disposable, source-driven Salesforce environment configured from a definition file and typically used with Salesforce CLI and source tracking.
- Apex test coverage
- Production deployments require at least 75 percent Apex code coverage across the org, and every trigger must have some test coverage.