The document provides an overview of Salesforce for beginners, including an introduction to the platform and data modeling. It discusses Salesforce's standard and custom objects, fields, and relationships. It also covers data security with Salesforce's layered sharing model including object, field, and record level access controls. The document concludes with a brief introduction to using Apex code to customize Salesforce functionality.

1. Developer Beginner : Salesforce
Trailhead
BY PRATIK SHRESTHA
COMPLIANCE QUEST

2. Overview
• Introduction to Salesforce
• Data modeling
• Data Security
• Apex

4. What is Salesforce ?
• Salesforce is a top-notch CRM application built on the Force.com platform.
• It can manage all the customer interactions of an organization through different media,
like phone calls, site email enquiries, communities, as well as social media.
• Salesforce handles all the customer relationships, by focusing on the sales, marketing and
support processes. This is done by working with the standard objects (Shown below), and
facilitating the relationships between them. Introduction to Salesforce

5. Data Modeling
Standard Data Model
▪ Standard Objects
 Account
 Contact
 Lead
 Opportunity
 Case
 …
▪ Standard Fields
 Id
 Name
 CreatedBy/Date
 LastModifiedBy/Date
 OwnerId
 IsDeleted
 …

6. Extensible Data Model
▪ Custom Objects
 Property__c
 Broker__c
 Favorite__c
 ….
▪ Custom Fields
 Status__c
 City__c
 Baths__c
 Beds__c
 Mobile_Phone__c
 …

7. Object Relationship
 Object relationships are a special field type that is created to link Objects
with each other.
 Due to the relationship user can view the records.
 They can see the related list to that records.
 For example, By creating a custom relationship field on the object, we can
define different types of relationships.
 There are two main types of object relationships: lookup and master-detail.

8. Master-Detail Relationship
 Master-Detail relationship is one type of relationship which forms a tight bond
relationship between a parent object and a child object.
 Child records should always be associated with a parent they cannot remain orphans.
 Cascade record deletions. When a parent object record is deleted all its child records
get deleted automatically.
 Standard Objects aren’t allowed to be used as details (Child object). A detail object,
for example, cannot be an account.
 The master-detail relationship fields are required on the page layouts of the detail
object.
 Roll-up Summary fields can be created on the Master object(Parent Object.)
 Child record inherits all security and sharing settings from its parent record.

9. Lookup Relationship
 Lookup relationship is one type of relationship which forms a loose bond
relationship between a parent object and a child object.
 In lookup, Child records need not be associated with a parent.
 No Cascade record deletion happens.
 Read more about Object relationship in Salesforce at the Blueflame Labs,
the salesforce consulting partners.

10. Schema Builder
 Schema Builder is a tool that lets you visualize and edit your data model.
 It’s useful for designing and understanding complex data models

11. Data Security
 Salesforce has layered sharing model.
 You can balance security and convenience ,reduce the risk of stolen or
misused data, and still make sure all users can easily get the data they
need.
 By combining security controls at different levels, you can provide just the
right level of data access to thousands of users without having to specify
permissions for each user individually.

12. Levels of Data
Access
Object Field Record
Preventing a user from
viewing, editing, creating
or deleting any instance of
a particular type of object.
Preventing a user
from viewing, editing,
creating or deleting
the value for a
particular field on an
object.
You can allow
particular users to
view an object, but
then restrict the
individual object
records they're
allowed to see.

13. Object Level Access
Create
View
Delete
Edit

14. Field – Level – Access
In Salesforce, profiles also control field-level access.

16. Record Level Access

17. Select appropriate default value
for sharing each object.

18. President
CEO
CFO CTO
Director of
Sales
VP Sales
Manager
Role – Hierarchies

19. Sharing Rules with Public Groups

20. Manual Sharing
Use this ‘button’ to individually share records.

21. Apex
 A strong typed object oriented programming language which is used to develop applications on top
of salesforce platform.
 Using apex you can write the custom business logic on the top of salesforce platform which can be
executed on different occasions like on a button click or you’re saving a particular recordings etc.
When to use Apex?
 To do certain automation that cannot be implemented using workflows or process builder.
 To implement complex validation rules.
 Whenever you want to create a web services to interact with external application.
What can’t Apex do?
 You can’t show anything on the UI using Apex except error message.
 We cannot change any salesforce functionality , we can add only new functionalities and stop the
execution of existing functionality onto particular action.
 Apex cannot be used to create temporary files.
 You cannot create multiple threads .

22. Flow Of Action