Salesforce Admin Notes

1. What is Salesforce and why do we need to use salesforce.

Ans: Salesforce is a CRM platform established by Marc Benioff in 1999, San Francisco. Over 150,000 companies using salesforce. 

Ex: Godrej, CEAT, Edelweiss, Clear trip, DTDC, Titan, Razorpay, IDFC mutual funds, Bharat Petroleum, L&T realty, Saint Gobin, etc.

Uses: 

* Win more customers by getting to know their needs and concerns.

* Deliver the amazing shopping experiences your customers expect.

* Respond faster to customer support issues on any channel.

* Automate time-consuming tasks by building custom apps.

2. Cloud Computing, IAAS, PAAS, SAAS

Ans: 

Cloud Computing:  Store, access, and work with data over the online cloud.

Uses: Fast implementation, No up-front costs, Instant scalability, Maintenance-free

Access anywhere, better security, 

IAAS: Infrastrcture as a Service

Examples: Amazon EC2, Windows Azure, Rackspace, Google Compute Engine.

                                      

PAAS: Platform as a Service 

Examples: AWS Elastic Beanstalk, Windows Azure, Heroku, Force.com, Google App Engine, Apache Stratos.

 

 

 

SAAS: Software as a Service

Examples: Google Apps, Microsoft Office 365.

 

3. Cloud in Salesforce

* Sales Cloud:

* Marketing Cloud:

* Analytics Cloud:

* Community Cloud:

* Commerce Cloud:

* Service Cloud:

* App Cloud:

* Collaboration cloud

For detail learning please go through below link

https://tweakyourbiz.com/business/crm/salesforce-cloud-types

 

4. Salesforce Portals.

* Self-Service portal

* Partner Portal

* Customer Portal

Customer Portal:

It allows customers to manage their cases, views solutions/knowledge, contribute to communities (questions, answers, ideas), and access data within custom objects.

Partner Portal:

The key difference between the customer portal and partner portal is that partner users can access leads and opportunities. This allows your organization and its partners to collaborate on your organization’s sales pipeline. Partners can also manage cases, view solutions/knowledge, contribute to communities (questions, answers, ideas), and access data within custom objects.

Self-Service Portal:

It allows customers to manage cases and view solutions/knowledge.

 

5. Salesforce Account to learn

https://developer.salesforce.com/signup

https://login.salesforce.com/

 

6. Create Salesforce App:

Gear icon, click on Set up--> in quick find, search for app manager.

Build->Create->Apps->click on New

7. Create User in SF:

 A user is anyone who logs in to Salesforce. Users are employees at your company, such as sales reps, managers, and IT specialists, who need access to the company's records.

 Every user in Salesforce has a user account. The user account identifies the user, and the user account settings determine what features and records the user can access. Each user account contains at least the following:

Username, Email Id, User's First and Last Name, License, Profile, Role (optional)

 Set up--> in quick find, type user--> click on new user and provide details

8. Create Role:

 Role: We may offer record-level access using roles, such as organization-wide defaults, Role hierarchy, sharing rules, and manual sharing. Simply put, record-level access is influenced by responsibilities.

 Set up--> in quick find, type Role --> click on a new role and give the role name

9. Create Profile:

Profile: 

A profile is like settings and permissions in Salesforce. It is used to perform different functions that are defined by users. It is another way to manage records.

There are two types of profiles:

·         Standard profiles: Profiles created by Force.com

·         Custom profiles: Profiles created by users

Salesforce standard profiles are:

·         Standard User

·         Solution Manager

·         Marketing User

·         Read-only

·         System Administrator

 Set up--> in quick find, type Profile --> click on a new role and give the Profile name.

10. Create Object:

In order to store the data for the data members of the class, we must create an object.

Set up--> in quick find, type object manager--> click on a new create and give the object details.

11. Queues:

Queues help your team to manage leads, cases, service contracts. Record is placed in queues automatically by automatic assignment rules(lead/case) from these users in queues work on that record.

12. Public Group:

The public groups are set of users. Users can be another group, individual, particular role in territory.

Public groups are used for primary security and to share data.

 Securities in Salesforce.

SF has basically 4 types of securities.

• OWD: (Org wide default): To share/give access over org-wide.

Private, Public read-only, public read/write

Role hierarchy: Bases on roles giving access. Sales Manager, Manager, VP, CEO, etc.,

 Sharing Setting:  To use sharing setting we need to keep in mind that

• What to share
• Whom to share
• What type of access need to share

Sharing setting can be done in 2 ways: Manual sharing and Criteria based sharing

Manual sharing: Manual sharing can be used by the owner of the record to share with someone they need.

 

 13. Lead Management:

Leads are people, companies that are identified as potential customers.

Leads are generated by happy customers and web-to-lead forms.

Lead à opportunity à Accounts à contacts.

 

14. Lead Assignments:

The process of distributing incoming leads among sales reps using lead assignments or lead routing.

Leads assignments can be done by territory, industry, deal size and others.

 

15. Case Assignments:

The case is a customer’s question that can be enrooted to a particular support team or customer service.

Tools help is case assignments are,

a)       Queues: Automatically prioritize support team to jump and resolve the issue.

b)      Assignment rules: Automatically assign cases to a specific agent.

c)       Auto-response rule: Automatically send emails responses to customers based on case details.

