SidebarSite navigation.

Cert++

Practice
Certle
Review
Tracks
Study Guide

More

About
Articles
Community
Support
Changes
Legal

Pipeline forecast submissions

Key Takeaway

A forecast submission saves a snapshot that managers compare with the live forecast and quota. Submissions work only on active forecast types that don't include product families or other forecast groups.

The live forecast can keep changing during a forecast period, so managers need a fixed number to compare it with. Pipeline forecast submissions give them that number. A sales rep or manager submits a best estimate, and Salesforce saves it as a snapshot. Managers later check the live forecast against that snapshot and against quota.

What a forecast submission is

Forecast submission: A sales rep's or manager's best estimate of the revenue or quantities they expect to close during the forecast period.

Submissions are typically required weekly. When a user submits, Salesforce takes a snapshot of the forecast at that moment. The live forecast can keep changing afterward. The submission still records what the forecast was at the time it was submitted.

Platform Administrator II Study Guide

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
Marketing Cloud Account Engagement Specialist
Marketing Cloud Next 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 Communications AP
Agentforce Consumer Goods AP
Agentforce Financial Services AP
Agentforce Health AP
Agentforce Manufacturing AP
Public Sector Solutions AP
Revenue Cloud Consultant
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 Next Consultant
Tableau Architect
Slack Administrator
Slack Consultant
Slack Developer

Checklist progressProgress

0/290Learned

Checklist progressProgress

0/290Learned

Organization-wide defaults versus role hierarchy access
Field-level security versus page layout visibility
Grant Access Using Hierarchies on custom objects
Controlled by Parent access on child records
Sharing rules as additive record access
Owner-based versus criteria-based sharing rules
Manual sharing behavior on ownership transfer
Implicit sharing on parent-child records
Account team access versus consolidated record access
Report and dashboard folder sharing
Email template folder access
Territory Management default record access
Territory membership versus role hierarchy access
Object permissions versus record-level sharing access
Object-level View All and Modify All versus View All Data
Exceptions to role hierarchy-based record access
Queue ownership and access to queued records
Sales Territories versus account teams for account access
User sharing to control which users can see each other
Restriction rules for narrowing record visibility
Standard versus custom profile editability
Additive permission set grants versus profile baseline
When to use a permission set instead of a new profile
Profile-only settings versus permission set capabilities
Permission set groups for job functions
Session-based permission sets for temporary access
When to use delegated administration
Delegated administration capabilities and limits
User licenses, permission set licenses, and standard permission sets
Organization versus profile password policies
Organization versus profile login hours
Trusted IP ranges versus profile login IP ranges
Identity verification and device activation
Multi-factor authentication requirements
Session security and high-assurance sessions
My Domain login policies
Freezing versus deactivating a user
SAML single sign-on as service provider
Delegated authentication versus SAML
Social sign-on versus single sign-on
Login flows after authentication
Certificate-based user authentication
Password-free login options for internal users
Restoring access after a lost MFA verification method
Controlling which users can authorize connected apps
Business accounts versus Person accounts
Person account enablement prerequisites
Business account to Person account conversion
Contacts to Multiple Accounts versus a single parent account
Contacts to Multiple Accounts setup
Direct versus indirect account-contact relationships
Contacts to Multiple Accounts considerations
Sharing implications of Person accounts and related contacts
Contacts to Multiple Accounts versus Account Contact Roles versus junction objects
Reporting on indirect account-contact relationships
Person account field security, history and formula behaviour
Relating person accounts to businesses and other people

Custom objects versus fields on standard objects
Master-detail versus lookup for object extension
Lookup field deletion behaviors
Converting master-detail relationships to lookups
Multilevel master-detail and subdetail records
Junction objects for many-to-many models
Junction object primary master and sharing
Related lists for related object data
Record types for picklists and business processes
Record type profile availability and defaults
Schema Builder for data model changes
Object Creator for extending objects
Reparenting detail records in a master-detail relationship
Page layout assignment by profile and record type
Standard report types created by object relationships
Lightning App Manager branding and navigation
Lightning page types in App Builder
Lightning App Builder versus page layout editor
Standard Lightning page components
Lightning page activation and assignment
Dynamic Forms versus Record Detail
Dynamic Forms migration and limitations
Dynamic related lists in Lightning App Builder
Lightning console apps versus standard apps
Lightning pages for console apps
Lightning page Analyze button
Utility bar for persistent productivity tools
Component visibility rules on Lightning pages
Highlights Panel fields: compact layouts versus Dynamic Highlights Panel
Record page buttons and actions: page layout versus Dynamic Actions
Conditional field formatting in Lightning App Builder
Dynamic Forms versus screen flows for record entry forms

