Salesforce Certification Training & Courses Online - Victorious Digital (1)

1
(No Transcript)
2
Why Salesforce Training Courses?

• Salesforce is a CRM based application built on
  the Salesforce.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. Salesforce.com
  is getting used by more and more industries. So
  with increasing usage of SFDC technology which
  also has exponentially increased more jobs in the
  market.Salesforce Training Certification in
  Online, helps you to transform your professional
  profile, enable you to help your company prosper
  immensely, and gives an incredible experience of
  satisfaction to your customer base. Moreover,
  Salesforce training and courses also help you as
  an individual to earn the credentials necessary
  for your career growth. Even if you hail from a
  non-developer and non-coding background, it is
  never too difficult or late to start learning
  Salesforce based on cloud computing from Best
  Salesforce Training Institute Online.Learn and
  experience Salesforce training online by our
  expert trainer. We teach and provide the best
  with 100 practical Salesforce training with
  real-time projects and real-time examples to
  understand it in better for your future success.
  Also, you can explicit your doubts regarding
  Salesforce training with our experienced expert
  in Salesforce.com so register yourself and gain
  the best practical knowledge in Salesforce
  training.We are located in the prime location of
  Pune to provide you the best Salesforce courses
  online with a pack of all 19 modules of cloud
  computing with updated CRM tools plus a bonus of
  100 job assistance to direct you to your path
  with multiple higher and reputed designation
  under Salesforce training online.Dont think
  twice for Victorious Digital for the best Online
  Salesforce Classes with 75 of practical and 25
  of theory classes with real-time projects and
  real-time examples.

3
Why We are best Online Salesforce Training
Institute

• We are the best Salesforce Institute Online
  because Expert Faculty We have got our
  certified faculty who is a subject matter expert
  with 7 years of experience.
• Complete Course of 19 Modules We train you in 19
  modules in our online salesforce courses that
  impart deep knowledge on the subject.
• 100 Placement Assistance After the completion
  of our salesforce training course, we provide
  100 job placement assistance to our students.
• Placement Services We concentrate on both
  theoretical and 100 practical at our salesforce
  training institute/cloud computing training.
• Multiple Batches We have multiple batches on
  weekdays and weekends to choose from so that you
  can join a batch that is suitable to your
  schedule for Salesforce courses online
• Keep you Updated We keep you updated on the
  latest trends to help you be job ready.
• Affordable Fees Spend less money gain more
  knowledge only one-time payment with a pocket
  budget in our Salesforce courses online. Our
  salesforce (SFDC) training courses fees are
  affordable.
• Interactive Session We are providing the 2-way
  exchange of knowledge ideas of Salesforce
  courses between our students and faculty.
• Students from all over India We have multiple
  branches of Salesforce training institute online
  that allow students from all over the city to
  join our cloud computing courses.

4
What is Cloud Computing?

• Paradigm/model that allows On Demand network
  Access to Shared Computing Resources
• Mananging, Storing, Processing Data Online via
  Internet

5
Characteristics

• On Demand Service
• Network Access
• Shared Resources
• More scalability

6
Delivery Models

• SAAS (Software as a Service)
• PAAS (Platform as a Service)
• IAAS (Infrastructure as a Service)

7
SAAS

• On Demand Service
• Pay per use of application software to users
• Independent of platform
• Dont require anything to be installed in PC
• Runs in a single instance of Software
• Available for multiple end users
• Cheap
• Resources maintained by vendor
• Accessible via web browser

8
Examples

• Who uses-end users
• Gmail
• Office 365
• Google drive
• CRM Salesforce.com

9
PROS and CONS

• Accessible from any platform
• No need to commute
• (we can work from anywhere)
• Allows Multi tenancy
• Best for collaborative working

• Browsers issues
• Internet performance

10
PAAS

• Service made with programming language, web
  server, database
• Like Salesforce Force.com (use of apex language
  similar to java)
• Build, Compile, Run programs without worrying
  about Infrastructure
• Manage data, Application Resources

11
Examples

• Who uses- developers
• AWS
• Heroku
• Force.com

12
PROS and CONS

• Cost effective
• Faster market for developers
• Easy deployment
• Private Public deployment possible (use of
  managed package)

• Limited developers
• Migration issues

13
IAAS

• Computing Architecture , Infrastructure, but all
  in virtual environment
• Data storage, Virtualization, Servers, Networking
• Mainly handle application, data, runtime,
  Middleware

14
Examples

• Who uses Sys Admins
• AWS EC2
• Rackspace.com
• Gogrid

15
PROS and CONS

• Cloud provides the Infra
• Scalability
• Flexible

• Security Issues
• Network Service delays

16
Database

• collection of related data and its metadata
  organized in a structured format
• Database Management System (DBMS)
• is a software that enables easy creation, access,
  and modification of databases

17
Salesforce.com Database 

• organized collection of objects. 
• database tables to collect (or store) the
  information 
•  information as object in Salesforce.com
• table is presented with rows and columns
• Salesforce its maintained as Record and Field.

18
Database Structure

• In Salesforce.com objects are of three types
• Standard Objects These are the objects that are
  pre defined by the salesforce and readily
  available.
• Custom Objects These are the objects created by
  user according to their need .Each custom object
  has five standard fields (refer Note 2.2.1)
• External Objects These are the custom objects
  which are used to map the data stored outside
  your organization.

19
Default Standard fields

• ID This is an index allocated to each object.
  This value is unique. ID can be of 15 digit (Case
  sensitive) and 18 digits (Case insensitive)
• Name
• Owner
• Created Date/ Created By
• Last Modified Date/ Last Modified By

20
Normal excel based vs Relational database

• Relationships define the connection between two
  objects, and objects are related to each other
  through the use of common fields.

