Salesforce
You might think that Salesforce is just a CRM. It stores your customer data, gives you processes to
nurture prospective customers, and provides ways to collaborate with people you work with.
Salesforce comes with standard functionality for tracking common sales objects like accounts,
contacts, and leads. But DreamHouse is a realty firm, so it has needs specific to its industry and
business model With the platform, you can customize and build whatever it is that makes your
company unique.
Administration: CRM
Wat is CRM and what does it do?
CRM = Customer Relationship Management, software that stores customer contact information (like
names, addresses, and phone numbers) and keep track of customer activity (like website visits,
phone calls, email and more)
What CRM does?
helps with contact, lead and opportunity management
track Deals, Product planning, manufacturing planning and shipping
What is salesforce CRM?
Salesforce = world’s number 1 CRM platform, is cloud-based applications for sales, service, marketing
but also a platform where you can also develop your own applications
idea salesforce connect desktop and mobile device to salesforce
Organizations in salesforce
o Production: where the client works real-time with original data (default)
o Sandbox: are copies of your production (with sample data that you CAN CHANGE) in a
separate environment used for development and testing.
o UAT – user acceptancy test: preproduction
Introduction
Standard (created by Salesforce) Customize (created by organization: create, modify, delete)
Right corner of salesforce you can see per cloud the standard applications (chatter, content,
marketing, service)
Creating custom objects
Object = data table in salesforce’ database which stores users data/information (name, salary, email,
domain) and organization’s information.
standard objects: can be renamed, but never can be deleted
o Leads: any person that may be interested in your products/services
o Accounts: info about organization with a relationship to your company
, o
Contacts: individual directly associated with an account and possibly one/more
opportunities
o Opportunities: store info about open and close deals and track any potential
generating sales deal or event
o Campaigns: a marketing initiative (ads, email) that you conduct in order to generate
prospects and build brand awareness
o Cases: store customers’ questions, feedback or issues
o Solution: Represents a detailed description of a customer issue and its resolution
o User: to allow a person log in to SF and access information
o Reports and Dashboards: info you can display that provides a summary of your data
and there are visual representation of your custom report data
o Documents: repository of reference documents online eg. Contract
eg. Standard object are related to account records: cases and opportunities
o Products: used on opportunities, Pricebook
Custom objects = created by user, can be customized by adding fields, creating relationships
• each object has 5 standard fields (name, label, data type, controlling field, indexed)
Must be configured: Name field is a standard field to identify records and can be text
field or auto-number (eg. V-0002)
• Enterprise Edition (200) and Unlimited and Perf Edition (2000)
• Optional features: allow reports, activities, track field history, in chatter groups
Assets are related to Products, Cases, Accounts, Contacts
Setup > build > create > object > new custom object > custom fields & relationships
Creating custom fields
Record = rows in object database tables. Records are the actual data associated with an object.
Fields are columns in object database tables.
field label: appear in the user interface: on the contact page and easy to understand
field name: what you see in the API API name: __c (customer object)
Able to change the API name
Help text: text is explained if the user scrolls over the info-button next to the field
Custom Field types: allow users to select a value: picklist or lookups
eg. Time Field: store info about preferred contact hours of customer, record the opening and
closing hours for store location (2 Time fields: opening, closing)
Customization options for standard fields
Field labels can be changed
Standard picklist values can be added, renamed, reordered, deleted
Field-level help text can be added
Field-level security
CANNOT delete standard fields, but you can remove non-required standard fields from page
layout to hide them for users
Field history tracking: need to be enabled on a field add related list to object page layout
enable fields history tracking on Case Status field and add related list to Case page layout
(up to 20 some standard and any custom fields on an object) automatically track changes in
the values of fields, the user that made the change, date/time of change or added a field to
the page layout (up to 18 months for org, and 24 months via API)
, Lookup filter can be added/edited: restrict the valid values and filter the records displayed
(eg. Restrict account name field on opportunity to allow only active accounts)
In Classic: required or optional, in LE: required (even it is optional during Setup)
if a lookup filter is defined on a lookup field means that user can only pick a value
that meets the previously used filter criteria (filter is case sensitive)
Applied to hierarchical relationship, master-detail relationship and lookup fields to
the Account, Contact, User, CO and Available in the Partner and Customer Portal
Benefit of using Lookup Filter instead of a VR: Improves user efficiency when
selecting related records
They can reference fields on the target object as well as fields on records related to
the target object or fields related to the user
Data loss
Changing field type of custom field data being lost (warning!): any list views based on the
field may be deleted (eg. change Percent to Number, one Currency to another currency)
Field type of custom field that is referenced by Process Builder cannot be changed
Assignment rules and Escalation rules may be affected
Deleting a custom field if there are no references to it (VR, workflows, processes)
A deleted field, its data and field history can be stored within 15 days until it is permanently
deleted: all field history data is deleted and changes are no longer tracked.
Hard-deletion: to free up custom field allocation
Custom field attributes
• Default field values: certain field types can have a default value set
>< Don’t assign default values to fields that are both required and unique
• Text field: can be set as case sensitive: values as ABC or abc, treated as different values
Setup > object manager > field & relationships > new > (1) data type > (2) enter details > (3) set
field-level security: visibility and editability by profile > (4) add to page layout
Creating custom tabs
Tab = user interface between app and object. It is required so user can interact with the object to
store records.
1. Create, name the tab and select the object:
If you create custom object a new tab must be created to be able to create records via UI
2. Choose the user profiles for which the tab will be available
Check if the object permission is correctly applied to the profile
3. Choose the app for which the custom tab will available: add tab to app
Profile don’t have access to app, the profile can still have access to tab and objects of the app
Custom tabs can be custom objects, Web tabs, Visualforce tabs, Lightning tabs
Setup > App Setup > Customize > Rename Tabs and Labels: rename Tab Names of standard objects.
If you add custom object tab:
Recent items
Sidebar search
Added to New Link/ Create New Object drop down
Custom Reports
, Declarative development = developing without code you use forms and drag-and-drop tools to
perform customization tasks.
Programmatic development = which uses things like Lightning components, Apex code, and
Visualforce pages.
Creating custom apps
App= collection of tabs made visible to certain profiles; workspace where the user works – a set of
objects, fields, and other functionality that supports a business process.
• Standard Apps eg. Sales, Marketing, Service, Community, Chatter, Content, Console apps
• Custom Apps: can have both standard and custom object tabs
eg. Create two custom apps with different tabs and apply one each to two different profiles
Create New App: user is taken to developer.force.com page:
Selecting tabs, selecting profiles, adding a logo
• You can see which app you’re using and switch between apps using the App Launcher
Every profile must have at least 1 visible app, except profiles associated with Customer Portal users
because apps are not available for them
Distinction in two Lightning apps
Lightning apps can have their own colors and brand images
Use pinned list view as the default list view for records that frequently accessed by the users
User no longer can view some of the tabs:
User has customized the navigation bar of the app:
• Default On: allows the tab to be visible in the app and when viewing all tabs
• Default Off: allows the tab to still visible when viewing ‘All Items’ in App Launcher,
not visible in the app
User has used the App Launcher to switch to a different app
User has logged into the wrong SF org
Admin could modify the access to a tab for a profile, not for individual user:
Enable ‘Tab Hidden’: tab will not be visible in app by default and the user cannot enable it
Lightning App Builder create Lightning Pages
• Create an App Page
• Create a Home Page: customize Home page for different profiles in LE (users cannot
customize their own Home Page): company logo, dashboard snapshot, custom links
Home page can be assigned to each app
• Create a Record Page: customized record page available to users must be activated
(customizations: Lightning components can be added, edited, reordered, removed)
eg. Lightning component Path not displayed on opportunity record page until sales reps have
been trained to utilize it: modify existing opportunity record page and remove the sales Path
component using Lightning App Builder or create and activate a new opportunity record page
in LB and assign it only to the sales reps
Different record pages displayed for different record types
Record page doesn’t have to be assigned just to profiles, can be assigned at different
levels: as the org default, as app default, as app/ record type/ profile assignment
• Create an Embedded Service Page
Creating custom links
Used for: