Lead, Contact, Account and Opportunity

Lead - People who you could potentially do business yet, but have not qualified
them. Unsure if they're going to buy from you. 22 - Company
Contact - Persons and business entity. Contacts work for Accounts. Possibly
has bought from you in the past.
Opportunity - Sales events related to an 1wrrfergh5 and one or more Contacts.

User Interface Features

https://help.salesforce.com/articleView?
id=customize_ui_settings.htm&type=0

Enhanced List
This is a list view where you can view list of records, List view is always on Tab
If offers additional functionality like Mass Edit, Navigation, Print view etc.
Click <Account>Tab -View button
1. Enable checkbox of all the records
2. Able to edit the records by double click the values for mass selection for edit
3. Sort the Columns by dragging
4. Create record from list view
5. Navigation
6. Print View

Inline Editing
Enable the values of page layout to edit by double click
Related List Hover Links
Enable to see the related list of the page layout (upper most) when hover Ex.
Case [2]
Enable Separate Loading of related list
Enable the separate loading of the related list ex.: Case [2..]
Enable Collapsible Sections
Collapsible sections let users collapse or expand sections on their record detail
pages by using the arrow icon next to the section heading. When enabling
collapsible sections, make sure your section headings are displayed for each
page layout. Sections remain expanded or collapsed until the user changes the
settings for that tab. If your org has enabled record types, Salesforce remembers
a different setting for each record type.
Show Quick Create
The Quick Create area on a tab home page allows users to create a record
quickly with minimal information. It displays by default on the tab home pages for
leads, accounts, contacts, forecasts, and opportunities. You can control whether
the Quick Create area is displayed on all relevant tab home pages.

Enable Separate Loading of Related Lists of External Objects

When enabled, related lists of external objects are loaded separately from
primary record details and related lists of standard and custom objects. External
objects behave similarly to custom objects, except that they map to data that’s
stored outside your Salesforce org. It can take awhile to retrieve data from an
external system, depending on the network latency and availability of the external
system. The Enable Separate Loading of Related Lists of External Objects option
is conveniently selected by default. The options for separately loading related
lists don’t apply to Visualforce pages, the Self-Service portal, or other pages for
which you can’t control the layout.

Enable the Salesforce Classic 2010 User Interface Theme

This option is not related to Lightning Experience. In this case, “Salesforce
Classic 2010 user interface theme” refers to the newer version of Salesforce
Classic, which is the interface that immediately precedes Lightning Experience.
Enabling this option turns on the updated Salesforce Classic look and feel.
Disabling it turns on the Salesforce Classic 2005 user interface theme —the
classic, classic Salesforce interface.

Enable Tab Bar Organizer

The Tab Bar Organizer arranges tabs in the main tab bar to prevent horizontal
scrolling of the page. The Organizer dynamically determines how many tabs can
display based on the width of the browser window. It puts tabs that extend
beyond the browser's viewable area into a drop-down list.

Enable Printable List Views

Printable list views let users easily print list views. If it’s enabled, users click the
Printable View link from any list view to open a new browser window, displaying
the list view in a print-ready format. The link is located next to the Help for this
Page link in the colored title bar of the page.
Enable Spell Checker on Tasks and Events
Available in all Editions. Enables the Check Spelling button when users create or
edit tasks or events. The spell checker analyzes the Description field on events
and the Comments field on tasks.

Enable Customization of Chatter User Profile Pages

Enables administrators to customize the tabs on the Chatter user profile page.
This includes adding custom tabs or removing default tabs. If disabled, users see
the Feed and Overview tabs only.

Enable Collapsible Sidebar

The collapsible sidebar enables users to show or hide the sidebar on every page
that normally includes it. When enabled, the collapsible sidebar is available to all
users in your org, but each user can choose how to display the sidebar. Users
can leave the sidebar visible, or they can collapse it and show it only when
needed by clicking the edge of the collapsed sidebar.

Show Custom Sidebar Components on All Pages