21
Types of Relationship

• Relationships associate one object with other
  object.
•  Relationship is always defined on the child
  object.
• The child object has complete access of the
  parent. Based on the handling of data deletion,
  record, ownership, security

22
Introduction of Primary-Keys Foreign-Keys
(Conceptual Knowledge)

• A Primary key is a column or set of columns that
  uniquely identifies the record in the table. When
  a primary key is defined using multiple columns,
  the data from each column is used to determine
  whether a record/row is unique. When we defined
  any column or columns as primary key, there are
  some constrains which should be satisfied by
  primary key that is column value should not be
  null (Null Constrains) and data should be unique
  (Unique Constrains.)
• A Foreign key is a set of one or more columns in
  a table that refers to the primary key in another
  table. Foreign key does not necessary  to be
  always point to primary key, but the basic idea
  behind foreign key is that any column which is
  unique to identify that record/row.

23
different types of relationships are categorized
in to following ways

• Master Detail
• Lookup relationship

24
Using 2 relationship we can build various
relationships in SFDC

• Many to One (Many child objects but one Parent
  Object)E.g. many metro cities are associated to
  One Country.
• This kind of relationship is represented in four
  different forms like
• Master-detail
• Look Up (Loosely Coupled Relationship)
• Self
• Hierarchical (only available on User object)

25
Master-Detail (1 n)  (One Parent Object and
Many Child Objects)

•  The record of child object gets automatically
  deleted when we delete the master object.
• To create a child object parent object reference
  field is required.
• Child object does not have separate sharing but
  it derives from Parent object, the detail records
  inherits the sharing and security settings of
  respective master record.
• The Owner field is automatically set to the owner
  of its associated master record as owner field is
  not available at detail side (child object).

26

• The detail record must have the master detail
  relationship field on its page layout.
• Administrators select Allow re-parenting option
  in the master-detail relationship definition to
  represent child records in master-detail
  relationship on custom objects.
• Master-detail relationships can be defined on two
  custom objects.
• One can define this relationship between one
  custom object and one standard object but in such
  relationship the standard object cannot be on the
  detail side of a relationship with a custom
  object. The data of custom object is displayed on
  page layout.
• master-detail relationship cant be created on
  objects where the User or Lead objects are the
  master.

27
Lookup (1 n) 

• Lookup is also one-to-many relationship but in
  this relationship two objects has no effect on
  deletion or security.
• Child objects are independent
• Child object have separate setting
• If we delete parent object child object will
  remain in system.
• Child may or may not have parent.

28
Self

•  In this relationship the object is
  self-referred. E.g. Add on Card on your credit
  card
• an object has a lookup with itself, it is a
  self-relationship. A self relationship creates a
  tree diagram of the objects. For example, the
  account has a lookup on himself, called Parent
  Account.

29
Hierarchical

• This is also (1 N) Lookup relationship
• But can only be defined on User object. In this
  we can use lookup field to associate one user
  with other user.
• relationship is a special lookup relationship
  available only for the user object. It allows
  users to use a lookup field to associate one user
  with another that does not directly or indirectly
  refer to itself. For example, you can create a
  custom hierarchical relationship field to store
  each user's direct manager.

30
 Many-to-many Very Very IMP

• master-detail relationships can be used to
  model many-to-many relationships between any two
  objects.
• In many-to-many relationship each record of one
  object is linked with multiple records from
  another objects and vice versa. 
• We need to create custom junction object to
  create a many-to-many relationship and then
  master-detail relationship fields, are linked
  with this objects.

31
Junction object

• This object is used to create Many-to-Many
  relationship.
• Salesforce support two relationship master
  detail and Lookup but both are 1n that is
  one-to-many.
• To define many-to-many relationship we need third
  object and that is called junction object.

32
Example

• Classroom and Courses
• Can have multiple courses in 1 classroom on
  different time
• Can have 1 course in multiple classroom
• To understand this we need a junction object
  Course offerings

33
Junction object Example

• Create 3 custom objects
• Classroom fields seats
• Course field Fees
• Junction Course offerings
• Fields start date, enddate
• On course offering have 2 master detail
  relationship one to classroom and other to Course

34
Sales Cloud process

• Objects within sales cloud
• Lead as prospects
• Account
• Contact
• Opportunity (if required)

35
(No Transcript)
36
(No Transcript)
37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
Model

• The model is your database objects in Salesforce.
  The include the standard Salesforce objects like
  Leads, Contacts, Accounts, Opportunities etc but
  it also includes any custom objects you've
  created. Think of it like this - the "model"
  represents your data model in terms of MVC.

43
VIEW

• The view represents the presentation of the data
  (i.e. the user interface).
• Pages - While often just called "pages", what we
  are talking about is Visualforce pages. They are
  the building blocks of the user interface.
  Visualforce uses HTML to lay out the appearance
  of the application interface. Each page is
  referenced by a unique URL just like a regular
  webpage. The pages themselves also
  contain Visualforce Components which can be
  invoked by simple tags inside the page. 
• Components - these are both standard and custom
  Visualforce Components. Think of them like
  widgets that you can add to your pages. Once you
  write the code once, you can reuse it on multiple
  pages. Components are important because they
  allow for this reuse. Components can be styled
  with CSS.

44
CONTROLLER

• Controllers are the building blocks of the actual
  application logic. The controllers are written in
  Apex code and they end up controlling and
  enforcing all the business logic. Remember that
  one of the key design elements of MVC is to
  separate the logic from the UI. The presentation
  layer (the view) shouldn't be mixed with a bunch
  of business logic. Pages interact with the
  controller through components which shuttle the
  data and specifies what happens when the user
  actually interacts with the UI. Salesforce has
  pre-built controllers for many of the standard
  actions like View, Edit, Save. If you want to add
  new behavior though you can extend or build new
  controllers (custom controllers) in Apex.

