• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Platform App Builder

Platform App Builder

Checklist progress

0/316Learned

Platform App Builder

Study Checklist

  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Architect

Checklist progress

0/316Learned

  • Declarative business logic tools
  • Apex use cases beyond Flow Builder
  • Formula field boundaries versus record-updating automation
  • Record-triggered Flow versus Apex triggers
  • Schedule-triggered Flow versus Batch Apex
  • Declarative callouts versus Apex HTTP callouts
  • Lightning App Builder versus custom programmatic UI
  • Invocable Apex actions in Flow Builder
  • AgentExchange as the Salesforce marketplace
  • AgentExchange solution types
  • Solution listings versus consultant listings
  • Agentforce solutions on AgentExchange
  • Marketplace versus custom build for a capability gap
  • Evaluating AgentExchange listings
  • Sandbox testing before production install
  • AgentExchange install permissions and user access
  • AgentExchange security review for public listings
  • Object, field, and record access layers
  • Profiles versus permission sets
  • Standard profiles and Minimum Access clones
  • Settings restricted to profiles versus permission set grants
  • Object-level Create Read Edit Delete permissions
  • View All and Modify All object permissions
  • View All Data versus View All object permission
  • Field-level security versus page layouts
  • Permission set groups for persona access
  • Muting permissions in a permission set group
  • Profile login hour restrictions
  • Login IP ranges versus trusted IPs
  • Restriction rules versus sharing rules
  • User access policies for granting and revoking access
  • Organization-wide default access levels
  • When to use each organization-wide default
  • Internal versus external organization-wide defaults
  • Controlled by Parent organization-wide default
  • Role hierarchy record access
  • Grant Access Using Hierarchies for custom objects
  • Sharing rules as exceptions to organization-wide defaults
  • Owner-based versus criteria-based sharing rules
  • Public groups as sharing rule targets
  • Manual sharing of individual records
  • Account, opportunity, and case teams
  • Queues for shared record ownership
  • Implicit sharing between accounts and children
  • Record-level sharing control interaction
  • Reports versus report types versus dashboards
  • Standard versus custom report types
  • Custom report type object relationships
  • Custom report type field layout
  • Custom report type availability status
  • Tabular, summary, and matrix report formats
  • Joined report blocks and common fields
  • Report filters and filter logic
  • Cross filters on related objects
  • Bucket columns in the report builder
  • Row-level formula columns
  • Summary formula columns on grouped reports
  • Conditional formatting on grouped reports
  • Report charts versus dashboard widgets
  • Dashboard component types
  • Tabular reports as dashboard sources
  • Dashboard running user and dynamic dashboards
  • Dashboard filters for interactive views
  • Report and dashboard folder sharing
  • Report and dashboard subscriptions
  • Historical trending reports

Given a scenario, determine the appropriate data model.

0/14

  • Standard versus custom objects
  • Standard object selection for business entities
  • Custom object versus custom field
  • Picklist versus related object
  • Master-detail versus lookup for parent-child models
  • Junction objects for many-to-many relationships
  • Self-relationships on the same object
  • Hierarchical relationships on the User object
  • Schema Builder for data model design
  • Record types for layouts, picklists, and processes
  • Record type assignment and the Master record type
  • Sales, support, lead, and solution processes
  • Custom metadata types versus custom objects
  • Hierarchy versus list custom settings

Given a scenario, explain the capabilities of the various relationship types and the implications of each on record access, user interface, and reporting.

0/14

  • Master-detail cascade delete and restore
  • Lookup parent-delete field behaviors
  • Master-detail child reparenting
  • Record access for master-detail versus lookup children
  • Master-detail Sharing Setting on the relationship field
  • Related lists and object tabs for relationships
  • Standard report types by relationship type
  • Custom report types for related objects
  • Junction object primary master effects
  • Multilevel master-detail relationships
  • Lookup filters on relationship fields
  • Converting lookup and master-detail relationships
  • External lookup versus indirect lookup
  • Contacts to Multiple Accounts

Given a scenario, determine the considerations when selecting or changing a field data type.

0/19

Text and long-text field types

Learn this concept
Unseen

Number, currency, and percent fields

Learn this concept
Unseen

Date, Date/Time, and Time fields

Learn this concept
Unseen

Checkbox versus Yes/No picklist

Learn this concept
Unseen

Email, Phone, and URL field types

Learn this concept
Unseen

Picklist versus multi-select picklist

Learn this concept
Unseen

Restricted versus unrestricted picklists

Learn this concept
Unseen

Global picklist value sets

Learn this concept
Unseen

Dependent picklists and controlling fields

Learn this concept
Unseen

Record types and picklist values

Learn this concept
Unseen

Auto-Number field configuration