If you have custom home page layouts that include components in the sidebar,
this option makes the sidebar components available on all pages for all org
users. If you only want certain users to view sidebar components on all pages,
grant those users the “Show Custom Sidebar On All Pages” permission.

Enable Home Page Hover Links for Events

Enables hover links in the calendar section of the Home tab. On the Home tab,
users can hover the mouse over the subject of an event to see the details of the
event in an interactive overlay. This option is enabled by default. This checkbox
only controls the Home tab; hover links are always available on other calendar
views.
The fields available in the event detail and edit overlays are defined in a mini
page layout.

Enable Drag-and-Drop Editing on Calendar Views

Enables dragging of events on single-user, daily and weekly calendar views. This
allows users to reschedule events without leaving the page. This option is
enabled by default.
Enable Click-and-Create Events on Calendar Views
Let’s users create events on day and weekly calendar views by double-clicking a
specific time slot and entering event details in an interactive overlay. The fields
available in the event detail and edit overlays are defined in a mini page layout.
Recurring events and multi-person events aren’t supported for click-and-create
events on calendar views.
Enable Drag-and-Drop Scheduling on List Views
Lets users create events associated with records by dragging records from list
views to weekly calendar views and entering event details in an interactive
overlay. This option is disabled by default. The fields available in the event detail
and edit overlays are defined in a mini page layout.

Enable Hover Links for My Tasks List

Enables hover links for tasks in the My Tasks section of the Home tab and on the
calendar day view. This option is enabled by default. Users can hover the mouse
over the subject of a task to see the details of that task in an interactive overlay.
Your administrator can configure the information presented on these overlays.

Enable Enhanced Page Layout Editor

When enabled, the enhanced page layout editor replaces the current interface for
editing page layouts with a feature-rich WYSIWYG editor that includes several
improvements.
Enable Enhanced Profile List Views
Enables enhanced list views and inline editing on the profiles list page. With
inline editing in enhanced profile list views, you can manage multiple profiles at
once.
Enable Enhanced Profile User Interface
Enables the enhanced profile user interface, which allows you to easily navigate,
search, and modify settings for a single profile.
Enable Streaming API
Enables Streaming API, which lets you receive notifications for changes to data
that match a SOQL query that you define in a secure and scalable way. This field
is selected by default. If your Salesforce edition has API access and you don’t
see this checkbox, contact Salesforce.
Enable Dynamic Streaming Channel Creation
Enables dynamic channel creation when using the generic streaming feature of
Streaming API. When enabled, generic streaming channels get dynamically
created when clients subscribe, if the channel hasn’t already been created. This
field is selected by default. If your Salesforce edition has API access and you
don’t see the checkbox, contact Salesforce.
Enable Custom Object Truncate
Enables truncating custom objects, which permanently removes all the records
from a custom object while keeping the object and its metadata intact for future
use.
Enable Improved Setup User Interface
When disabled, users with Salesforce Classic access their personal settings from
the Setup menu. When enabled, users with Salesforce Classic access their
personal settings from the My Settings menu, accessible from the username
menu. The Setup link is also moved from the username menu to the Force.com
App Menu. If you change this setting, be sure to notify all users in your org.
Enable Advanced Setup Search (Beta)
When enabled, users can search for Setup pages, custom profiles, permission
sets, public groups, roles, and users from the sidebar in Setup. When disabled,
users can search for Setup pages only.

Activate Extended Mail Merge

Enables Extended Mail Merge for your org. When selected, the Mass Mail Merge
link is available in the Tools area on the home pages for accounts, contacts, and
leads. Also, single mail merges requested from the Activity History related list on
a record are performed using Extended Mail Merge functionality.
Extended Mail Merge is available by request only. Contact Salesforce Customer
Support if you are interested in this feature.
Always save Extended Mail Merge documents to the Documents tab
Mail merge documents generated using Extended Mail Merge are added to the
user's documents folder on the Documents tab, rather than delivered as email
attachments. Users are sent confirmation emails when their mail merge requests
have completed. Those emails include links for retrieving generated documents
from the Documents tab. These documents count against your org's storage
limits.