45
LookUp filter

• To filter the records to a lookup relationship
• For example Contact has lookup to Account
• Then user would only be able to select the
  accounts whose SLA is gold

46
Roll-up Summary Field

• A roll-up summary field is custom object field
  which calculates values from related records
  child records detail records or the records in a
  related list.
• Roll-up summary field is created to display a
  value in a master record based on the values of
  fields in a detail record.
• Roll-up summary can be defined on Master-Detail
  relationship only.

47
Types

• Assumption child record has fees field of master
• Count-count of all child records on master
• Sum- field on child for aggregation referred sum
  of fees field on child
• Min minimum value of fees in all child records
• Max maximum value of fees in all child records
• Go to App Setup Create Objects and click on
  New field and Select Roll up summary field.

48
Type Description
COUNT Totals the number of related records.
SUM Totals the values in the field you select in the Field to Aggregate option. Only number, currency, and percent fields are available.
MIN Displays the lowest value of the field you select in the Field to Aggregate option for all directly related records. Only number, currency, percent, date, and date/time fields are available.
MAX Displays the highest value of the field you select in the Field to Aggregate option for all directly related records. Only number, currency, percent, date, and date/time fields are available.
49
Formula Cross Object Formula Field in
Salesforce

• Formula Field is a read only field whose value is
  evaluated from the formula or expression defined
  by us. We can define formula field on both
  standard as well as custom objects. Any change in
  expression or formula will automatically update
  the value of formula field.

50
Return types of Formula Fields

• We can define formula field for 7 types
• Number
• Currency
• Percent
• Date
• Date/Time
• Checkbox
• Text

51
Cross Object Formula Field

• Cross Object Formula Fields are the fields which
  are based on a Cross-object formulas.
• The cross object formulas are defined on two
  related objects and reference merge fields on
  those objects.
• This field is built on child object. It is also
  known as Reference formula. We can apply
  cross-object fields up to 10 levels. 
  Cross-object formulas can reference merge fields
  from a master object as well as if field is at
  detail side then it can merge field from a
  master-detail relationship. Cross Objects formula
  can also be defined on lookup relationships.

52
Basic Config

• Pagelayout
• Record type
• Creation of Profile
• Creation of User

53
Record types

• Record types allow you to offer different
  business processes, picklist values, and page
  layouts to different users based on their
  profiles. Record types can be used in various
  ways, for example
• Create record types for Account to differentiate
  type of account for one business process with
  another and offer different picklist values for
  each.

54

• Record types allow you to associate different
  business processes and subset of pick list value
  to different users based on their user profile.
• They are used to drive which page layouts users
  see when viewing records, based on their user
  profile.
• Benefits of record types
•  Tailors user interaction experience to specific
  business needs.
• Allows for easier administration as there are
  fewer fields to maintain.
• Creating Record Types
• Example to create record types In this example I
  am creating record type for Case object.
• Setup-gtCustomize-gtObject(Account,case
  Contact)gtRecord Type

55
Pagelayouts

• Page Layout
• The organization of fields, custom links, and
  related lists on an object detail or edit page.
• Used to organize UI pages for your users
•           Which fields, related lists, and
  Custom links a users sees.
•           Field properties visible, read-only
  and required.
•           Page section customizations.
• NOTE Establish unique layouts for different
  business scenarios.
• Creating Page Layout
• Following is example to create page layout for
  case object.
• Set Up-gtCustomize-gtObject(Account,Contact,case)gtPa
  ge Layout-gtClick on New button
• Fill Mandatory details
• Drag and drop required to the layout and save
  page layout.

56
Page Layout Assignment

• Go to Record Type or Page Layout and click
  on Page layout Assignment
• assign page layout to record types based on
  profiles.

57
Concept of Dependent Picklist values

• Create two Fields
• Customer Type-
• Gold Silver platinum Bronze,Diamond
• Dependent picklist as Free Services-flight
  discount,drinks,Wifi,Lunch free
• Gold-has FD ----Silver-Wifi,drinks----Platinum
  all----diamond-wifi,lunch,FD---Bronze-drink

58
Validation Rules

• Validation rules verify that the data a user
  enters in a record meets the standards you
  specify before the user can save the record.
• A validation rule can contain a formula or
  expression that evaluates the data in one or more
  fields and returns a value of True or False.
• Validation rules also include an error message to
  display to the user when the rule returns a value
  of True due to an invalid value.
• rules helps you to improve data quality by
  preventing users form entering incorrect data. 

59

• Validation rules apply to new and updated records
  for an object
• Even if the fields referenced in the validation
  rules are not visible on the page layouts, the
  validation rule still apply and will result in an
  error message if the rule fails.
• If entered invalid data, it will display the
  associated error message without saving the
  record.
• Validation rules don't apply if you create new
  records for an object with Quick Create.

60

• Rule Name Validation_on_Account_revenue
• If Industry equal to Banking then annual revenue
  should not be null.
• Industry Banking and AnnualRevenue
• Error-Annual Revenue should not null when
  Industry is Banking.
• Link to practice more -https//resources.docs.sale
  sforce.com/204/latest/en-us/sfdc/pdf/salesforce_us
  eful_validation_formulas.pdf

61
Automation processes

• Workflow
• Approval Process
• Process Builder
• Assignment Rules
• Auto Response Rules
• Web to Lead
• Web to Case
• Email to Case

62
workflow

• Workflow lets you automate standard internal
  procedures and processes to save time across your
  org. A workflow rule is the main nfor a set of
  workflow instructions.
• Workflow rules can help automate the following
  types of actions based on your organization's
  processes
• Tasks Assign a new task to a user, role, or
  record owner.