Learn this concept
Unseen

External ID and unique field types

Learn this concept
Unseen

Geolocation custom fields

Learn this concept
Unseen

Formula versus stored field types

Learn this concept
Unseen

Classic encrypted text fields

Learn this concept
Unseen

Universally required versus page-layout required fields

Learn this concept
Unseen

Field history tracking

Learn this concept
Unseen

Custom field type conversion data loss

Learn this concept
Unseen

Blocked custom field type changes

Learn this concept
Unseen

Given a scenario, determine the options and considerations when importing and exporting data, including the capabilities of external data sources.

0/9

  • Data Import Wizard versus Data Loader
  • Data Import Wizard matching and add-or-update actions
  • External ID matching on upsert
  • Import considerations for validation rules and field types
  • Data Loader delete versus hard delete
  • Data Export Service versus Data Loader export
  • Salesforce Connect versus importing a data copy
  • External object capabilities
  • Salesforce Connect adapter types
  • When to use a formula field
  • Formula field return types
  • Formula operators and functions by context
  • Conditional logic in formula fields
  • Text functions in formula fields
  • Date and time calculations in formula fields
  • Picklist values in formula fields
  • Blank and null handling in formula fields
  • Formula merge fields and global variables
  • Cross-object formula spanning and syntax
  • Formula field visibility of referenced data
  • Display formulas for images and links
  • Formula field reference restrictions
  • Formula field search and attribute restrictions
  • Formula field size and compile limits
  • Roll-up summary relationship rules
  • Supported roll-up aggregate functions
  • Roll-up summary filter criteria
  • Roll-up summaries versus formula fields
  • Roll-up summary recalculation
  • Roll-up summary field limits
  • Validation rules and roll-up summaries
  • Roll-up summary sharing and field access
  • Advanced currency management with opportunity roll-ups
  • Validation rule error-condition formulas
  • Validation error location and multiple-rule display
  • Validation rule execution timing
  • Validation rules versus field-level and layout required
  • Conditionally required fields with validation rules
  • Format and range checks in validation formulas
  • Create versus edit functions in validation formulas
  • User, profile, and record type conditions in validation rules
  • Cross-object fields in validation rules
  • Validation formula field restrictions
  • Lookup filters versus validation rules
  • Validation rules versus automation field updates
  • Custom permission bypass for validation rules
  • VLOOKUP checks in validation rules
  • Flow Builder elements, connectors, and resources
  • Flow formula resources
  • Input and output variables
  • Get Records in Flow Builder
  • Create and delete records in Flow Builder
  • Update Records versus assigning $Record
  • Decision outcomes and the default outcome
  • Loops and bulk DML in Flow Builder
  • Collection Filter, Sort, and Transform
  • Screen components and input validation
  • Choice resources versus picklist and record choice sets
  • Record-triggered start events
  • Entry conditions and when-to-run on update
  • $Record and $Record__Prior
  • Scheduled path time source and offset
  • Asynchronous paths on record-triggered flows
  • Custom Error on record-triggered paths
  • Subflow referenced-flow rules
  • Send Email versus Email Alert
  • Flow run context and sharing
  • HTTP Callout from Flow Builder
  • When to use Flow Approval processes
  • Flow Approval processes versus classic approval processes
  • Autolaunched versus record-triggered Flow Approval processes
  • Starting an autolaunched Flow Approval process
  • Submit for Approval versus Request an Approval
  • Stages, steps, and Decision paths in Flow Approval processes
  • Approval steps versus background steps
  • Approval step assignment and unanimous approval
  • Completing Flow Approval work items
  • Delegated approvers for approval requests
  • Record locking in Flow Approval processes
  • Recall path in Flow Approval processes
  • Flow Approval processes limits and considerations
  • Screen Flow versus Autolaunched Flow (No Trigger)
  • Record-triggered Flow versus user-launched flows
  • Fast Field Updates versus Actions and Related Records
  • Schedule-triggered Flow versus scheduled paths
  • Platform Event-triggered Flow
  • Testing flows with the Flow Builder debugger
  • Automated flow tests in Flow Builder
  • Flow version activation and interview continuity
  • Flow version deletion constraints
  • Fault paths for flow error handling
  • Unhandled flow fault notifications
  • Transaction rollback after a flow error
  • Governor-limit failures versus fault paths
  • Paused and failed flow interviews
  • Flow Trigger Explorer for record-triggered flows
  • Recursive record-triggered flow loops
  • Agentforce capabilities for autonomous process automation
  • Employee versus Service agent use cases
  • Agentforce topics, actions, and reasoning
  • Standard versus custom Agentforce actions
  • Reference action types for Agentforce custom actions
  • Invoking Agentforce from Flow
  • Agentforce versus Flow for process automation
  • Agent execution context and data access
  • Setup with Agentforce for administrative processes
  • Lightning app branding and navigation
  • Standard versus console app navigation
  • Custom tab types
  • Tab visibility in apps
  • Page layout contents and field behavior
  • Page layout assignment by profile and record type
  • Related list customization on page layouts
  • Compact layouts for record highlights
  • Record types for layouts and picklists
  • Lightning App Builder versus the page layout editor
  • Lightning App Builder page types
  • Lightning page activation and assignment
  • Dynamic Forms versus page-layout record detail
  • Component visibility rules on Lightning pages
  • Path on Lightning record pages
  • List view customization
  • Kanban views for list views
  • Search layouts for results and lookups
  • Lightning themes and branding
  • Org-wide User Interface settings
  • Object-specific versus global actions
  • Quick action types and use cases
  • Action layouts and predefined field values
  • Custom button and link display types
  • Custom button and link content sources
  • Quick actions versus custom buttons
  • Lightning and mobile action placement on layouts
  • Lightning Experience action locations by type
  • Dynamic Actions and visibility filters
  • Standard, custom, and third-party Lightning components
  • Lightning page templates, regions, and form factors
  • Standard Lightning page components
  • Highlights Panel versus Dynamic Highlights Panel
  • Related list Lightning components
  • Flow component on Lightning pages
  • Visualforce Page component on Lightning pages
  • Utility bar Lightning components
  • Custom Lightning components in Lightning App Builder
  • When a custom Lightning component is required
  • Aura versus Lightning Web Components coexistence
  • Exposing custom Lightning components to App Builder
  • Design attributes on custom Lightning components
  • Lightning component overrides for standard actions
  • Lightning web component record actions
  • Custom Lightning components on Flow screens
  • Visualforce pages in Lightning Experience
  • Mobile navigation bar and menu
  • Page layout optimization for the Salesforce Mobile App
  • Salesforce mobile action bar
  • Global publisher layouts
  • Quick actions and record type availability
  • Productivity actions in the Salesforce mobile app
  • Mobile smart action bundles
  • Application lifecycle environment path
  • When to use a sandbox versus production
  • Sandbox type selection by business requirement
  • Sandbox data copy and storage allocations
  • Sandbox refresh intervals and effects
  • Sandbox templates
  • Sandbox cloning versus creating from production
  • Sandbox org identity and user considerations
  • Overlapping customizations across Developer sandboxes
  • DevOps Center for application lifecycle
  • Scratch orgs versus sandboxes
  • Outbound versus inbound change sets
  • Deployment connections and inbound authorization
  • Affiliated-org limits for change sets
  • User permissions for change sets
  • Metadata versus data in change sets
  • Components available in change sets
  • Custom metadata type records in change sets
  • Profile settings versus permission sets in change sets
  • Delete and rename limits for change sets
  • Dependent components for change set deploy
  • Validate a change set before deploy
  • All-or-nothing change set transaction
  • Apex tests on production change set deploy
  • Flow activation after change set deploy
  • Closed outbound change sets and cloning
  • When inbound change sets become unavailable
  • When to use managed versus unmanaged packages
  • Namespace prefixes on packaged component API names
  • Subscriber customization of packaged components
  • Managed package upgrades and versioning
  • Uninstall behavior for installed packages
  • Unmanaged packages versus change sets for metadata migration
  • AppExchange package install in a sandbox
  • Package installation user access options
  • Packaged components and org edition limits
  • Unlocked packages versus managed packages for internal apps
  • AppExchange security review for public managed packages
  • Change sets versus packages versus Metadata API
  • Metadata versus data in a deployment plan
  • Deployment dependency and migration order
  • Destination org feature enablement before deploy
  • Pre- and post-deployment run list
  • Rollback and backup after a production deployment

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.

Go to Discord

Universally required versus page-layout required fields

Explainer

Learn More

Practice Question

Keep going

Next conceptField history tracking

Checklist progress

0/316 (0%)

0 of 316 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.

Go to Discord

Explainer

Universally required fields are custom fields that must have a value any time a record is saved, in Salesforce, through the API, or by automated processes, so the rule is not limited to one screen. Page-layout required fields only force a value on that layout's detail and edit pages. Use universally required when the field must always be populated; use page-layout required when the constraint should apply only to a specific presentation.

Core information
  • A universally required field is a custom field set to Required in the field definition in Object Manager. It must have a value whenever a record is saved within Salesforce, the Lightning Platform API, Connect Offline, Salesforce for Outlook, the Self-Service portal, or automated processes such as Web-to-Lead and Web-to-Case.
More details and nuances
  • To automatically add a field to all page layouts and make it visible and required everywhere regardless of field-level security, make it a universally required field.