Salesforce Interview Questions with Answers Part 61

Salesforce Interview Questions with Answers Part 61

1. Classic vs Lightning Knowledge in Salesforce
Classic Knowledge
Article Types are used for showing differnt buttons and fields.

Lightning Knowledge
Looks similar to regular objects.
Record Types are used for showing differnt buttons and fields.
Agent Search tab helps to search articles. Filters are available in the left pane.

2. Lightning Knowledge in Salesforce
Looks similar to regular objects.

Record Types are used for showing different buttons and fields.

Agent Search tab helps to search articles. Filters are available in the left pane.

Article Category is for visibility requirements.

Approval works only for Draft articles.

3.Einstein Search in Salesforce
Search results are personalized based on record ownership, recent activity, geography, etc.

It allows us to hover. When we hover the suggestion, it will show additional information. Shows Page-level record actions, related list quick links and list views.

If you search “my open opportunities”, it will show all your owned opportunities in open Stages(Negotiation, Discovery, Qualification, etc).
If you search “open opportunities”, it will show all the opportunities in open Stages(Negotiation, Discovery, Qualification, etc) you have access to.
If you search “my open opportunities in Miami”, it will show all your owned opportunities in open Stages(Negotiation, Discovery, Qualification, etc) where city is Miami.

We can use my, all, my team, my account team, my sales teams, colleague’s name, etc during search.

If you search “acme contacts”, it will show all the contacts which belongs to Acme Account. If there are multiple Acme accounts, you can click Looking for different acme? and select a different account.

Supports different search layouts for every profile for every object.

4. When calling apex GlobalDescribe on a standard object fails?
Calling apex GlobalDescribe on a standard object fails for standard objects added to the API in versions after the version of your apex class.

5.What Is A Gack?
If you’ve been around Salesforce long enough, you have probably encountered a screen saying “An internal server error has occurred.”
That screen is what we call a GACK.
This message is part of an elaborate system for efficiently bringing these events to the attention of R&D.

On gack notification, you will see two numbers.
The first of these numbers has a hyphen in it, and the second number is in parentheses.
These two numbers are the identifying ID for that specific event, and the general stack trace that was produced by that failure.

6. What Is Apex Replay Debugger?
Apex Replay Debugger is a free tool that allows you to debug your Apex code by inspecting debug logs using Visual Studio Code as the client. Running the replay debugger gives you the same features you expect from other debuggers.

7. What Is Apex Interactive Debugger?
Apex Interactive Debugger, also included in the Salesforce Extension Pack, allows customers to debug their Apex code on sandboxes and scratch orgs, in real time, using Visual Studio Code as the client.

Apex Interactive Debugger also comes with features for independent software vendor (ISV) partners working with subscribers who install a managed package. Because of the protections against seeing managed code, subscribers can’t debug ISV code in their orgs. With ISV Customer Debugger, an ISV can work with a subscriber to debug issues specific to the subscriber’s org.

8. What are continuous integration, continuous delivery, and continuous deployment?
Continuous Integration
Using continuous integration, a product is built to include and integrate every code change on every commit (continuously), by any and all developers. An automated build then verifies each check-in, letting teams detect problems early.
Continuous integration (CI) is a component of the continuous delivery process that enables developers to integrate their updates into the master branch on a regular basis.
With CI, automated tests run before and after each change is merged, validating that no bugs have been introduced.

Continuous Delivery
Continuous delivery ensures that code can be rapidly and safely deployed to production by manually pushing every change to a production-like environment. Since every change is automatically delivered to a staging environment, you can deploy the application to production with a push of a button when the time is right.
The additional step of pushing the code to a staging environment is what makes continuous integration different than continuous delivery. Having a green (successful) build with CI doesn’t mean your code is production ready until you push it to a staging environment that matches the final production environment.

Continuous Deployment
Continuous deployment is the next step of continuous delivery. Using Continuous Deployment, every change that passes the automated tests is deployed to production automatically.

9. var and let difference in JavaScript
var is a function-scoped. It can be re-declared.
let is a block-scoped. It can be used in for loops, while loops, if blocks. It cannot be re-declared.