• Email Alerts Send an email to one or more
  recipients you specify.
• Field Updates Update the value of a field on a
  record.
• Outbound Messages Send a secure, configurable
  API message (in XML format) to a designated
  listener.

63

• For example, workflow rules can
• Assign follow-up tasks to a support rep one week
  after a case is updated.
• Send sales management an email alert when a sales
  rep qualifies a large deal.
• Change the Owner field on a contract three days
  before it expires.
• Trigger an outbound API message to an external HR
  system to initiate the reimbursement process for
  an approved expense report.
• Each workflow rule consists of
• Criteria that cause the workflow rule to run.
• Immediate actions that execute when a record
  matches the criteria. For example, salesforce.com
  can automatically send an email that notifies the
  account team when a new high-value opportunity is
  created.
• Time-dependent actions that queue when a record
  matches the criteria, and execute according to
  time triggers. For example, salesforce.com can
  automatically send an email reminder to the
  account team if a high-value opportunity is still
  open ten days before the close date.

64
Scenarios

• Customer Type- gold email to owner of the
  account
• When SLA platinum update field Active as No
  on account.
• Contact phone is null update contact field phone
  with any default value(12345677890)
• When customer type is diamond assign task to
  record owner after 60 minutes of record creation

65
To be Continued

• Whenever Opportunity probability is 30
• Update field on Account Customer Priority as
  High

66
Email Template

• Creation
• Assigning to workflow Rule

67
Things to Remember on Workflow Rules

• Update field can only happen from child to parent
  but not from parent to child
• For eg- when opportunity is edited update filed
  on account but vice versa is not possible
• Workflow can only fire on same object or related
  object which has master detail relationship and
  not applicable for lookup relationship
• You cannot add time-dependent workflow actions
  with criteria created and every time its edited

68
Process Builder

• The Process Builder is a workflow tool that helps
  you easily automate your business processes by
  providing a powerful and user-friendly graphical
  representation of your process as you build it.
  The Process Builders simple and powerful design
  allows you toCreate your processes using a
  convenient layout with point-and-click
  efficiency.
• Create your whole process in one place rather
  than using multiple workflow rules.
• Create processes by collaborating with different
  teams in your business.
• Stop using Apex code to automate simple tasks.

69
Criteria

• Automated processes in the Process Builder are
  based on records and consist of
• Criteria that determine when to execute action
  groups.
• Immediate and scheduled actions to execute when
  those criteria are met.

70
Actions

• Create a record
• Update any related recordnot just the record or
  its parent
• Use a quick action to create a record, update a
  record, or log a call
• Launch a flowyou cant schedule this action with
  workflow
• Send an email
• Post to Chatter
• Submit for approval
• The process builder doesnt support outbound
  messages, but we can easily create one with Apex.

71

• Create a record This will allow you to create
  new records and set certain field values for the
  new record.
• Email alerts IN order to send an email from a
  process, you must create the email alert. To send
  an email alert that email should be associated
  with the same object on which process is started.
  Email template contains the standard text, list
  of recipients, and template

72

• Trigger a flow You can launch a flow from your
  process to automate complex business processes.
• Post to Chatter Process builder post to chatter
  action helps to post information to any user or
  group chatter feed within Salesforce. The post
  will appear in the chatter field as if the person
  who triggered the process had written it. You can
  reference groups or topics and add merge fields.
• Submit for approval Only the record that started
  the process will be submitted. You cant submit
  any related records for approval.
• Update records Update one or more records that
  are related to the record that started the
  process. You can update the record with manually
  entered values or by using the values from
  related records. We can update records of parent
  or child whereas workflow only updates same or
  parent object from the child.
• Quick actions You must already have global
  actions or an object specific action created
  within Salesforce to use these quick actions. You
  can then select to log a call, send an email, or
  update a record.
• Process This action will call another process to
  another process. For this action, you need to
  choose process type as it invoked by another
  process.

73
Why Process builder?

• Process builder is more flexible in comparison to
  workflow.In workflow rule cant update child
  record, Post to Chatter, auto submits record in
  the Approval process, invoke an apex or call
  flows.

74
Scenario

• On Account when status In progress
• Or customer type Bronze
• Create an Contact which gets attached to same
  account with same name as Account

75
Assignment Rules

• Assignment rules are used to automate
  your organizations lead generation and support
  processes.
• Assignment rule are used to assign owner to the
  records based on the condition.
• Lead Assignment Rules  Specify how leads are
  assigned to users or queues as they are created
  manually, captured from the web, or imported via
  the lead import wizards.
• Case Assignment Rules  Determine how cases are
  assigned to users or put into queues as they are
  created manually, using Web-to-Case,
  Email-to-Case, the Customer Portal

76

• Self Study
• Web to case email to case
• Scenario
• Account rating is hot assign Case to Tier 1 queue

77
Auto Response Rules

• An auto-response rule is a set of conditions for
  sending automatic email responses to lead or case
  submissions based on the attributes of the
  submitted record. Applicable leads include those
  captured through a Web-to-Lead form.
• Applicable cases include those submitted through
  a
• Self-Service portal
• Customer Portal
• Web-to-Case form
• Email-to-Case message
• On-Demand Email-to-Case message
• You can create as many response rules as you like
  based on any attribute of the incoming lead or
  case, but only one rule for leads and one for
  cases can be active at a time.

