Top Asked Salesforce Admin Questions and Answers
1. How can you grant access to the profile to the user?
Ans: Security control -> Delegated Admin, Add user to here.
2. what are Custom Metadata types in SF?
Ans: Custom Metadata types are objects used to define a structure for application metadata.
Fileds 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.
3. 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.
4.Territory Management:
TM is helpful to improve sales and boost team competition. TM helps in assigning accounts to a particular sales rep for that territory(Geographic region). TM can be implemented by knowing the territory, territory type, priority model, and hierarchy.
5. Queues and Public Group:
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.
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.
6. Duplicate Management:
Duplicate management helps users not to create duplicate records.
the two important ways of controlling duplicate records in SF are
a) Matching rule: Matching criteria to identify duplicate records.
b) Duplicate Rule: Duplicate rule helps users not to create duplicate records by configuring duplicate management.
7. 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.
8. 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
9. 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 allows to add.
10. Dynamic Dashboard.
Dashboard for which Running user is always the logged-in user.
11. Page Layouts:
Page layout is about controlling and arranging fields, buttons, custom links, quick actions on the object record page. In page layout, the fields can be given access like read-only, required, visible, and edit access.
12. Record type:
Record types are most convenient to offer different subsets of picklist values or page layout for the user. These are based on user profile
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 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 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. Securities in Salesforce.
SF has basically 4 types of securities.
- OWD
OWD: 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 by 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.
17.Portals in Salesforce:
We have 3 portals in SF.
- Customer Portal:
The customer portal provides customers
with an online channel to communicate with customers' executives and solve their
issues. They help to streamline communication and provide easy and fast
solutions. The customer portal is to support customers.
- Self-Service Portal:
Self-Service Portal let users resolve their issues on their own by redirecting to the right FAQ’s, blogs, technical
documents, videos, etc.
- Partner Portal:
The partner portal is to support your
partners. Partners users are SF users with limited access to your org data and
log in via the partner portal. Partner portal exposes the leads and opportunity
objects and can convert to opportunity.
18. Community Cloud:
Community cloud is an online social platform from SF that
enables companies to connect customers, partners, employees with each other and
can share data and can work.
19. Data Loss in Salesforce:
* Changing field value from data type like % to number, Text
area to email, phone and URL etc
* Accidental or malicious deletion by users
* Bad code
* Data imports
* SOQL mistakes
* Integration of API’s calls
20. Edition of salesforce: Unlimited.
21. Limits:
* SOQL -100
* SOSL-20
*DML-150
*Send email methods-10
*callouts in transactions-100
*Heap size-6-8 MB
22. De-Duplication tools:
To de-duplicate records in SF org, we can use the below tools.
- Demand Tools
- Ring Lead
23. Order of execution in SF:
a) System validation rules
b) Before triggers
c) custom validation
d) duplicates rules
e) after triggers
f) assignments rules
h) auto-response rules
i) workflow rules
k) Process builder
l) Escalation rules
24. Custom setting:
Custom settings are similar to a custom object. Custom setting
data can be used by formula fields, validation rules, flows, apex, and soap API.
To avoid governing limit we can use custom settings. It allows us to store a set
of data and access it without querying it from Apex.
Types: List and Hierarchy
List: City, states, zip code of the country.
Hierarchy: Personalized setting for specific profiles or
users. The Hierarchy logic checks the org, profile, and user settings for the
current. The Hierarchy setting for an org is overridden by the profile setting
which in turn are overridden by the user setting.
25. Workflows:
WF is used to automate business processes. WF can be broken
into 2 main components
A)
Criteria (If part)
B)
Action (Then part)
WF is done by evaluation
criteria and rule-based criteria.
While creating WF we see options
like
- Created.
- Created and every time its
edited(No time-dependent wf can be performed)
- Created and anytime its
edited to subsequently meet criteria.
WF Uses:
Assign Tasks
Send Emails
Update fields
Send outbound messages.
26. Outbound Messages:
In wf outbound, messages can be
sent to another system (third party) by using the end pint URL.
In outbound messages
we can send fields values by using the WSDL file and this WSDL file can be
converted to view mode by the third-party system.
27. 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.
28. Flows:
Flows allow us to build complex automation by using clicks
instead of code. Flows are easy to build and can access easily.
The 3 main building blocks of flows are:
- Elements: Performs logical actions such as assignments, decisions,s or loops also there are data
elements to query or commit record change.
- Connectors: Determines which elements lead to which.
- Resource: individual variable data such as a string of text, numbers, records, formulas, or collections.
Comments
Post a Comment