Setup Audit Trail for configuration change history
Debug logs for transaction and automation troubleshooting
Login History versus Identity Verification History
Transaction Security policies for real-time enforcement
Field data classification for compliance policies
Field Audit Trail for compliance retention
Shield Platform Encryption for data at rest
Deterministic versus probabilistic encryption
Platform Encryption key management
Sandbox data masking and anonymization
Data Mask masking types
Sandbox seeding versus full-copy masking
Shield Platform Encryption versus Classic Encryption
Security Health Check review and remediation
Reviewing effective user access
Release Updates affecting system access
Troubleshooting unexpected access from security settings
Reviewing guest user object, record, and field exposure

Describe the features of Salesforce which enable Sales users to conduct the sale process, including products, price books, schedules, orders, and quotes

0/14

Products versus price books in the sales catalog
Standard Price Book versus custom price books
Opportunity price book and opportunity products
Quantity versus revenue product schedules
Quotes created from opportunities
Quote sync with opportunity products
Order Settings and enabling orders
Creating orders from quotes and opportunities
Activated orders versus reduction orders
Removing products and price books
Price book sharing and product access for sales reps
Product pricing across multiple currencies
Default product schedules and schedules on opportunity products
Quote templates and quote PDF generation

Distinguish and understand the implications and capabilities of Forecasting and Territory Management

0/17

Pipeline forecast types

Learn this concept

Unseen

Forecast categories and stage mapping

Learn this concept

Unseen

Forecast quotas, periods, and fiscal year

Learn this concept

Unseen

Forecasts hierarchy for role-based rollups

Learn this concept

Unseen

Manager judgments in pipeline forecasts

Learn this concept

Unseen

Pipeline forecast submissions

Learn this concept

Unseen

Territory types and hierarchy

Learn this concept

Unseen

Territory model states

Learn this concept

Unseen

Account assignment rules versus manual assignment

Learn this concept

Unseen

Opportunity assignment to territories

Learn this concept

Unseen

Territory hierarchy versus role hierarchy

Learn this concept

Unseen

Territory administration permissions

Learn this concept

Unseen

Role-based versus territory-based forecasts

Learn this concept

Unseen

Territory forecast manager assignment

Learn this concept

Unseen

Sharing forecasts with users outside the forecast hierarchy

Learn this concept

Unseen

Territory forecast rollups for opportunities and holdout owners

Learn this concept

Unseen

Effect of territory hierarchy changes on territory forecast data

Learn this concept

Unseen

Explain how to create and maintain Salesforce Knowledge

0/13

Lightning Knowledge enablement
Lightning Knowledge user access
Knowledge article record types and page layouts
Data category groups and category hierarchy
Data category visibility
Knowledge article lifecycle
Knowledge article import
Lightning Knowledge sharing versus data category visibility
Article channel visibility for internal, customer, partner and public audiences
Approval processes and automation for Knowledge article publishing
Connecting Knowledge articles to cases
Knowledge article search tuning
Multilingual Knowledge base and article translation

Explain how to create and maintain service entitlements and entitlement processes

0/13

Entitlements versus entitlement processes versus milestones
Entitlement models for accounts, contacts, assets, and contracts
Entitlement Management enablement and lookup filters
Creating and maintaining entitlement records
Service contracts with related entitlements
Entitlement templates for products and assets
Entitlement process timelines, entry, and exit
Support milestones on entitlement processes
Milestone warning, violation, and success actions
Business hours in entitlement milestone timing
Case and work order movement through entitlement processes
Entitlement verification and Milestone Tracker on cases
Entitlement process versioning

Describe the features of Salesforce which enable interaction between support agents and customers

0/7

Agentforce Service Console workspace
Case Feed actions for agent-customer communication
Chat and Enhanced Chat for customer conversations
Omni-Channel routing and agent capacity
Experience Cloud sites for customer self-service
Site Case Feed for Experience Cloud members
Macros for repetitive service rep tasks

Given a scenario, understand the standard Salesforce suite of products that enable extending the core platform

0/6

Sales, Service, Marketing, and Commerce product fit
Salesforce edition and suite implications
Salesforce Foundations bundled capabilities
Experience Cloud as a platform extension
AppExchange solutions versus custom-built functionality
Declarative extension tools versus programmatic development