78
Auto-response rules and workflow email alerts
provide similar functionality. The following
table lists some of the differences between
workflow alerts and auto-response rules to help
you determine which process to use
TYPE OF PROCESS DESIGNED FOR RUNS WHEN SENDS EMAIL TO NUMBER OF EMAILS SENT
Workflow email alerts Notifications to interested parties. A case or lead is created or edited. Anyone you choose. Sends one email per email alert. Each workflow rule can have up to 10 email alerts as immediate actions 10 email alerts per time trigger as time-dependent actions 10 time triggers
Auto-response rules Initial response to the contact who created a case or the person who submitted the lead on the Web. A case or lead is created. Contact on a case or the person who submitted the lead on the Web. Sends one email based on the first rule entry criteria it matches in a sequence of rule entries.
79
Auto Response Rule Scenario

• Send Auto Response email to the person who
  creates web to lead
• Send Auto Response email to the person who
  creates web to Case and email to case

80
Escalation Rules

• Escalation rules automatically escalate cases
  when the case meets the criteria defined in the
  rule entry.
• You can create rule entries, which define
  criteria for escalating a case, and escalation
  actions, which define what happens when a case
  escalates.
• Reference-https//help.salesforce.com/articleView?
  idrules_escalation_create.htmtype5
• http//www.infallibletechie.com/2013/08/escalation
  -rule-in-salesforce.html

81
Web to Lead

• Salesforce web to lead is to directly collect
  capture the leads form your website and loaded
  into Salesforce.
• This is built in functionality in Salesforce.
  Nothing you need to download or install.
•  Go to set up -gt Customize -gt Leads -gt click on
  web-to-Lead
• we can see web to lead set enabled checkbox is
  checked. By default web to lead is enabled in
  sales force. And default lead creator is owner of
  the lead creator in Salesforce. By default it
  will display System Administrator who created
  Salesforce organization.

82
Web to Case

• customer support requests directly from your
  companys website and automatically generate up
  to 5,000 new cases a day with Web-to-Case.
• Web To Case is a means by which you can post a
  simple, unauthenticated web page that allows your
  customers to submit cases directly to your
  Salesforce.com instance.
• This means that you can post a public case
  submission page on your own website with your own
  branding and styling.
• Web To Case works by generating a snippet of
  HTML for you. This HTML is an HTML form that you
  can put on any page.
• When your customer presses Submit, the
  information on this form is posted directly to a
  Salesforce.com server, which handles the
  information, converts it to a case, and redirects
  the customer's browser back to a page of your
  choosing

83

• Generate same as Web to lead
• Self study -https//help.salesforce.com/servlet/se
  rvlet.FileDownload?file015300000036A6eAAE

84
Email -to -Case

• Salesforce can automatically create a case when
  an email is sent to one of your company's email
  addresses, such as support_at_company.com.
• This Email-to-Case functionality auto-populates
  case fields from the content of each email.
• For example, an email subject heading becomes a
  case subject.
• Your organization can set up Email-to-Case or
  On-Demand Email-to-Case to efficiently resolve
  and correspond with customer inquiries via email.

85
Email-to-Case

• Email-to-Case requires downloading the
  Email-to-Case agent and setting it up behind your
  network's firewall.
• Use Email-to-Case if you have a requirement to
  keep all email traffic within your firewall, and
  you want to accept email attachments larger than
  25 MB from customers.

86
On-Demand Email-to-Case

• On-Demand Email-to-Case uses Apex email services
  to convert email to cases, without you having to
  download and install an agent behind your
  network's firewall.
• Use On-Demand Email-to-Case if you are not
  concerned about keeping email traffic within your
  firewall and you do not need to accept
  attachments larger than 25 MB from customers.

87
Configure email to case

• From Setup, enter email- to - case in the Quick
  Find box,
• then select Email-to-Case.
• In the Routing Addresses list, click New.
• Enter your routing address settings.
• Click Save.
• A verification email is sent to the routing email
  address you provided.
• Click the link in the verification email.
• A confirmation page opens in your web browser.
• Click the link in the confirmation page to
  continue to Salesforce.

88
Approval Process

• Salesforce approval process is an automated
  process and your organization can use to approve
  records in Salesforce, An approval process is
  combination of steps for a record to be approved
  and person has to approve it each step. A step
  can apply to all the records to that object or
  just record that meets the certain criteria. An
  approval process also specifies the actions to
  take when a record is approved, rejected,
  recalled, or first submitted for approval.
• Simple or multi-step approval processes to
  automate and enforce the approval of virtually
  anything in your company.
• Navigate setup -gt Create -gt Workflow Approvals
  -gt Approval Processes.
• Select Object for the new approval process.
• Click on  Create New Approval Process and
  choose Use Standard Setup Wizard from the
  drop-down button.
• Note  If you want to create a basic approval
  process with default settings. Click on Use Jump
  Start Wizard.

89
(No Transcript)
90
Scenario

• Opportunities that are probability more than 40
  require a CEO approval. Use this example to
  create a one-step approval process.
• Whenever Account Status Completed,or Account
  Customer Type Platinum Account should follow
  approval process to submit record to manager of
  the user submitting the record

91
Data management

• Import wizard
• It is easy to use tool to load Accounts,
  Contacts, Leads, Solutions, or Custom
  Objects.-Load 50,000 records or less.-Prevent
  duplicates-Doesnt support all standard object
  but supports all custom object

92
Apex Data Loader

• Data Loader  is a tool or Application used in
  salesforce to import and export bulk data.
  ThroughApex Data Loader we are able
  to Update, Insert, Delete, Upsert, Export and
  Export All. Each operation will be different from
  each other.
• Insert  insertion of new records
• Update Updating existed  records.
• Upsert Update and Insertion of records
• Delete Deletion of records.
• Export Extraction of all records.
• Export All It extracts all records from
  salesforce including Recycle Bin records.

93
Advantages

• Is a fully supported salesforce.com product.
• Supports import from CSV or export to CSV.
• Can be used to import or export more than 50,000
  records.
• Supports loading from or exporting to a database
• Supports custom relationships for upsert.Can be
  run from command line.