Best Practice:Do not use var in for/while loop, because after the loop, it will hold the value due to it’s availability.
var can be considered to be defined a global variable in the function scope. 

10.  Modular programming
Modular programming involves breaking your code up into logical chunks so that it’s easier to access. Using modules generally results in code that is easier to read and maintain.

11. Heroku Connect
 Heroku Connect provides both data replication and data proxies for Salesforce. Data replication synchronizes data between Salesforce and a Heroku Postgres database. Depending on how it’s configured, the synchronization is either one way or bidirectional.
One of the biggest benefits of using Heroku Connect for data replication is that a subset of Salesforce data is quickly and easily accessible to an app on Heroku.

12. Record Sharing in Partner Community 
1. Communities can have separate OWD through Default External Access.

2. Role Hierarchy can be set using “Number of partner roles” under Community Settings.
Note: Maximum Number of partner roles can be set to 3.

3. Sharing Rules can be created. Supports both Criteria Based and Owner Based sharing rules.

4. Sharing Sets can be used –

5.  Owner of the account(Channel Sales Manager – Usually an internal Salesforce user with full Salesforce license) have access to all the records associated to it.

6. Account Relationships and Account Relationship Data Sharing Rules-

13. Live Agent
Live Agent API Endpoint URL is available in Live Agent Settings.

Enable Live Agent check box on the user record.

1. Create Skills.
2. Create Chat Button.
Chat Button – Standard Chat Button
Automated Invitation – Pop Up Chat Button
Customer Time-Out(seconds) – End Chat after time-out
Cusotmer Time-Out Warning(seconds) – Warning for customer for inactivity

Chat Routing Options –

3. Live Agent Configurations
Sneak Peak Enabled – Enable it to show “Typing”
Notifications Enabled – Indicates whether to display a desktop alert when an agent receives a new chat request.
Visitor Blocking Enabled – Indicates whether an agent can block visitors from an active chat within the Salesforce console.
Assistance Flag Enabled – Indicates whether an agent can send a request for help (“raise a flag”) to a supervisor.
Chat Conferencing Enabled – Indicates whether agents can invite other agents to join them in customer chats.

3. Create Deployments.
Allow Access to Pre-Chat API – Allows to use VF page for pre-chat form

1. Works only with Console App.
2. Make sure Include Live Agent in this App check box is enabled to have Live Agent in the app.
3. When an agent accepts a transferred chat, only the chat is transferred to the agent.
Ownership of related records, such as a case, aren’t transferred to the agent.

Live Agent Supervisor tab access is required to view as Supervisor.
Supervisor can sneak peak if it was enabled.
Supervisor can whisper messages to the agent if it was enabled.

14. In Omni-Channel, Assignment Rules, Auto-Response Rules, Escalation Rules, and Workflow Rules trigger policy
Automation rules, such as assignment, auto-response, escalation, and workflow rules, aren’t triggered when Omni-Channel routes a work item to an agent and the agent accepts the work.

When an agent accepts the work and then edits and saves the work item record, automation rules are triggered.

15.What is the difference between Live Agent and Embedded Service/Snap-Ins?Embedded Service chat (formerly known as snap-in)
Live Agent
Live Agent connects customers with your support agents through web-based chat.
In order to browse the website when they are chatting with the agent, they have to minimize the chat window. But, in embedded service, chat stays on the same window even when they navigate and browse the website.

Embedded Service/Snap-Ins
This uses Live Agent but, with a simpler setup.
Lightning Experience must be enabled to set up Embedded Service.
Users can get answers to their questions by chatting with an agent while browsing the site.
After you’ve set up Chat and Omni-Channel to work together in Lightning Experience, give your customers a better chat experience with Embedded Service and Einstein Bots. Embedded Service lets you create a pre-chat form and custom branding with little to no code. Embed the chat window on your website and both your desktop and mobile customers can have the same chat experience. Einstein Bots lets you connect customers to an automated chat bot to answer questions and solve straightforward issues.

Leave a Reply