Data quality assessment and management plans
Field data types for data quality
Picklist administration for data quality
Validation rules versus formula fields for data quality
Matching rules versus duplicate rules
Merging duplicate records
Duplicate jobs and duplicate record sets
Record data enrichment tools
In-org archival and mass delete
Field-level required and unique attributes versus page layout settings
Validation rules for conditional enforcement, existing data and bypass
Matching rule criteria and fuzzy matching methods
Duplicate rule actions on create and edit
Duplicate rule scope: conditions, compared objects, and record-level security
Custom report types versus standard report types
Cross filters versus field filters
Report bucket fields versus formula fields
Custom summary formulas versus row-level formulas
Complex report and dashboard charting
Joined reports versus a single report type
When to use reporting snapshots
Dashboard filters versus cloned dashboards
Dynamic dashboards versus specified running user
Report groupings and date granularity in summary and matrix reports
Standard versus cross-block custom summary formulas in joined reports
Data backup versus data archive
Native data export versus third-party backup
Data warehouses and data lakes for off-platform data
Big objects versus Salesforce Connect versus Heroku Connect
Salesforce Connect adapter selection
External lookup versus indirect lookup relationships
Salesforce Connect feature support and limitations
Standard versus custom big objects
Big object capabilities and limitations
Third-party and middleware solutions for external data
Choosing an archiving approach for historical records
Data Import Wizard versus Data Loader
Data Import Wizard matching options
External ID matching for upserts
Relating imported records with External IDs
Formatting picklist, checkbox and date values in import files
Data Loader SOAP API versus Bulk API settings for large loads
Monitoring import jobs and reviewing import errors

Sandbox types and what they copy from production
Sandbox refresh implications
Sandbox copy versus change set deployment
Managed versus unmanaged packages
Change sets versus packages for unrelated orgs
Administrative versus development changes in production
Sandbox templates and Full sandbox copy options
Installing AppExchange packages and granting access
Deployment connections for change sets
Outbound versus inbound change sets
Permissions to upload and deploy change sets
Components available in change sets
Change set coverage for data and destructive changes
Dependent components in change sets
Profile settings and permission sets in change sets
Inbound change set validation versus deployment
Apex tests when deploying change sets
Adding components to an already uploaded change set
Org locking and deployment timing for change sets
Change set file limit and splitting large deployments
Flow activation state after change set deployment

Flow versus Process Builder and Workflow Rules
Flow versus Apex for business automation
Screen Flow versus record-triggered Flow
Record-triggered versus scheduled Flow
Formula fields versus Flow
Formula fields combined with Flow
Approval processes versus Flow for record review
Classic approval processes versus Flow approvals
Approval processes combined with Flow
Flow Orchestration versus Flow Builder
Migrate to Flow versus rebuilding automation
Validation rules versus flow custom errors for blocking saves
Roll-up summary fields versus flow for aggregating child records
Automation options for reaching external systems
Flow tests versus Flow Debugger
Flow fault paths and error emails
Monitoring flow and orchestration runs
Debug logs for declarative automation
Declarative automation that never ran
Delayed and waiting automation diagnosis
Process Builder and workflow failure diagnosis
Classic approval process troubleshooting
Flow approval process troubleshooting
Orchestration run details and debug modes
Debugging a flow as another user
Null values from Get Records causing flow failures
Flow Trigger Explorer for an object's record-triggered automation
Screen flow input, navigation, and Lightning page placement
Before-save versus after-save record-triggered flow capabilities
Flow create update and delete versus Workflow and Process Builder
Scheduled paths versus time-dependent workflow actions
Workflow rule remaining actions and limitations
Classic approval process steps actions and record locking
Flow approval processes versus Classic approval processes
Flow interview bulkification and transaction limits
Record-triggered flow trigger events and entry conditions
Flow actions for records, notifications, approvals, subflows and messaging
Flow running user and execution context by flow type
Run Asynchronously path for callouts and long-running work
System validation versus custom validation in the save order
Before-save versus after-save record-triggered Flow timing
Duplicate-rule block actions versus later automation
Assignment and auto-response rules versus later automation
Record-triggered Flow trigger order on one object
Process Builder and after-save flows in the late save window
Workflow field updates re-entering the save order
Roll-up summary parent updates re-entering the save order
Approval field updates re-entering the save order
After-commit emails and scheduled paths versus in-save automation

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Platform Administrator II studiers.

Pipeline forecast submissions

Key Takeaway

A forecast submission saves a snapshot that managers compare with the live forecast and quota. Submissions work only on active forecast types that don't include product families or other forecast groups.

The live forecast can keep changing during a forecast period, so managers need a fixed number to compare it with. Pipeline forecast submissions give them that number. A sales rep or manager submits a best estimate, and Salesforce saves it as a snapshot. Managers later check the live forecast against that snapshot and against quota.

What a forecast submission is

Forecast submission: A sales rep's or manager's best estimate of the revenue or quantities they expect to close during the forecast period.

Submissions are typically required weekly. When a user submits, Salesforce takes a snapshot of the forecast at that moment. The live forecast can keep changing afterward. The submission still records what the forecast was at the time it was submitted.