94

• In dataloader settings we should enable insert
  null values checkbox otherwise we cant insert
  null values

95
Bulk API

• The Bulk API is used to upload high volume of
  data (millions of records).The Data Loader uses
  the SOAP-based Web Services API by default. To
  use the Bulk API instead, check Bulk API
  checkbox in apex data loader settings page.When
  you check Bulk API checkbox, increases the batch
  (upto 10000 records) which is usually 200 in
  normal upload.

96
External ID

• We have account table in Salesforce and account
  table outside of the Salesforce (ex .csv file,
  sql database).
• In Salesforce all the records can be identified
  with record id and outside of the Salesforce we
  cant recognize records with Salesforce id that
  is the reason to compare outside table and
  salesforce table in Salesforce for one of the
  field we have to enable external ID (we can
  enable external id for text, number, auto number
  and email).
• If we enable external id we can compare that
  particular column with the column which is
  available in external table. While comparing if
  the both column values are same then it will
  update otherwise it will insert.

97
Types of Salesforce Org

• Sandbox
• Production
• Deployment process

98
Different levels of Security

• Object level security
• The bluntest way that we can control data is by
  preventing a user from seeing, creating, editing,
  and/or deleting CRUD any instance of a particular
  type of object, like a Position or Review.
  Object-level access allows us to hide whole tabs
  and objects from particular users, so that they
  don't even know that type of data exists.
• On the platform, we set object-level access rules
  with object permissions on user profiles or
  permission sets
• Object Level security can be done in the
  following Sections.
• Permission Sets.
• Profiles
• Permission Sets  In this Permission sets we
  define the access level of the user. Generally we
  determine what a user can do in the applications.
  These are used to grant additional permission to
  a user. Profiles  In Object level Security,
  Profiles are assigned to the user by system
  administrator. A profile can be assigned to many
  users where as a user can have only one Profile.
• A permission set is a collection of settings and
  permissions that give users access to various
  tools and functions. The settings and permissions
  in permission sets are also found in profiles,
  but permission sets extend users functional
  access without changing their profiles.
• For example, to give users access to a custom
  object, create a permission set, enable the
  required permissions for the object, and assign
  the permission set to the users. You never have
  to change profiles, or create a profile for a
  single use case. While users can have only one
  profile, they can have multiple permission sets.

99
Record Sharing

• Object Level Security
• Field
• OWD
• Record Sharing

100
Field level security

• A variation on object-level access is field-level
  access, in which a user can be prevented from
  seeing, editing, and/or deleting CRUD the value
  for a particular field on an object. Field-level
  access allows us to hide sensitive information
  like the maximum salary for a position or a
  candidate's social security number without having
  to hide the whole object.
• On the platform, we set field-level access rules
  with the field-level security.

101
Record level security

• To control data with a little more finesse, we
  can allow particular users to view an object, but
  then restrict the individual object records that
  they're allowed to see. For example, record-level
  access allows an interviewer like Melissa Lee to
  see and edit her own reviews, without exposing
  the reviews of everyone else on her team.
• On the platform, we actually have four ways of
  setting record-level access rules
• Organization-wide defaults sharing settings
• Role hierarchies
• Sharing rules
• Manual sharing
• Apex Sharing

102
Organization wide default

• OWD stands for Organization wide defaults. This
  setting is defined at object level. OWD defined
  the default record level sharing for objects. All
  profiles get at least the privileges defined in
  OWD. OWD takes three different values
• Private
• Public Read only
• Public Read-Write
• Public Read-Write/Transfer
• To find out what should be set as OWD for an
  object, first find out which user requires least
  access to an object. OWD is set based upon this
  users access requirements.Most restrictive
  record access is defined using OWD. Access to
  additional records is made available through Role
  hierarchy, Sharing rules, Manual sharing, Apex
  sharing

103

• Private      If the OWD for an object is set to
  private, then only the owner, and users above
  that role in role hierarchy, can view, edit and
  report on those records
• Public Read Only     If the OWD for an object
  is set to Public Read Only, then all users can
  view and report on records but they cannot edit
  them. Only the record owner and the users above
  that role in the role hierarchy can edit the
  recordsPublic Read/Write If the OWD for an
  object is set to Public Read/Write, then all
  users can view, edit and report on all records.
  But only owner of the record can delete the
  records.
• Public Read/Write/Transfer This is available
  only for Case and Lead objectsIf the OWD for an
  object is set to Public Read/Write/Transfer then,
  all users can view, edit, Transfer and report on
  all the records but only owner of the record can
  delete the records

104

• Public Full Access This is available only for
  Campaign object.If the OWD for Campaigns are set
  Public Full Access then, all users can view,
  edit, delete and report on all records.
• No Access, View Only or Use This is available
  only for Price Book object.If the OWD for Price
  Book is set Use then, all users can access the
  Price Book information and as well as using the
  Price Book configuration for Opportunities with
  Products.If the OWD for Price Book is set View
  Only then, all users can access the Price Book
  information but not to use that Price Book detail
  in Opportunities with ProductsIf the OWD for
  Price Book is set No Access then, it restricts
  users from accessing information for Price Book
  and Prices.
• Controlled By Parent If the OWD for any object
  is set as Controlled By Parent, then user can
  perform an action on the record based on whether
  they can do the same on the parent record
  associated with it.

105
Role Hierarchy

• Role Hierarchy allows additional users access to
  records. A hierarchy of roles is defined based
  upon access requirements at record level. Each
  user belongs to a unique role.
• If a role has access to some record, than its
  parent and ancestors will also have access to
  this record.
• Roles can be created using the Manager Users
  menu.
• Roles are used to control record access, where as
  profiles are used to specify access at object and
  field level.

