================ Salesforce Class Org Access ========================
https://login.salesforce.com/[email protected]&pw=sfdc@123
================ Assignments: [email protected] ========================
https://trailhead.salesforce.com/en/content/learn/trails/force_com_admin_beginner
* 24th May --> Salesforce Platform Basics
* 25th May --> Data Modeling > Understand Custom & Standard Objects
25th May - STARTS
* App: Training Management -
* Object: Batch -
Fields:
* Name (Auto Number)
* Start Date
* End Date
* Object: Student -
* Name (Auto Number)
* First Name
* Last Name
* Mobile
* Email
25th May - ENDS
26th May -
* Applicant: Either Mobile Number of the Email field value is required
AND(
ISBLANK( Email__c ),
ISBLANK( Mobile_Number__c ),
OR(
ISNEW(),
ISCHANGED(Email__c),
ISCHANGED(Mobile_Number__c)
)
)
* Applicant: Either Tofferl or GRE field is required
27th May -
Create the relationships b/w the below objects -
Batch
Student
Fee -
Amount
Course
1st June -
* Send email to the owner of the Opportunity if the Opportunity amount is >
1M
================ Salesforce Websites ========================
Free Salesforce Account Registration -
https://developer.salesforce.com/
Salesforce Production Login -
https://login.salesforce.com/
Salesforce Sandbox Login -
https://test.salesforce.com/
Free Salesforce Learning Platform -
https://trailhead.salesforce.com/
Salesforce carrier profile to show case skills and certification achievements -
https://trailblazer.me/id?lang=en_US
Salesforce Apps Market Place -
https://appexchange.salesforce.com/
Ideas Exchange -
https://trailblazer.salesforce.com/ideaSearch
Salesforce Servers -
https://trust.salesforce.com/en/
Certifications Registration -
https://www.webassessor.com/salesforce
Admin Beginner -
https://trailhead.salesforce.com/en/content/learn/trails/force_com_admin_beginner
================ Current Batch Demo Recordings ========================
-----------------------------------------------------------------------------------
-------
Basic Termilonogy -
Project --> Application / App
Table --> Object
Columns --> Fields
Rows --> Records
SQL, DML--> Tab (Link to an object)
CRM Apps -
* Marketing -
Campaigns --> Advertisements
Leads --> Company + Person
Account --> Company
Contact --> Person
* Sales -
Opportunity --> Deal
Account --> Company
Contact --> Person
* Service -
Case --> Support Activity
Account --> Company
Contact --> Person
---------------------------------
Developer Editon -
* Data Space: 5 MB
* Only 2 users with Saleforce
* No Sandbox option
---------------------------------
10 users * 300$ = 3000 * 12 = 36k $
Airtel -
Marketing App -
Campaigns
Lead (SonixHR --> Gayatri)
Account (Company) -
Name: SonixHR
Contact (Employee/Person) -
FirstName: Gayatri
Mobile: *******
Opportunity (Deal) -
Name: Internet for 100 Emps
Sales App -
Opportunity (Deal) -
Name: Internet for 100 Emps
Accounts
Contacts
Service App -
Case
Accounts
Contacts
Airtel -
Yamini + 5 TM
Java CRM App -
UI (HTML,javaScript, css) ----> Business Logic (Java) ---> Database
(Oracle) ---> Server Space
3 - 6 Months --> Basic CRM App
Salesforce CRM App -
Unlimited --> 30 Free Trail
Airtel Production -
Yamimi --> System Administrator
https://login.salesforce.com/ or https://sonixhr-dev-
ed.my.salesforce.com
Username:
[email protected] Password: sfdc@123
https://login.salesforce.com/[email protected]&pw=sfdc@123
5 users
Sandboxes - https://test.salesforce.com/
100 Reqirements -
Sonix -->
1 Manager + 1 TL + 4 TM (3 Admin/Dev + 1 QA)
Jira (Proeject Management) -
Airtel CRM App -
Req1 --> Shivani
Req2 --> Chandini
|
Req100
Agile Process -
Sprint 1 -
2 weeks -
1 week for Dev -
4 Admin/Dev --> 4 Req
2 week for QA -
1 QA --> 4 Req
Sprint 2 -
Sprint 3
Dev -
Username: [email protected]
Password: ****
QA -
Username: [email protected]
Password: ****
UAT -
Username: [email protected]
Password: ****
Development Life Cycle -
Dev ---> QA ---> UAT ---> Production
Configuration (Point and Click) --> Administration / Admin --> 3 weeks
Customization --> Development / Dev --> 5 weeks -
UI ---> Business Logic ---> Database
UI -->
* HTML, javaScript, CSS
* Visualforce
-- Basics --
* Lightning -
* Aura
* LWC (Lightning Web Components)
Business Logic -
* Apex
Database -
* SOQL
* SOSL
* DML
Integration -
Airltel -
SFDC --> CRM
SAP --> ERP
QuickBooks --> Accounting
-----------------------------------------------
Basic Termilonogy -
Project --> Application / App
Table --> Object
Columns --> Fields
Rows --> Records
SQL, DML--> Tab (Link to an object)
---------------------Project - STARTS---------------------------
Working Company: Sonix
Project Name: JHU Admissions
Client Name : JHU University (USA)
End Users: Employees of JHU University
* Administration Staff -
* Collect applications from the applicants in differnt formats(hard
copy, word , PDF)
* Faculty Staff -
* Evaulate the applications to give admission or not
* Course Administrators -
* Designing the courses for University for UG/PG
Admin/Dev Users: Employees of Sonix
High level Requirement: Need an application to manage the admissions of the JHU
University
Total Req: 100 Req
* One Applicant can apply for the multiple courses
* One Course can have multiple applicants
* One Application at a time should be associated with only one course
* One Application should be associated to only one applicant at a time.
Applicant (Many to Many) Course
One to Many One to Many
Course Application -
Fields -
Name (Auto Number)
Status (Picklist) -
New
Queued for Assessment
Under Assessment
Under Conditional Approval
Conditional Approval Pending
Pending for Business Approval
Closed - Admit Applicant
Closed - Application Denied
Withdrawn by Applicant
Canceled by Admissions
Education Details (Text Area)
Experinece Details (Text Area)
Decision Conditions (Text Area)
Decision Notes (Text Area)
App Name: JHU Admissions
Object Name: Course
Fields:
* Name
* Fee
* Graduation Type
* Department
* Syllabus
Tab: Courses
Object Name: Applicant
Fields;
* Name (Auto Number)
* First Name (Text(32))
* Last Name (Text(32))
* Salutation (Picklist) -
Mr.
Ms.
Mrs.
Dr.
Prof.
* Gender (Picklsit) -
Male
Female
* Email (Email)
* Mobile (Phone)
* DOB (Date)
* Age (formula)
* Country (Picklist) -
India
USA
* City (Picklist) -
Bangalore
Hyderabad
New York
San Fransisco
Tab: Applicant
ISBLANK() --> null, ''
ISNULL()-->null --> for relationships
Setup > Session Settings > Enable secure and persistent browser caching to
improve performance --> Disable
1,000,000
(080)-8898-7889
Course-0001
Course-1000
Course-9999
Course-10000
Requirement: Based on the Department automatically Department Sub Type picklist
values should be controlled.
Solution: Use Field Depency
Controlling Field -
* Picklist
* Checkbox
Dependent Field -
* Picklist
* Multi Select Picklist
* Multi Currency
* Time Zone
* Search Layouts -
* To control 'Recently Viewd' list view and global search result view
fields.
* No more than 10 fields can be added to a search layout.
* List Views -
* You can display up to 15 fields.
Record Id -
18 digits -
* Lightning Experinece
* API
a00(Object) 5g0000(Org Id) 2vVNHF(Unique) AA4(Checksum)
15 digits -
a005g00002vVNHF
a005g00002vVNHf
001 --> Account
003 --> Contact
005 - User
Note: First 3 digits of the record represents the object type
JHU Production -
Employees of JHU University
Sandboxes -
Dev -
--> QA --> UAT --> Prod
---------------------Project - ENDS---------------------------
Record Types -
Lead --> Status --> Lead Process
Opportunity --> Stage Name --> Sales Process
Case --> Status --> Support Process
Solution --> Status --> Solution Process
--------------------------------------------------------------
Applicant(Parent) (Many to Many) Course(Parent)
One to Many (Lookup) One to Many (Master - Detail)
Course Application (Child)
Relationships -
-- Field Data Type --
1. Lookup -
* The relationship field is not required on all child records by default.
You can make this field required but the existing records continue without any
value.
* Reparenting the records is possible by default.
* When a user deletes the parent record, all child records are not deleted,
it only clears the lookup field value.
* The ownership and sharing of a child record can be managed independently.
* You cannot create rollup summary fields on the parent record to summarize
the child records.
--
* Max. 40 relationship fields can be created per object.
2. Master Detail -
* The relationship field is required on all detail records.
* Reparenting the records is not possible by default. Enabled Allow
Reparenting checkbox in the M-D field.
* When a user deletes the master record, all detail records are deleted.
* The ownership and sharing of a detail record are determined by the master
record.
* You can create rollup summary fields on the master record to summarize
the detail records.
* Max. 2 Master Detail relationship fields can be created per object.
3. Hierarchical -
* You can see standard Hierarchical relationship fields on Account and User
Objects
* Creating custom Hierarchical relationship field is only possible on the
user object.
Purpose:
--------- External Object ----------
4. External Lookup
5. Indirect Lookup
Salesforce Database -
Standard Object
Custom Object
External Database -
External Datasource --> External Objects
[email protected]
pw=sfdc@123
Username: [email protected]
Security token (case-sensitive): KDmznxKS50VuhxgX1LCvav91
-- No Data type --
6. Many to Many
7. Self
External Ids -
1. Auto Number
2. Number
3. Email
4. Text
* Max. 25 External Id fields can be enabled per object.
Formula -
* It will be calcualted automatically by using the same object fields and
the parent object fields.
Rollup Summary -
* It will be calcualted automatically by using the child object
information.
You cannot create a new Master-Detail relationship on an existing custom object
if records already exist. You must first create a Lookup relationship, populate the
lookup field with data in all records, and then change the relationship type to
Master-Detail.
Object --> Table
Records --> Rows
Fields --> Colulmns
Security -
1. Org Level (Before we Log into Salesforce) -
Org Level -
* Network Access > Trusted IP Ranges --> To bypass the verification
code.
Profile -
* Login IP Ranges
* Login Hours
2. Config Level (Apps, Tabs, Objects, Fields, System Permissions) -
* Profile - It holds set of permissions over the Apps, Tabs, Objects,
Fields, Record Types, System
Permissions
* When you create a user, relating the user to a profile is mandatory.
* Once the user is created it is not possible to delete the user in
Salesforce.
Apps -
* Show / Hide / Default
Tab -
* Default On
* Default Off
* Tab Hidden
Object -
* Create
* Read
* Edit
* Delete
Field -
* Read
* Edit
Record Type -
* Show / Hide
System Permissions -
* View Setup and Configuration --> to see the setup
* Bulk API Hard Delete --> to allow hard delete
* Permission Sets -
* It holds most of the permissin present in the profile.
* It is used to provide additional permission over the profile
Note: It is not possible remove permissions over the profile
P1 --> 10 users
P2 --> 10 users
P3 --> 10 users
Amount --> 1 user in P1, 2 users in P2 , 5 users in P3
3. Record Level -
-- Basic Access on the object data --
* OWD (Organization Wide Defaults) -
* Public Read/ Write
* Public Read Only
* Private
* Role Hierarchy -
* To deal with the record access
-- To increate access over OWD and Role Hierarchy --
* Manual Sharing -
Course__c
Course__Share
Account
AccountShare
* Apex Managed Sharing
* Sharing Rules -
1. Owner Based
2. Criteria Based
-- Profiles / Permission Sets --
-- Object Specific --
* View All
* Modify All
-- All Objects --
* View All Data
* Modify All Data
Users -
1. Yamini --> System Administrator --> CEO
2. Batch93 --> System Administrator --> SVP Customer Service and Support
3. Test1 --> Standard Platform User --> SVP Customer Service and Support
4. Test2 --> Standard Platform User --> Customer Support, International
P1 --> 10 users
P2 --> 10 users
Course: private
2 users of P1, 1 user of P2 should be able to see and modify all the
records of the Course.
Solution:
1. Create a permission set
2. Enable Modify All permission
3. Assign 2 users of P1, 1 user of P2
----------------Automation - STARTS-----------------------------------
Group (Public Group , Queue) -
Group Members (Users , Role, Public Groups)
Public Group -
* It can be used with sharing settings (Manual Sharing, Sharing Rules, List
View Sharing Settings...)
Queue -
* To assign the record owner to the multiple users at a time
* To assign for the multiple users approval in the approval process
Workflow Rules -
Immediate Workflow Actions -
1. Field Update
2. Email Alert
3. New Task
4. Outbound Message
Time Dependent Workflow Actions -
1. Field Update
2. Email Alert
3. New Task
4. Outbound Message -
Reference: http://intg-playground.herokuapp.com/
Field Update -
Cons -
1.
* It can be used to update only one field.
* Only same object and master objec fields can be updated.
* Updating parent in lookup or updating child records is not
possible.
2. For each criteria and action we need to create a sperate workflow
rule
Pros -
1. Outbound Message is used for the integratin with writing custom
logic
Standard / Custom Object -
Activities -
* Task
* Event
Object: Opportunity
Criteria of WFR: Amount > 1M --> Send Email
created, and every time it's edited -
Create: Amount = 2M --> Fires to send email
Edit: Stage = 'Negotiation and Review' --> Fires to send email
created, and any time it's edited to subsequently meet criteria -
Create: Amount = 2M --> Fires to send email
Edit: Stage = 'Negotiation and Review' --> won't fire
Note: It fires only if the criteria meeting due to the new modification
(existing record should not meet the criteri)
Requirements -
1. To assign the owner to Business Faculty Queue when the course is
related to Business department
2. To assign the owner to Science Faculty Queue when the course is
related to Science department
3. If the Status = 'Queued for Assesment' and Owner is a user then
update the Status to 'Under Assesment'
4. If the Status = 'Under Assesment', send email notificaiton after 1
hour.
Process Builder -
Pros -
1. Update Records:
* Updating multiple fields is possible
* Updating parent object record fields and child object record fiels is
possible
2. Only with one process we can manage including each criteria and the
corresponding actions.
Cons -
1. Outbound Message is not possible, if you want to integrate we need to
call apex logic
Approval Process -
----------------Automation - ENDS-----------------------------------
Data Management -
* CSV (Comma Seperated Value) is the file format used for the tools
1. Data Import Wizard -
1. Web Based
2. Supported Operations -
1. insert
2. update
---
3. Upsert --> insert / update
3. Supports only following standard objects -
1. Campaign Members
2. Accounts and Contacts
3. Solution
4. Lead
4. Supports all the custom objects
5. It supports only max. 50k records at a time.
2. Data Loader -
1. Stand Alone (Download and Install)
2. Supported Operations -
1. insert
2. update
3. upsert --> insert / update
4. Delete --> Delete the records but stores the data in the Recycle Bin
5. Hard Delete --> Delete the records perminantly without keeping in
the Recycle bin
6. Export --> It won't include data present in the recycle bin while
exporting
7. Export All --> It also includes data present in the recycle bin
while exporting
3. It Supports all the standard objects
4. Supports all the custom objects
5. It supports only max. 5M records at a time.
--
3. Data Export --> Backup
Username: [email protected]
Security token (case-sensitive): PfKGv8B5UedO0IrwLy0dupRus
--
Chrome Plug ins -
Salesforce Inspector
Partner Applications -
DataLoader.io
Reports and Dashboards -
---------------
Web2Lead -
Web2Case
Assignment Rules -
* It can be created only on the Lead and Case Object
* Purpose: To assign the owner of the lead or case based on criteria.
Auto Responsive Rules -
* It can be created only on the Lead and Case Object
* Purpose: To notify the lead or case owner with a spcific email template
format
Escalation Rules -
* Only can be configured on the case object.
*
---------------------------------------------------
JHU University Employees -
*** Internal Users ***
* Administration Staff
* Faculty Staff
* Course Administrators
*** External Users ***
Partner Account -
contact1
contact2
Customer Account -
contact1
contact2
HP -
employees --> internal users
Partner -
Distributors
Amazon Account -
amazon con1
amazon con2
Retailers
Customer -
TCS Account -
tcs con1
tcs con2
CTS Account -
cts con1
cts con2
Communities (Digital Experineces) -
* To provide access to the external users (partners / customers)
================================================================================
