[MOHIT]

This is the Syntax for Spinner:

Component:

<aura:component>
<div class="exampleHolder">
<lightning:spinner alternativeText="Loading" size="small" />
</div>
<div class="exampleHolder">
<lightning:spinner alternativeText="Loading" size="medium" />
</div>
<div class="exampleHolder">
<lightning:spinner alternativeText="Loading" size="large" />
</div>
</aura:component>

 

 

And it's CSS is:

 

.THIS.exampleHolder{
position: relative;
display: inline-block;
width: 80px;
height: 80px;
}

[MOHIT]

hii,

Syntax to call Child Component in Parent component is :

<c:childComponent aura:id=’childCmp’ />             – Use this Syntax if no namespace is defined by you.

<yourNameSpace:childComponent aura:id=’childCmp’ />   Use this Syntax if you have your own  namespace is defined by you.

[MOHIT]

we used handler class in trigger in Salesforce because it:

facilitates logic-less triggers and One Trigger Per Object, which itself has many benefits(including fine grained control over order of execution)
improves readability and Separation of Concerns(this improved readability makes version control more fruitful as well)
optionally facilitates selective disablement

[MOHIT]

These are global Value Provider

 

globalID

$Browser

$ContentAsset

$Label

$Locale

$Resource

[MOHIT]

In Salesforce  Lightning Component Apex are used in server-side and JavaScript are used on client-side.

[MOHIT]

By selecting the “All Time” in the “Range” on the page.

[MOHIT]

We can create two types of Apps in Salesforce

Custom app: This type of apps can be used in every business scenario. It is widely used in the market.

Console app: This type of app can be used only in the client service business, where we focus on solving the client’s issues. It is not comparatively, widely used in the market.

[MOHIT]

Ans: The following are the major subsidiaries of Salesforce:
Tableau
Pardot
Heroku
Mulesoft
Demandware Inc
SalesforceIQ

[MOHIT]

The framework supports client-side (JavaScript) and server-side (Apex) controllers. An event is always wired to a client-side controller action, which can in turn call an Apex controller action. For example, a client-side controller might handle an event and call an Apex controller action to persist a record.
Server-side actions need to make a round trip, from the client to the server and back again, so they usually complete more slowly than client-side actions.

[MOHIT]

A standard field record name can have data type of either auto number or text field .

[MOHIT]

Yes, we can call one lightning component from another component.

• This reply was modified 4 years, 10 months ago by  Forcetalks.

[MOHIT]

Hii Manish,

• XML stands for eXtensible Markup Language.
• XML is a markup language much like HTML.
• XML was designed to store and transport data.
• XML was designed to be self-descriptive.
• XML is a W3C Recommendation.

[MOHIT]

Hai Anjali,

The class can be deployed on 0% coverage as well, but overall coverage of your production org after getting your code deployed should be 75%, otherwise, Salesforce won’t let you deploy your code.

• This reply was modified 4 years, 10 months ago by  Forcetalks.

[MOHIT]

Hai Anjali,

Every trigger you are trying to deploy should have at least 1% coverage, but yes overall coverage of your production org after getting your code deployed should be 75%, otherwise, Salesforce won’t let you deploy your code.

• This reply was modified 4 years, 10 months ago by  Forcetalks.

[MOHIT]

Thanks Anjali.

[MOHIT]

Lightning is a framework which is based on component model which helps to build our app faster. Lightning framework basically put together different components which result in faster app development because we are reusing the existing component.

 

[MOHIT]

Yes, Aggregate query is to optimize the code. But It has limitations.

[MOHIT]

No, I think it’s a component-based framework.

[MOHIT]

We can convert a master-detail relationship to a lookup relationship as long as no roll-up summary fields exist on the master object.

We can convert a lookup relationship to a master-detail relationship, but only if the lookup field in all records contains a value.

[MOHIT]

These are the fields that are automatically indexed in Salesforce :

Name

Email (for contacts and leads)

Division

CreatedDate

Systemmodstamp (LastModifiedDate)

Foreign key relationships (lookups and master-detail)

RecordTypeId

[MOHIT]

apex:inputText: An HTML input element of type text. Use this component to get user input for a controller method that does not correspond to a field on a Salesforce object.

This component doesn’t use Salesforce styling. Also, since it doesn’t correspond to a field or any other data on an object, custom code is required to use the value the user enters.

apex:inputField: An HTML input element for a value that corresponds to a field on a Salesforce object. The <apex:inputField> component respects the attributes of the associated field, including whether the field is required or unique, and the user interface widget to display to get input from the user. For example, if the specified <apex:inputField> component is a date field, a calendar input widget is displayed. When used in an <apex:pageBlockSection>, <apex:inputField> tags automatically display with their corresponding output label.

[MOHIT]

System.Assert accepts two parameters, one (mandatory) which is the condition to test for and the other a message (optional) to display should that condition be false.
System.AssertEquals and System.AssertNotEquals both accept three parameters; the first two (mandatory) are the variables that will be tested for in/equality and the third (optional) is the message to display if the assert results in false.

[MOHIT]

Total heap size Synchronous Limit: 6 MB  - Asynchronous Limit: 12 MB
and Email services heap size is 36 MB.

[MOHIT]

apex:panelBar is used to insert headers in visualforce page While <apex:panelBarItem> tag is used as a child item for <apex:panelBar> tag.

[MOHIT]

Apart from standard Visualforce markup, the body of an <apex:component> tag can also specify the attributes that can be passed in to the custom component when it’s used in a Visualforce page. The values of such attributes can then be used directly in the component, or within the component’s controller, if applicable. They can’t, however, be used in the constructor of the component’s controller.