106
Public Group

• Public group consists of users, roles or "roles
  and subordinates".
• Sharing rule is defined using public groups.
  Record that match certain condition can be
  assigned to users in public groups using Sharing
  Rules.

107
Manual Sharing (User Managed Sharing)

• Manual Sharing is used to grant one-off access.
• Manual sharing can be granted by record owner,
  any one above the owner in role hierarchy and
  System Administrator.
• Manual sharing is used to handle exception cases
  where access to a particular record needs to be
  given to a specific user.
• There is a Sharing button on the records page.
  This is used to provide manual sharing.

108
Sharing Rules.

• Sharing Rules makes automatic exceptions
  to organization wide defaults settings for
  particular users in an organization. Sharing
  rules can be done by manual sharing, criteria
  based sharing and Apex managed sharing.

109
Controlling Access Using HierarchiesGrant Access
Using Hierarchies

• Determine whether users have access to records
  they dont own, including records to which they
  dont have sharing access, but someone below them
  in the hierarchy does.
• Beyond setting the organization-wide sharing
  defaults for each object, you can specify whether
  users have access to the data owned by or shared
  with their subordinates in the hierarchy.
• For example, the role hierarchy automatically
  grants record access to users above the record
  owner in the hierarchy. By default, the Grant
  Access Using Hierarchies option is enabled for
  all objects, and it can only be changed for
  custom objects.

110

• To control sharing access using hierarchies for
  any custom object, from Setup, enter Sharing
  Settings in the Quick Find box, then select
  Sharing Settings. Next, click Edit in the
  Organization Wide Defaults section. Deselect
  Grant Access Using Hierarchies if you want to
  prevent users from gaining automatic access to
  data owned by or shared with their subordinates
  in the hierarchies.

111
Important points

• Regardless of your organization's sharing
  settings, users can gain access to records they
  do not own through other means such as user
  permissions like View All Data, sharing rules,
  or manual sharing of individual records.
• The Grant Access Using Hierarchies option is
  always selected on standard objects and is not
  editable.
• If you disable the Grant Access Using Hierarchies
  option, sharing with a role or territory and
  subordinates only shares with the users directly
  associated with the role or territory selected.
  Users in roles or territories above them in the
  hierarchies will not gain access.
• If your organization disables the Grant Access
  Using Hierarchies option, activities associated
  with a custom object are still visible to users
  above the activitys assignee in the role
  hierarchy.
• If a master-detail relationship is broken by
  deleting the relationship, the former detail
  custom object's default setting is automatically
  reverted to Public Read/Write and Grant Access
  Using Hierarchies is selected by default.

112

• The Grant Access Using Hierarchies option affects
  which users gain access to data when something is
  shared with public groups, personal groups,
  queues, roles, or territories. For example, the
  View All Users option displays group members and
  people above them in the hierarchies when a
  record is shared with them using a sharing rule
  or manual sharing and the Grant Access Using
  Hierarchies option is selected. When the Grant
  Access Using Hierarchies option is not selected,
  some users in these groups no longer have access.
  The following list covers the access reasons that
  depend on the Grant Access Using Hierarchies
  option.
• These reasons always gain access
• Group Member, Queue Member, Role Member, Member
  of Subordinate Role, Territory Member, Member of
  Subordinate Territory
• These reasons only gain access when using
  hierarchies
• Manager of Group Member, Manager of Queue Member,
  Manager of Role, Manager of Territory, User Role
  Manager of Territory

113
Apex Sharing

• Apex managed sharing is a type of "Programatic
  Sharing" which allows you to define a custom
  sharing reason to associate with your programatic
  share.
• Standard Salesforce objects support "Programatic
  Sharing" while custom objects support Apex
  managed sharing. More specifically, object shares
  can be written to both standard and custom
  objects, however custom sharing reasons can only
  be defined for shares written to custom
  objects.apex manage sharing is used for custom
  objects as we can define apex sharing reason for
  custom objects. For standard object, apex sharing
  reason will be Manual
• Salesforce create share table for all objects for
  which OWD is either public read only or
  Private. For standard object, share table name is
  table name followed by share word. For
  example AccountShare, ContactShare,
  CaseShareFor custom object, it is followed by
  __share. For example  For Position__c, share
  table name is Position__share

114

• Objects on the detail side of a master-detail
  relationship do not have an associated sharing
  object. The detail records access is determined
  by the masters sharing object and the
  relationships sharing setting.

115
Create share table record using apex

• Share table contains four columns ParentId,
  UserOrGroupId, RowCause, AccessLevel.Below is
  code to create position__share record
• Position__share p new Position__share()p.pare
  ntId Position Record Id which needs to be
  sharedp.userOrGroupId User id or Group id
  with which we want to share recordp.RowCause
  apex sharing reason defined for custom object,
  here for position__cp.AccessLevel access
  level for record //can be Read or Editinsert
  p
• Note you cannot update share table record.
  System only allows insert or delete of records
  for share table. So if you have to change access
  for user, you have create new record and can
  delete already existing record if you want.

116
Scenario

• Account Sharing Example The Western and
  Eastern Regional Directors need to see all of the
  accounts created by each others sales reps. You
  can create two public groups one that includes
  the Western and Eastern Regional Director roles
  and one that includes the Western and Eastern
  Sales Rep roles. Then create an account sharing
  rule so that records owned by the Western and
  Eastern Sales Rep group are shared with the group
  containing the Western and Eastern Regional
  Director roles

117
What is a report?

• A report is a list of records that meet the
  criteria you define. Its displayed in Salesforce
  in rows and columns, and can be filtered,
  grouped, or displayed in a graphical chart.
