###### 1st level Admin Basics ######
CRM -
Pre Sales -
Campaigns --> Adventertisements
Lead --> who enquires about the product or service (Company + Employee)
Account --> company
Contact --> Person / Employee
Opportunity --> Deal
Post Sales -
Case --> Support Activity
Solution / Knowledge Articles --> The solutions to resolve the problem
------------------------------------
Production - Live environment/instance where the end users use the applications
* Production URL: [Link]
Sandbox - Test environment/instance where we do developement or testing
* Sandbox URL: [Link]
------------------------------------
CRM Apps -
1. Marketing
2. Sales
3. Service
App ---> Collection of tabs
Tab ---> It links to an object which can fetch data and show on UI and also we can
perform DMl operations once we see the data after clicking on the tab
Object --> Database Table
* Standard Object --> which is provided by Salesforce
* Custom Object --> which is created by admin/developer as per the requirement
Field --> Column in a database table
Record --> It is a row in the database table
---------------------
API --> Application Programing Interface
Record Id (API Name: Id)
--> Unique Id for the record which is automatically generated by Salesforce
15 digit id -
* Salesforce Classic URL
18 digit id -
* Salesforce Lightning Experience
* Through API (When we programatically query using soql)
Standard Objects -
Account
Contact
Custom Objects -
Applicant__c
Course__c
----------------------
Validation Rule -
It can be configured to throw the error when the user enters bad data and save.
Note: It fires only for insert (Create) or update (Edit)
----------------------
Field Dependency -
It can be created b/w two fields. one field is controllable field the other
field is dependent field. Based on the controlling field value, the values of
dependent field will be decided.
Note:
Controlling -
* Picklist
* Checkbox
Dependent -
* Picklist
* Multi Select Picklist
----------------------
Relationships -
1. Lookup -
a. Lookup field is optional by default
b. When you delete the parent record , the related child records will not
be deleted, only the lookup value from the all related child records will be
cleared.
c. Rollup Summary cannot be created
2. Master Detail -
a. Master Detail field is required by default
b. When you delete the parent record all the related child records will be
deleted.
c. Rollup Summary can be created
3. Hierarchical
4. External Lookup
5. Indirect Lookup
---
6. Many Many
7. Self
----------------------
Workflow Rules -
a. It fires automatically when the record is created or edited. It is possible
to peform new field update, new email alert, new task, new outbound message
b. For each criteria to perform actions we need one workflow rule
Process Builder -
a. It fires automtically when the record is created or edited. It is possible
peform all the actions of workflow rule except outbound message and also many
addtional actions like Submit for Approval, Invoke Apex, Invoke flows.
[Link] each criteria to peform different actions in same process we can
configure
----------------------
Profile -
a. Deals with permissions on Apps, Tabs, Objects, Fields, Record types, System
permissions
b. Profile is required for all users
Role -
a. Deals with the data/records access based on role hierarchy and OWD level
b. Role is optional for users
----------------------
Data Import Wizard -
a. We can load upto 50k records
b. Supported DML operations -
1. insert
2. update
3. upsert
Data Loader -
a. We can load upto 5M records
b. Supported DML operations -
1. insert
2. update
3. upsert
4. delete
5. hard delete
6. export
7. export all
------------------------
Reports -
a. To summarise the information and display in a understandable way to the
business users. We have Tabular, Summary, Matrix and Join reports
Dashboards -
a. The graphical represenation give to the report. In dashboard multiple graphs
to understand the business can be added.