Service Portal/Salesforce Knowledge Vs. Public Solution

Service Port/Salesforce Knowledge
1. Users can write, edit, publish, and archive articles
2. Need to login
3. Categorizing articles
4. Reassign the article to an editor, translator, reviewer, or any other
collaborator
Public Solutions
1. Not required to login
2. Can only search the solutions/answers but cannot create cases

Delegated Administration
What is Delegated Administration?
Delegated administration allows named users to manage other users within
selected roles and profiles, as well as manage fields on selected custom objects.
Why use Delegated Administration?
If you assign user administration privileges using profiles or permission sets, that
user will gain the ability to administer most or all users and objects in your org.
Delegated administration allows you to specify which users (based on
role/profile) and custom objects (standard objects excluded) a delegated
administrator can manage.
https://certifiedondemand.com/understanding-salesforce-delegated-
administration/

Order Process

Validation > Assignment > WorkFlow Rules > Escalation

What is Validation Rules

Validation rules verify that the data a user enters in a record meets the standards
you specify before the user can save the record. A validation rule can contain a
formula or expression that evaluates the data in one or more fields and returns
a value of “True” or “False”. Validation rules also include an error message to
display to the user when the rule returns a value of “True” due to an invalid value.

Assignment Rule - only used for Lead and Cases

Lead/Cases Assignment Rules—Specify how leads are assigned to users or

queues as they are created manually, captured from the web, or imported via the
Data Import Wizard.
Create assignment rules to automate your organization’s lead generation and
support processes.
■ Lead Assignment Rules—Specify how leads are assigned to users
or queues as they are created manually, captured from the web, or
imported via the Data Import Wizard.
■ Case Assignment Rules—Determine how cases are assigned to
users or put into queues as they are created manually, using Web-to-
Case, Email-to-Case, On-Demand Email-to-Case, the Self-Service
portal, the Customer Portal, Outlook, or Lotus Notes.

What is WorkFlow Rules

Workflow lets you automate standard internal procedures and processes to save
time across your org. A workflow rule is the main container for a set of workflow
instructions. These instructions can always be summed up in an if/then
statement.

Workflow rules can be broken into two main components.

1. Criteria: the “if” part of the “if/then” statement. In other words, what
must be true of the record for the workflow rule to execute the
associated actions.
2. Actions: the “then” part of the “if/then” statement. In other words, what
to do when the record meets the criteria.

What is Escalation Rules - only used for Cases

Escalation rules automatically escalate cases when the case meets the criteria
defined in the rule entry. You can create rule entries, which define criteria for
escalating a case, and escalation actions, which define what happens when a
case escalates.

What is Auto-Response Rules - only used for Lead and Cases

An auto-response rule is a set of conditions for sending automatic email
responses to lead or case submissions based on the attributes of the submitted
record. Applicable leads include those captured through a Web-to-Lead form.

Send automatic email responses to lead or case submissions based on the

record’s attributes. Set up auto-response rules to send quick replies to customers
to let them know someone at your company received their inquiry or details about
their issue.

Create auto-response rules for leads captured through a Web-to-Lead form and
for cases submitted through a:

■ Self-Service portal
■ Customer Portal
■ Web-to-Case form
■ Email-to-Case message
■ On-Demand Email-to-Case message
Create as many response rules as you like based on any attribute of the
incoming lead or case. Keep in mind that you can activate only one rule for leads
and one for cases at a time. Sales and service reps can find the email responses
in the Activity History related list of the lead or contact and in the Email related
list on cases.

Email-to-Case

Automatically turn emails from your customers into cases in Salesforce to

track and resolve customer cases quickly. Salesforce can automatically create a
case when an email is sent to one of your company's email addresses, such as
[email protected]. This Email-to-Case functionality auto-populates case
fields from the content of each email. For example, an email subject heading
becomes a case subject. Your organization can set up Email-to-Case or On-
Demand Email-to-Case to efficiently resolve and correspond with customer
inquiries via email.
What is Support Process - only used for Cases