• Every report is stored in a folder. Folders can
  be public, hidden, or shared, and can be set to
  read-only or read/write. You control who has
  access to the contents of the folder based on
  roles, permissions, public groups, and license
  types. You can make a folder available to your
  entire organization, or make it private so that
  only the owner has access.

118
Standard Salesforce Reports

• A report represents the relationship between
  primary objects and its related objects. To
  represent this relationship report has predefined
  templates which makes reporting easier. Every
  report displays only those records which meets
  the criteria.
• Salesforce has Standard report type as default
  report type. Standard report type is present for
  all salesforce standard objects. For custom
  objects, salesforce automatically create a
  standard report type using with, or and
  relationship.

119
Custom Salesforce Reports

• The custom report type can be created by
  selecting the objects of your interest and their
  relationships. The wizard will give access to all
  child objects of these selected objects. This
  type of report can be customize as per user need.

120
Salesforce Reports Presentation Styles

• Based on the presentation following styles can be
  used to generate report in salesforce.
• Tabular Report  The basic form of presentation
  of user data is tabular report. It has simple
  listing of data without any subtotals. One can
  use this report if the presentation is simple.
• Summary Report  Summary report is little bit
  advanced report as compare to tabular report
  having grouping of information with subtotals.
• Matrix Report  Matrix report has groups of data
  based on columns and rows. This report can be
  used to represent comparison between related
  total with total by row and total by column.
• Join Report  Join report has the more advanced
  way to represent data. This report will allow you
  to relate different blocks and show them in
  single report. Each block has unique attributes
  like name, filters, columns, data, and summary
  fields.

121
Features of the Salesforce Reports

• Salesforce Reports is one of the most powerful
  features to represent business and easy
  understanding of the relationship among objects.
   Every report in salesforce support following
  features.
• Custom Summary Formula field User can define
  formula based on summary report is generated.
• Exception Reports (Cross Filters) These reports
  are used to show highlight the position where
  data doesnt exist. These reports are created
   using cross filters.
• Custom Summary Formulas These formulas are used
  on reports to calculate complex data from summary
  level.
• Analytical Snapshots Snapshot captures data at
  schedule point with respect to time.
• Historical Trend Reporting This will allow you
  to track your data. This will allow you to track
  upto 8 fields on Opportunity object and 3 fields
  up to custom objects.
• Bucket Field Salesforce allows us to categorize
  records without using any formula. This is known
  as Bucketing. In bucketing user defines the
  bucket field (or bucket multiple categories) to
  group report value.
• Condition High-lighting  To highlight field
  values on summary or matrix reports based on some
  criteria like value ranges user can apply
  conditional highlighting. To enable this, report
  must have custom summary formula or at least one
  summary field.

122

• Scheduling report for future run  Once you
  create a new report we can schedule report by
  using following steps
• Set the frequency field to run report. It can be
  any value you want to run the report number of
  times like Daily, Weekly or Monthly.
• Mention the dates in Start and End fields.
• To run the report you must select start time.
  Click on Find available options  to  choose a
  start time.
• To save report schedule click on Save Report
  Schedule.

123
What is a dashboard?

• A dashboard is a visual display of key metrics
  and trends for records in your org. The
  relationship between a dashboard component and
  report is 11 for each dashboard component,
  there is a single underlying report. However, you
  can use the same report in multiple dashboard
  components on a single dashboard (e.g., use the
  same report in both a bar chart and pie chart).
  Multiple dashboard components can be shown
  together on a single dashboard page layout,
  creating a powerful visual display and a way to
  consume multiple reports that often have a common
  theme, like sales performance, customer support,
  etc.
• Like reports, dashboards are stored in folders,
  which control who has access. If you have access
  to a folder, you can view its dashboards.
  However, to view the dashboard components, you
  need access to the underlying reports as well.
  You can also follow a dashboard in Chatter to get
  updates about the dashboard posted to your feed.
• Each dashboard has a running user, whose security
  settings determine which data to display in a
  dashboard. If the running user is a specific
  user, all dashboard viewers see data based on the
  security settings of that userregardless of
  their own personal security settings. For this
  reason, youll want to choose the running user
  wisely, so as not to open up too much visibility.
  For example, set the Sales Manager as the running
  user for a leaderboard for her team. This allows
  her team members to view the leaderboard for
  their individual team, but not other teams.
• Dynamic dashboards are dashboards for which the
  running user is always the logged-in user. This
  way, each user sees the dashboard according to
  his or her own access level. If youre concerned
  about too much access, dynamic dashboards might
  be the way to go.

124

• Dashboard is a page layout for visual display of
  your data. Each dashboard has 11 mapping for its
  component and report. One can clubbed multiple
  dashboard components to display a single report.
  The security settings is used to control the
  visibility of data. These dashboards are dynamic
  in nature. User can only view their own data as
  per their settings.

125
Dashboard components and their usage

• Charts, tables, gauges, metrics are component in
  dashboard. User can select any of these component
  to view data.

126

• Chart Chart is used for graphical presentation
  of data. Visual force has variety of chart types
  to represent your data.
• Gauge This can be used when the single value
  need to pointed within range of custom values.
• Metric This used to represent data based on one
  key value.
• Table Table is used to show the set of data.

127
Dashboard Settings

• The dashboard setting option is available next to
  report setting for tabular reports limited by
  row.
• Dashboard Running User concept
• Each dashboard has a running user, based on
  security settings determined by the user the data
  is display in a dashboard.
• To select a dashboards running user in
  Salesforce Classic use following steps
• Go to Edit a dashboard.
• Click the down arrow button next to the View
  dashboard as
• Select a running user setting. It has two options

128

• Run as specified user. In this view all users
  able to see same data regardless of their
  personal security settings.
• Run as logged-in user.This type of settings is
  used in dynamic dashboard and each user can view
  only their own data

129