Process Builder

WorkFlow

Approval Process

Flows

Organization Level Security X

Object Level Security

Field Level Security

Record Level Security

Relationships X

Master Detail Relationship X

Validation Rules

Formulas

Cross Object Formula Fields x

Record Types x

Insert Update Upsert X

Insert tools (there is one to schedule these workbench) x

Record ID and External ID

Standard Objects (need and usage Leads, Accounts, Contact, Opportunities, Products,
Pricebooks objects) x

---------------------------------------------------

Leads, Accounts, Contact, Opportunities, Products, Pricebooks, Contract, Orders

Campaign Object

used to store the information of the campaign that you do for marketing or generate
new leads.

Leads

Store info of potential customers of your business

Account

store information of prospects that are interested to buy something, or just

customers we had business with
those can be either people or companies, prospect and customers

Contact
store info of specific key people and individuals working on that particular
account

Opportunities

store information of deals that are happening or that happened with customers and
prospects either if is lost or won

Products

store information of the products/services availbale in the inventory and selling

in the company, save quantity too

Pricebooks

to store info of different prices we have for the same product and more products

Quote

tracks all quotes of a single deal, and we use a button to send it and customer
will check it out

Contract

store info of contract, dates, products rate provided.

-----------

Workflow

Old school Automation tool

4 types of action:

send email
field update
task
outbound message (Process Builder doesnt have it)

Process Builder

Gives a user friendly visual

8 types of action:

create record
update record related to it
post something onto chatter
launch a flow
launch a quick action
submit automatically for the approval
call an apex code
invoke to another process
You can put order of all the different actions that at which criteria, which action
will be getting executed that
this criteria should evaluated

Can control evaluation criteria of the processes using this tool, workflow cant

Shouldn't create workflows and processes together in a single object because

Salesforce cannot guarantee
the order of execution of them and that may create some problems

If cant make automation in declarative way (workflows and processes), then use Apex
triggers.

----------------------------------

Organization Level Security

4 features

Managing password policies: defining level of complexity that a password is

required to match,
like lenght or capital letters, how many days till expiration of password and how
many invalid attempts
and we can set logout period (15-30-60 mins or forever which means that password
can only be reset by admins)

Restricting login location:

login IP ranges (in which if you are outside of the IP range of the org you get a
login challenge that requires
OTP from email or phone number but if you are out of login IP ranges of the user
you cant login at all)
2 levels: Organization and Profile level

Restricting login by time: when someone is logged and the time finishes, the user
will only be able to see the
page, when they click to go somewhere else, they get logged out

Restricting users email domain: we can use to limit which email domains must be
used to register.

Health Check scans your org and compares security and sharing settings with
Salesforce defaults and provides a
percentuage of how secure your org is, providing also a detailed report that where
does your org stands in security
Pointers: High risk, medium risk, meets the standard

----------------------------
Manual Sharing

gives other users access to certain types of records, including accounts, contacts,
and leads.
if you grant another user access to an account, the user automatically
has access to all the opportunities and cases associated with that account.

If a user transfers ownership of a record, Salesforce deletes any manual shares

created by the original
record owner, which can cause users to lose access. When account ownership is
transferred, manual shares
created by the original account owner on child records, such as opportunities and
cases, are also deleted.

--------------------------------

Lookup Relationships
essentially links two objects together so that you can “look up” one object from
the related items on another object.
Lookup relationships can be one-to-one or one-to-many.
Objects in lookup relationships usually work as stand-alone objects and have their
own tabs in the user interface.

Master Detail Relationships

In this type of relationship, one object is the master and another is the detail.
The master object controls
certain behaviors of the detail object, like who can view the detail’s data.
With a master-detail relationship you can delete the property and all its
associated offers from your system.

the detail object doesn’t work as a stand-alone. It’s highly dependent on the
master. In fact,
if a record on the master object is deleted, all its related detail records are
deleted as well.
When you’re creating master-detail relationships, you always create the
relationship field on the detail object.

Hierarchical relationships
are a special type of lookup relationship.The main difference between the two is
that hierarchical
relationships are only available on the User object. You can use them for things
like creating
management chains between users.

------------------------------

The INSERT option pushes the incoming records to the destination.