Support process is Applicable only in Case, But Sales Process is applicable in

Opportunity. A business process is the same thing, but for Opportunities
instead of Cases.

A support process is the case status values assigned to a case record type:

1. Open

2. Case Accepted

3. Case Assigned

4. Case In Progress

5. Case Closed

A support process is simply one set of steps that are defined in the org. There
may be different steps for different types of cases, for example:

1. Open

2. Case Accepted

3. Case Proposed

3. Case Prioritized

4. Case Closed

Cross-object
-if you are trying to relate the records in different object o pagelayout but the object
should have relationship between.
Cross-object formulas can reference merge fields from a master (“parent”) object if an
object is on the detail side of a master-detail relationship. Cross-object formulas also
work with lookup relationships. You can reference fields from objects that are up to 10
relationships away.
Cross-object formulas are formulas that span two related objects and reference merge
fields on those objects.

Cross-object formulas are formulas that span two related objects and reference
merge fields on those objects. Cross-object formulas can reference merge fields
from a master (“parent”) object if an object is on the detail side of a master-detail
relationship. You can reference fields from objects that are up to ten relationships
away. Cross-object formulas are available anywhere formulas are used except
when creating default values

For example, enter Contact.Account.Name to reference the Account Name for a

contact associated with a case in a formula field on the Case object. Be sure to
use the relationship names of the objects, not the labels. Although the
relationship name is often the same as the object name, it is technically the field
name of the relationship field. For example, to reference the parent account
name from Account object, the syntax is Parent.Name, not Account.Name. Also,
when referencing a custom object, add two underscores and the letter r to its
name. For example, Position__r.title__c references the Job Title field (title__c) on
a Position custom object.

Roll-up Summary
-summarizing records with the same page-layout.

1. Count
2. Sum
3. Min
4. Max

A roll-up summary field calculates values from related records, such as those in a
related list. You can create a roll-up summary field to display a value in a master record
based on the values of fields in a detail record. The detail record must be related to the
master through a master-detail relationship. For example, you want to display the sum
of invoice amounts for all related invoice custom object records in an account’s Invoices
related list. You can display this total in a custom account field called Total Invoice
Amount.

Currency
When the multiple currencies feature is enabled, Corporate currency is used as
the basis for exchange rate

Data Import Service VS. Data Loader of Import Data

Data Import Wizard - avoid duplicate of records but cannot update

Opportunity, this tool, accessible through the Setup menu, lets you import data
in common standard objects, such as contacts, leads, accounts, as well as
data in custom objects. It can import up to 50,000 records at a time. It provides a
simple interface to specify the configuration parameters, data sources, and the
field mappings that map the field names in your import file with the field names in
Salesforce.
Data Loader—this is a client application that can import up to five million
records at a time but the records can be duplicated, of any data type, either
from files or a database connection. It can be operated either through the user
interface or the command line. In the latter case, you need to specify data
sources, field mappings, and other parameters via configuration files. This makes
it possible to automate the import process, using API calls.

Data Export Service VS. Data Loader of Export Data

Data Export Wizard—this is an in-browser wizard, accessible through the Setup

menu. It allows you to export data manually once every six days (for weekly
export) or 28 days (for monthly export). You can also export data
automatically, at weekly or monthly intervals.

Data Loader—this is a client application that you must install separately. It can
be operated either through the user interface or the command line. The latter
option is useful if you want to automate the export process, or use APIs to
integrate with another system.
Export All: Includes all data.

Export: Exclude(records)

Custom Fields
In the Salesforce CRM user interface, you can identify up to seven (7) custom
fields on an object as being an external ID field. The field type must be a text,
number or email field

Data Security

Levels of Data Access

You can control which users have access to which data in your whole org, a
specific object, a specific field, or an individual record.

*Organization
For your whole org, you can maintain a list of authorized users, set password
policies, and limit logins to certain hours and locations.

*Objects - can be done in profile level

Permissions: Create, View, Edit, or Delete, [View/Modify All Data and

View/Modify All- Admin only]

