Section 3 SF Admin Deck Flashcards
Opportunity insights
Lasted news > up to date articles
Sales team wants to see opps sorted by stage
use kanban view
Sales teams handles hundreds of opps
Set up sales console opp view in multiple tabs
Sales team needs specific steps
Set up a path
Exec team needs to be notified of deals over $1
Set up big deal alert
Sales managers need to review open opps daily
Satup update reminders
What is true regarding web to lead
- data enter in web form is validated before its sent to SF 2. default lead creator for web gen leads can be specified
- standard and custom fields which need to be captured online can be selected
- assignment rules can be used
- if assign rules are NOT used or can’t locate the owner of the lead it will be assigned to the default lead creator 6. max # of leads per day 50-0 (using recapta) to reduce spam
Web to lead form - what happens when creating multiple response rule entries?
- only 1 auto resp can be active at one time
- there can be multiple response rule entries w/ diff criteria
- rules are processed in order
How to manually share a record?
- must be owner of record
- or above owner in hierarchy
- user must have full access aka administrator
- if you manually share a record you either get
a. read/write or b. read only
4 levels of control
ORG Sec Control –login hours and IP restrictions
Objects — permissions + perm sets
Object Record — OWD, Roles, Sharing Teams
Field on Record — field level security
Obj permissions are
Obj Access - create read edit delete
Profiles determine
which obj you can access and what actions they can take
Profile Tabs what if they are hidden?
If the are OFF they are hidden
Profiles house
tabs + apps
Org Sec Controls are….
PW Policies such as PW resets, login attemps
Identity confirmation
IP restrictions (profile level)
Network Settings
User Auth
SSo
2FA
How are relationships between obj represented on a record page in the user interface
Lookups
Related lists
Example: Search Accounts
Relationships between objects can be seen via related lists on record page
Org level security
Platform policies 2FA Trusted IP ranges Identity confirmation PW for all users
Chatter free access gives you
files shared to groups
mbr profiles for any groups they belong to
Reports
1 grouping = summary
2 groupings = matrix
Org settings controlled from profile
TAB
OBJ PERMISSIONS & FIELD USER
Record types & page layout assignments
Audit features
setup audit trail
login history
field history tracking
Who uses a debug log
Developers
Possibilities w/ workflow tasks
Tasks can be reused in multiple wf rules
Tasks can be tracked in activity history
When would an admin consider introducing a new record type for cases
when multiple page layouts are required
when diff picklist values are required
Customization for standard fields
- edit picklist values
- rename field labels- user interface
- remove non-required standard fields from page layout
Assignment rules
assign record ownership to indiv or queues based on criteria set in assignment rule
Rules can apply to
Leads or Cases
Standard fields that can be modified include
- field level sec
3, field label - help text
- picklist values
Standard validation allows you
to mark fields as universally required or unique
Custom validation
Create rules using own criteria to prevent users from saving invalid data
History tracking how to set up
Set history tracking > select fields to track > add page layout
Formula size for validations
4K max
Case mgmt
case escalation or accept case
Content mgmt
files to library
must add mbrs or no one will see your content
accounts
companies you do business with
contacts
people who work at an acct
leads
potential prospects
opportunities
qualified leads that you have converted
when you create a lead you….
create the account and contact with opportunity
opportunity workspace
gives you an at a glance insights and activity with a PATH
related cases
link parent case field
related case list > add to page layout
case feed
chatter feed, feed actions & comments in feed
case milestones
time dependent steps
SF knowledge
article creation autos suggestions send articles share URL knowledge search
knowlege component
allow users to access knowledge base in SF
agents can attach knowledge to cases
case collaboration
allows support agents to commun effectively
Support processes
define stages of cases
Key fields in case process
Case status
Case record import fields are
case # case type case reason case priority auto # values values > reason level of urgency
Import fields for case
include case origin
case status
internal comments > related items
Storage
Data (records)
File (crm content, articles etc)
Duplicate Rules
will not run if records are created w/ quick create or via commun self registration restored w/ un delete added w/ lightening sync manually merged
case activation rules
triggers
activation
rule entries
list views
let you see records important to you &
filters allow you to create customized lists
a pinned list view is the
default list view for that object
kanban view
organizes records into columns
reports
are a list of records that meet criteria you define
reports do more than lists
use complex filter logic
summarize and group data
preform calculations
create more sophisticated views of your data using dashboards
report types
standard > fields can’t be hidden from report type
AND
custom > primary obj + 3 related obj & fields need to be added to page layout > fields CAN be hidden
joined reports
multiple data types
5 blocks
2000 records
formula fields
are read only
can reference fields on same obj
can not reference currency codes long text or multisearch picklists
are not searchable or available for lead conversion or data export
page layout controls
fields sections related lists buttons that appear when users view or edit a record