The UPDATE option keeps track of the records being updated in the database table.

The UPSERT option is the combination of ‘Update’ and ‘Insert’ which means that it
will
check for the records that are inserted or updated.

------------------------------

Data Import Wizard

in-built Data Import wizard that is accessible through the Setup menu and can help
you to import accounts,
campaign members, person accounts, leads, custom objects, and contacts. This wizard
is a step-by-step process
that can take data to your desired location and displays error messages to change
the potential duplicates of records.

It provides an easy interface and self-explanatory wizard to load the data into
Salesforce.
You can perform import operation from this wizard but delete and insert operations
cannot be performed through
this wizard. Data import wizard doesn’t allow to load the duplicate records and all
fields can be individually
mapped by this wizard within Salesforce.

Data Loader

perform insert, update and delete operations on Salesforce records. It enables you
to
interact with your data within Salesforce across all objects.

Data loader can help in various ways such as:

Inserting data from one system to another upon the initial implementation of
Salesforce
Updating bulk records with new data
Deleting bulk records that aren’t required anymore
Exporting data to other systems
Create a backup of previous data

Features of the Data Loader

Easy-to-use tool to offer a great interaction with data.

Command line interface for performing automated operations.
Support and manage the excess amount of data.
Drag-and-drop functionality is used for mapping fields.
It can be used to streamline data in both Salesforce and Database.com.
Error log files in CSV format.

Data Import Wizard Data Loader

For simple imports of data For complex imports of data

It can load up to 50,000 records. It can load up to 5,00,000 records.

It supports all the custom objects and only

a few standard objects like Account, It supports all custom and standard
objects.
Contact, Campaign members, person
accounts, Leads, and Solution.

It supports schedule export. It doesn’t support scheduled export.

Delete operation is not available. Delete operation is available.

Cannot import cases and opportunity. Can import cases, events, tasks,
and opportunities

While importing, duplicates can be ignored. While importing, duplicates cannot

be ignored.

It doesn’t require installation. It requires installation.

------------------------------------

Cross-object formulas
they incorporate fields from related objects for calculations and display on detail
pages,
list views, and reports. These formulas get data from related parent objects to
display on the child object.
Using them is a great way to avoid duplicate work, duplicate data, and data
inconsistency.

Cross Object Formula Fields span two related objects and reference merge fields on
those objects.
It can be referred to merged fields of parent objects on the child objects.
Cross Object Formula Field is available on both master-detail as well as lookup
relationship.
Fields can be referred up to 10 relationships away.

A Formula that references a field on another object is known as a Spanning

Relationship.
The limit of spanning relationships per object is 15. This means that an object can
only
contain up to 15 different object references.

Formula fields can expose data that user do not have access, such as:
- user do not have access to the field level security within the same object
- cross-object where user do not have access to the record
- cross-object where user do not have access to the record and the field
- cross-object where user do not have permission to the object

Roll-Up Summary Field

If a roll-up summary field doesn’t contain cross-object field references or
functions that
derive values on the fly, such as NOW or TODAY, it can calculate the values of
formula fields.

Record Types

Record types let you offer different business processes, picklist values, and page
layouts to different users.
You might create record types to differentiate your regular sales deals from your
professional services
engagements, offering different picklist values for each. Or you might display
different page layouts for
your customer support cases versus your billing cases.

Page Layouts

Page layouts control the layout and organization of buttons, fields, s-controls,
Visualforce,
custom links, and related lists on object record pages. They also help determine
which fields
are visible, read only, and required. Use page layouts to customize the content of
record pages for your users.

Record types control:

Business processes
Represented by special picklist fields that capture the lifecycle of standard
object such as Opportunity,
Case or a lead or a lifecycle of a custom object

Page layouts
let you select and organize groups of fields related to an object

Picklist Values
lists of choices that you define when you create a picklist field, defining a
master list
with all possible choices and use a record type to display a subset, depending on
the situation.

Status field is used by Case Support Processes

First Business Processes, then page layouts then record types then picklist values

User selects a record type, and it provides him the fields, picklist values and
business process that
he needs for that type of case

Edit record type assignments in Manage Users > Profiles

Any records created before record types must have a record type assigned
retroactively by the
proper record type ID (not automatically)