View/Modify All Permission on Object will give you View/Modify Access to All
records of the specific Objects you permissioned. View/Modify All Data will give
you permission to View/Modify all records in the system across all objects on
entire org.
*Records

You can allow particular users to view an object, but then restrict the individual
object records they're allowed to see. For example, an interviewer can see and
edit her own reviews, but not the reviews of other interviewers. You can manage
record-level access in these four ways.
1. Organization-wide defaults specify the default level of access users have
to each others’ records. You use org-wide sharing settings to lock down your
data to the most restrictive level, and then use the other record-level security and
sharing tools to selectively give access to other users.

Permissions: Private, Public Read/Write and Public Read Only

Org-Wide Sharing

Permissions: No Access, View Only, View & Edit

Org-wide defaults specify the baseline level of access that the most restricted
user should have. Use org-wide defaults to lock down your data, and then use
the other record-level security and sharing tools (role hierarchies, sharing rules,
and manual sharing) to open up the data to users who need it.
Permissions [CRED]– is the base-line level of the user to the records that the
user has access.
Org-Wide Default [Private/Public Read/Write]– restrict this user to the records
that the user does not own.
Private – No access to record you don’t own
Public Read – You can view all records you don’t own
Public Write – You can Edit and Delete the records you don’t own.

A. Role hierarchies give access for users higher in the hierarchy to all
records owned by users below them in the hierarchy. Role hierarchies
don’t have to match your organization chart exactly. Instead, each role in
the hierarchy should represent a level of data access that a user or group
of users needs.

B. Sharing rules - sharing rule is a set of predefined conditions on an

object, and if an object's record meets these conditions, the record is
automatically shared to a predefined role or a user group. All records of the
object that meet the conditions will be shared, there is no way to stop that without
changing the rule. Sharing rules are created and managed by admins.
Example: all Opportunities above $10M should be shared to everyone in
the C-suite, regardless of actual role hierarchy.

Permissions: Read and Read/Write

Sharing rules permission can be Read or Read/Write. Full access can't be

given through sharing rules. So providing Delete or Transfer permission not
possible through sharing rules.

C. Manual sharing - is a permission to access one specific record of any

object. Sharing this record in no way affects sharing of any other records of any
object, unless of course they are in a master-detail relationship with the manually
shared record. Manual sharing can be granted by the record owner. Sharing
button only appears on an object layout if the org wide defaults for that object
are set to private or public read only.
Example: sales rep is going on vacation and needs to share an
Opportunity in progress to another sales rep who is going to cover for him.

Permissions: Read and Read/Edit

*Fields – can be done in Field-level security

You can restrict access to certain fields, even if a user has access to the object.
For example, you can make the salary field in a position object invisible to
interviewers but visible to hiring managers and recruiters.

Permissions: View, Edit and Delete

In some cases, you want users to have access to an object, but limit their access
to individual fields in that object. Field-level security settings—or field
permissions—control whether a user can see, edit, and delete the value for a
particular field on an object.
Unlike page layouts, which only control the visibility of fields on detail and edit
pages, field-level security controls the visibility of fields in any part of the app,
including related lists, list views, reports, and search results.

Report Folder

A folder is a place where you can store reports, dashboards, documents, or

email templates. Folders can be public, hidden, or shared, and can be set to
read-only or read/write. You control who has access to its contents based on
roles, permissions, public groups, and license types. You can make a folder
available to your entire organization, or make it private so that only the owner has
access.
If a folder does not have Manager access, it is public, and users with the “View
Reports in Public Folders” permission can view it. Depending on their object
access, these users can also run the report.

(1) Share your folder by user, by user group, or by role.

(2) Choose the access level you want each user, group, or role to have.
(3) Stop sharing the folder with the user, group, or role.

Permissions needed to create a folder

To create, edit, or delete public document folders: “Manage Public Documents”

To create, edit, and delete public email template folders: “Manage Public Templates”
To create, edit, and delete public report folders: “Manage Public Reports”
To create, edit, and delete public dashboard folders: “Manage Dashboards” AND “View