[Deepak]

Hi Udit,

• System debug logs are retained for 24 hours. Monitoring debug logs are retained for seven days.
• If you generate more than 1,000 MB of debug logs in a 15-minute window, your trace flags are disabled. We send an email to the users who last modified the trace flags, informing them that they can re-enable the trace flag in 15 minutes.
• When your org accumulates more than 1,000 MB of debug logs, we prevent users in the org from adding or editing trace flags. To add or edit trace flags so that you can generate more logs after you reach the limit, delete some debug logs.

[Deepak]

Lightning events are fired from JavaScript controller actions that are triggered by a user interacting with the user interface. The communication between components are handled by events.

[Deepak]

Attribute groups enable you to organize your data in Contact Builder. Each attribute group includes a data model consisting of data extensions linked to either the contact record or other data extensions.

[Deepak]

There are various reasons why you should use Apex over declarative automation options: -Workflow rules and Process Builder operations sometimes have feature limitations that can be overcome with Apex. For example, pulling information from an external system.

[Deepak]

The Apex testing framework generates code coverage numbers for your Apex classes and triggers every time you run one or more tests. Code coverage indicates how many executable lines of code in your classes and triggers have been exercised by test methods.

[Deepak]

1. Have your batch class implement Database.stateful
2. Declare some variables that are initialized in the constructor to 0. These variables count successes and errors; also a string variable that remembers the records that failed and why (initialized to empty string).
3. Use Database.update with allOrNothing = false instead of update within execute(). Interrogate each member of Database.SaveResult[] for isSuccess() and count succcesses and failures in your stateful variables from second point. Log in the stateful variable all the errors (id of record, name of record, and error message/exception)
4. In the finish method, send an email to the sysad of count of successes/failures + string variable of all the failures.
5. In finish() method, write your batch results to a custom Log__c record(s

[Deepak]

An app in Salesforce.com is nothing but a container which contains in it - a name, a logo, and an ordered set of tabs.

[Deepak]

An UTM parameters, which are appended to the URL, identifies the marketing campaign that refers traffic to your website. Only the Campaign Source, Campaign Medium, Campaign Name, sfmc_activityID, and Campaign ID parameters are tracked for SMS activities.

[Deepak]

• Insert is a DML statement which is same as Database.insert to insert the record in database. If we use insert DML statement in bulk operation if error occurs in this operation, then execution stop and rollback all the insertion from the database those has been inserted successfully. When error occurs then you can handle this error by try catch block.
• If we use DML database method (Database.insert) to insert/update record in bulk, then if error occurs the remaining records will be inserted/updated means partially operation will be done.

[Deepak]

Reloads the view.
To refresh a view, run $A.get('e.force:refreshView').fire();, which reloads all data for the view.
This example refreshes the view after an action is successfully completed.
refresh : function(component, event, helper) {
var action = component.get('c.myController');
action.setCallback(component,
function(response) {
var state = response.getState();
if (state === 'SUCCESS'){
$A.get('e.force:refreshView').fire();
} else {
//do something
}
}
);
$A.enqueueAction(action);
}

[Deepak]

You can use the same controller class but cannot share data via the controller fields. Lightning Components do not support the view state mechanism that is used in Visualforce (as that design approach tends to lead to unnecessary data being moved to and from the client). Yes, you could use the same controller.

[Deepak]

Use Lightning Components in Visualforce Pages
Add Aura components to your Visualforce pages to combine features you’ve built using both solutions. Implement new functionality using Aura components and then use it with existing Visualforce pages.
There are three steps to add Aura components to a Visualforce page.

1. Add the Lightning Components for Visualforce JavaScript library to your Visualforce page using the <apex:includeLightning/> component.
2. Create and reference a Lightning app that declares your component dependencies.
3. Write a JavaScript function that creates the component on the page using $Lightning.createComponent().

Add the Lightning Components for Visualforce JavaScript Library
Add <apex:includeLightning/> at the beginning of your page. This component loads the JavaScript file used by Lightning Components for Visualforce.
Create and Reference a Lightning Dependency App
To use Lightning Components for Visualforce, define component dependencies by referencing a Lightning dependency app. This app is globally accessible and extends ltng:outApp. The app declares dependencies on any Lightning definitions (like components) that it uses.
Creating a Component on a Page
Finally, add your top-level component to a page using $Lightning.createComponent(String type, Object attributes, String domLocator, function callback). This function is similar to $A.createComponent(), but includes an additional parameter, domLocator, which specifies the DOM element where you want the component inserted.

[Deepak]

Sales Cloud Einstein is your own data science department that learns from your team's sales activities and CRM data and helps you identify the best leads, convert opportunities more efficiently, and retain customers with ease.

[Deepak]

Steps to Enable Salesforce IoT:

1. Launch your Trailhead Playground, click. and select Setup.
2. Enter IoT into the Quick Find box and under Salesforce IoT, select Get Started.
3. In the Enable Salesforce IoT section, click Enable.

[Deepak]

Hi Anjali,
IoT requires that companies invest in these four key segments:
Things: We’ve got this part covered already, but just as a reminder, things are devices, apps, and other objects with embedded electronics, sensors, or software. Once connected, these things can send and receive data.
Connectivity: This refers to evolving plain old “things” into connected things that transmit data over networks and other systems to the cloud. It also refers to how things connect to each other over networks and other systems. Wireless connectivity for devices, sensors, and software is usually provided by the wireless carriers and companies that specialize in this area.
Device management: It takes sophisticated software to manage connected devices, keep their firmware up to date, and store all the data they transmit. Do a simple Internet search and you’ll find more than 300 IoT device management platforms.
Customer experience: Using the data that comes from all the connected things in the land of IoT, you can create new kinds of customer experiences that proactively engage your customers across all lines of business. Including from how you sell to how you service, market, and even build apps. And who lives in this part of the map? Salesforce. Salesforce IoT connects the Internet of Things to the customer experience and the world’s number one CRM. This connection empowers any business, and every trailblazer, to harness data streaming from their network of connected products and reimagine the way they sell, service, market, build apps, and more.

[Deepak]

• Before any Apex callout can call an external site, that site must be registered in the Remote Site Settings page, or the callout fails. Salesforce prevents calls to unauthorised network addresses.
• To add a remote site settings:
• From Setup, enter Remote Site Settings in the Quick Find box, then select Remote Site Settings.

1. Click New Remote Site.
2. Enter a descriptive term for the Remote Site Name.
3. Enter the URL for the remote site.
4. Optionally, enter a description of the site.
5. Click Save.

[Deepak]

Governor execution limits ensure the efficient use of resources on the Force.com multitenant platform. It is the limit specified by the Salesforce.com on code execution for efficient processing.

[Deepak]

An indirect lookup relationship is a new field type introduced with Salesforce Connect. It links an external object to a standard or custom object in the same way that a regular lookup relationship links standard or custom objects.

[Deepak]

Hi Ayush,
<Object>TriggerDispatcher
The trigger dispatcher classes contains the methods to handle the trigger events and this is the place where the developers had to instantiate the appropriate trigger event handler classes.

[Deepak]

Custom object are custom database tables that allow you to store information unique to your organization. Every object may not have tab while if you have a tab (Custom Object) then it implies there is an underlying object. (Note tab can be a visualforce tab as well).

[Deepak]

Hi Anjali,
Dynamic SOQL refers to the creation of a SOQL string at run time with Apex code. Dynamic SOQL enables you to create more flexible applications. For example, you can create a search based on input from an end user or update records with varying field names.

[Deepak]

Create a custom component event using the <aura:event> tag in a .evt resource. Events can contain attributes that can be set before the event is fired and read when the event is handled.
Use type="COMPONENT" in the <aura:event> tag for a component event. For example, this c:compEvent component event has one attribute with a name of message.
<!--c:compEvent-->
<aura:event type="COMPONENT">
<!-- Add aura:attribute tags to define event shape.
One sample attribute here. -->
<aura:attribute name="message" type="String"/>
</aura:event>
The component that fires an event can set the event’s data. To set the attribute values, call event.setParam() or event.setParams(). A parameter name set in the event must match the name attribute of an <aura:attribute> in the event. For example, if you fire c:compEvent, you could use:
event.setParam("message", "event message here");
The component that handles an event can retrieve the event data. To retrieve the attribute value in this event, call event.getParam("message") in the handler’s client-side controller.

[Deepak]

The framework uses events to communicate data between components. Events are usually triggered by a user action. A client-side controller handles events within a component. It's a JavaScript resource that defines the functions for all of the component's actions.

[Deepak]

aura:registerevent is the notifier component and it declares that it may fire a particular event, it includes 'name' attribute which is relevant only to component event and is not used for application event. Other attribute is the 'type' which lets the component know which event would be fired.

[Deepak]

Hi Sumit,
It depends on your purpose:

• If you want a page with many records, using standard list view, and list actions you could use standard list controller:

<apex:page standardController="Account" recordsetVar="accountsList"...> ... </apex:page>

• If you want to use completely custom functionality and don't really need most of the standard object behaviors, custom controller is a good option, but bear in mind, any standard actions you want to use will have to be implemented in your custom class. A page with a custom controller would use the following attribute:

<apex:page controller="MyApexClass"...> ... </apex:page>