d)      Escalation rule: Automatically escalates cases to right people when cases aren’t resolved in a certain time.

e)      Macros: Automatically complete repetitive tasks on cases like selecting email templates.

 

 

16. Custom Metadata types in SF?

Ans: Custom Metadata types are objects used to define a structure for application metadata.

Fields and values in the metadata types are metadata, not data. Metadata is pretty handy to imported into SF, modified in the interface, and manipulated using metadata API. Instead of storing hard coded data custom metadata let you configure the app by reusable functionality that determines behavior based on metadata and can be customized using declarative tools.

Uses Creates association between different objects, use in Apex code, use in extension packages.

Fileds supported by metadata types are Checkbox, data, date/time, number, picklist, text, text area, and URL.

 

17. Custom Label:

The custom label enables developers to create a multilingual app by automatically presenting info in users' native language. a custom label is custom text values that can be used in Apex code, VF pages, Lighting components, and lighting pages.

18. Reports:

Reports are used to display and export data from SF org. Every report is stored in a folder and these folders can be hidden, public, and shared and can be set to read-only, read-write access. Access to reports and folders can be controlled by roles, permissions, public group, and license type.

Type: Tabular, Joined, Matrix, Summary.

19. Dash Boards:

Dashboards are visual displays of key metrics and trends for records in org. Dashboards are also having access as same as reports. 20 components can be added to the one dashboard.

Types: Table, Vertical, Horizontal, gauge, metric, pie, donut, funnel, scatter chart, etc

 

20. Report Type:

Report types are templates that make reporting easier. Report types determine which fields and objects are available for use when creating reports. Report types create relations between objects and fields also allow to add.

21. Page Layouts:

Page layout controls the layout of an object. It defines which fields the user can view and edit while entering the data in sObjects. It contains a different set of Fields, Buttons, Related Lists, Custom Links, Visual force pages on the objects record page. It is used to assign field accessibility.

Go to Setup-> Build-> Customize-> ObjectName-> Page Layouts

22. Record Types:

Record types let you offer different business processes, picklist values, and page layouts to different users. You might create record types to differentiate your regular sales deals from your professional services engagements, offering different picklist values for each

 

23. Workflows:

Workflow in Salesforce is basically a container or business logic engine which automates certain actions based on particular criteria. If the criteria are met, the actions get executed. When they are not met, records will get saved but no action will get executed.

For more info: https://intellipaat.com/blog/tutorial/salesforce-tutorial/workflow-rules-in-salesforce/

24. Approval process:

Approval process automates SF records are approved in org. we need to specify steps necessary for a record to be approved and who approves it at each step also actions to consider like field update and send notification.

The approval process is 2 types.

• Jump Start – use for the single and simple approval process.
• Standard setup- use for complex or business solutions.

25. Process Builder:

Process Builder Salesforce is basically an automated tool that allows you to control the order of actions or evaluate the criteria for a record. It has eight actions associated with it:

Creating records: This will allow you to create a new record and add different field values for it.

·         Updating records: You can update one or more records that are somehow related to the record that started the process. This can be done either by manually entering records or by using the records from a related record.

·         Posting on Chatter: Process Builder allows you to post on Chatter for sharing any information to any user.

·         Quick action: If you already have global actions or objects, within Salesforce, you can use Quick action to use them in any record.

·         Launching/triggering the flow: It is possible for you to launch the flow from your process to automate different processes.

·         Submitting the record automatically for approval: The record that started your process can be submitted. Any other record cannot be automatically submitted.

·         Calling/triggering Apex code: You can invoke an Apex code that you have already written within Salesforce.

·         Invoking another process: This action will actually invoke a process to another process.

26. Flows:

In Salesforce, a flow is an application that automates complex business processes. Simply put, it collects data and then does something with that data.

Flow Builder is the declarative interface used to build individual flows. Flow Builder can be used to build code-like logic without using a programming language.

Flows fall into five categories:

Screen Flows: These are flows that have a UI element and require input from users. These types of flows are either launched as an action or embedded as an element on a Lightning page.

Schedule-Triggered Flows: These auto launched flows launch at a specified time and frequency for each record in a batch, and they run in the background.

Auto launched Flows: Run automated tasks with this flow type. Auto launched flows can be invoked from process builder, from within an Apex class, from a set schedule, from record changes, or from platform events.

Record-Triggered Flows: These auto launched flows run in the background when a record is created, updated, or deleted.

Platform Event-Triggered Flows: When a platform event message is received, these auto launched flows runs in the background.

Salesforce order of execution

System Validation Rules.

Executes record-triggered flows that are configured to run before the record is saved.

Executes all before triggers.

Custom Validation rules.

Executes duplicate rules.

Saves the record to the database, but doesn’t commit yet.

Executes all after triggers.

Executes assignment rules.

Executes auto-response rules.

Executes workflow rules.

Executes escalation rules.

If there are workflow field updates, updates the record again.

If the record was updated with workflow field updates, fires before and after triggers one more time. Custom validation rules, flows, duplicate rules, processes, and escalation rules are not run again.

Executes processes and flows launched via processes and flow trigger workflow actions.

Executes entitlement rules.

Executes record-triggered flows that are configured to run after the record is saved.

If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.

If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.

Executes Criteria Based Sharing evaluation.

Commits all DML operations to the database.

Executes post-commit logic, such as sending email.