salesforce overview

1. Salesforce
Presented by :
Maheswar Reddy

2. Indroduction:
 Salesforce CRM is customer relationship management
 Salesforce CRM developed company sfdc.com
 Salesforce CRM introduce by the Marc Benioff in the
year of 1999
 Salesforce Crm is easy to under standard

3. Cloud computing
 Cloud computing is nothing internet
 Cloud computing is a group of unknown resources that
are giving to or a specific purpose to the user
 It is a concept of pay per use of each IT service
Three type service:
1.IAAS
2.PAAS
3.SAAS

4. Three type of cloud
1.Marketing cloud
2.Sales cloud
3.Service cloud

5. Property of object
 Page layout
 Validation rule
 Search layout
 Button links
 Action
 Record type
 Triggers

6. Relationship
1.Master relationship
2.Lookup relationship
3.Many to many relationship
4.Hierarchical relationship

7. Reports:
 Reports is over all information
They are four type:
1.Tabular report
2.Summary report
3.Matrix report
4.Join report

8. Dashboards
 Dashboard shows the data from source report
 Each dashboard can have up to 20 components
 Like as
1.Horizantal bar chart
2.Vertical bar chart
3.Line chart
4.Pie chart
5.Table

9. Workflow
 Workflow rules allow us to automate the business
processes for organization
They is four type of action:
1.Email alert
2.Tasks
3.Field update
4.Outbound message

10. Approval Processes
 An approval process is an automated process your
organization can use to approve records in Salesforce.
 allowing you to specify a sequence of steps that are
required to approve a record.
 An approval process also specifies the actions to take
when a record is approved, rejected, recalled, or first
submitted for approval.

11. Profile:
 Profile is collection of settings.
 Profile is object level and field level access and it is
mandatory for all users.
Permission set:
 permission sets extend user’s functional access with
out changing user’s profile.
Role:
 Role is record level access and it is not mandatory for
all user

12. Share rule
 If we want to give the access to other user we use
share rule.
OWD:
 Organization wide defines the level of access to user
can see the other user’s record.
 Owd can be private, public read, public read and write.

13. Data loader
 Data loader is a tool provided by sales force.
 It is allow the duplicated data
 We can support record 1millin
 Data loader to perform following operation
1. Insert: it is for inserting data from external machine(file
should be an CSV).
2. Update: it is for updating existing record.
3. Upsert: it is having the function of insert and update.

14. 4. Delete: its for deleting data(deleted files available in
recycle bin).
5. Hard delete: its for deleting but its not recoverable .
6. Export: its for taking out the data from our
salesforce.com.
7. Export all: for all data extraction

15. Import wizard
 It is one way of import/export of the into from salesforce
 To support standard object account, contact, lead,
solution and custom object.
 Duplicated not allow
 Up to 50,000 records.

16. Apex :
 Apex is a strongly typed, object-oriented programming
language that allows developers to execute flow and
transaction control statements
 on the Force.com platform server in conjunction with
calls to the Force.com​ API.
Collection:
 Collection are the group of similarly type.
They three type of collection

17. 1.List:
 A list is an ordered collection.
 List can contain Duplicates.
 so use list when you want to identify list element based
on Index Number.
Syntax: list<account>list=new list<account>();
2.Set:
 A set is an unordered collection of primitives.
 Set can not contain duplicates.

18. Syntax: set<account>set=new set<account>();
3.map:
 A map is a collection of key-value pairs where each
unique key maps to a single value.
Syntax: map<key, Pairs>map=new map<key, pairs>();

19. Difference between SOSL and SOQL in
Salesforce
SOSL SOQL
stands for "Salesforce object search
language".
stands for "Salesforce object query
language".
Works on multiple object at a same time. Need to write different SOQL for
different object.
All fields are already text indexed. SOQL against same field will be slow.
Cannot used in Triggers. Can only be
used in Apex class and anonymous
block.
Can be used in Apex class and Triggers.

20. Trigger
 Apex can be in invoked through the use of trigger.
 A trigger are functional actions which gets fired on
particular events.
Seven set of events:
Before insert
Before update
Before delete
After insert
After update

21. After detete
After undelete
Trigger syntex:
Trigger trigger name on object name(events)
{
Code
}

22. visualforce
 Visualforce is a framework that allows developers to
build sophisticated, custom user interfaces that can be
hosted natively on the Force.com platform.
 The Visualforce framework includes a tag-based
markup language, similar to HTML, and a set of server-
side “standard controllers” that make basic database
operations, such as queries and saves, very simple to
perform.

23. Components
 Similar to the way you can encapsulate a piece of code
in a method and then reuse that method several times
in a program.
 you can encapsulate a common design pattern in a
custom component and then reuse that component
several times in one or more Visualforce pages.
 A custom Visualforce component. All custom
component definitions must be wrapped inside a
single <apex:component> tag.

24. Batch apex
 To use batch apex we must write an apex class that
implements the salesforce provided interface
database.batchable and then invoke the class
programmatically
 The database.batchable interface contains three
methods that must be implemented.
1.Start method
2.Execute method
3.Finish method

25. Apex Scheduler
 Apex scheduler is helpful to invoke apex classes to run
at specific times, first implement the “schedulable”
interface for the class, then specify the schedule using
either the schedule apex page in the sales force user
interfaces or the system schedule method
Email service:
Email service are automated processes that use apex
classes to process the contents, header, and
attachments of inbound email