[shariq]

To ensure that your code meets certain standards, Apex Code coverage shows you how many executable lines of code in your classes and triggers have been exercised by test methods. Code coverage percentage is a calculation of the number of covered lines divided by the sum of the number of covered lines and uncovered lines. The minimum test coverage required to deploy to production is 75%

[shariq]

Salesforce runs on a multitenant environment which means resources (Storage, CPU, Memory) are shared with other companies on the Salesforce platform. This means limits must be in place to ensure that all companies using the Salesforce architecture abide by certain rules and don’t let their code or processes monopolize shared resources. A few examples of Governor Limits are:

Total number of records retrieved by a SOQL query – 50,000
Total number of SOQL queries issued – 100 (Synchronous) 200 (Asynchronous)
Total number of DML statements issued – 150
Total number of callouts (HTTP requests or Web services calls) in a transaction – 100
Maximum CPU time on the Salesforce servers – 10,000ms (Synchronous) 60,000ms (Asynchronous)

[shariq]

Apex Triggers can either run before a record has been saved of after. A before operation is usually used to verify information that is going to be inserted, and after trigger is used to access data that has previously been entered by a user or system.

[shariq]

Apex cannot be customised in a production Org, it must be changed and deployed through a sandbox and meet test coverage. Visualforce, on the other hand, may be customised directly in production (Although this is not best practice)

[shariq]

Apex is a strongly typed, object-oriented programming language that allows developers to extend the Salesforce platform by writing their own business logic into the platform. Apex looks similar to Java and can be launched through a variety of user-initiated events such as record updates, button clicks, triggers on objects, or external web service requests.

[shariq]

Bucket fields can be used in Salesforce reports to group together field values. These fields are not created on the Salesforce platform and only exist in in the report itself.

[shariq]

There are various ways to deploy from Sandbox to Production. The main way is to use a Salesforce feature called Change Sets. These allow you to package up components and then deploying them to another Salesforce Org. There are various other methods including ANT MIgration Tool, Force.com IDE and Unmanaged packages

[shariq]

Salesforce.com is SaaS (Software-as-a-Service) product while Force.com is a PaaS product (Platform-as-a-Service). Salesforce.com has a selection of prepackaged solutions such as the Sales & Service Cloud that are designed for a specific purpose. While Force.com allows you to build your own applications. Salesforce.com is built on the Force.com platform.

[shariq]

SOQL stands for Salesforce Object Query Language. It is very similar to the widely used language SQL (Structured Query Language), to query databases. SOQL is specifically designed for Salesforce data and is used to query the Salesforce platform to retrieve data. SOQL is used within Apex & Visualforce to return sets of data.

[shariq]

There are three main relationship types in Salesforce…

A lookup relationship can be used to link two objects together. It is the most basic type of relationship that creates a child-parent relationship between two objects.

A master-detail relationship can also be used to link two objects together. A master-detail relationship creates a tight relationship between the parent and the child. The child record inherits security of the parent, and if the parent is deleted, all associated child records will also be deleted. Master-detail relationships created some extra functionality such as roll-up summary fields that allow you to calculate data on the parent from the children.

A many-to-many relationship (Also referred to as a junction object), allows you to create a relationship between two objects that need to model a many-to-many relationship. These are created with an object that has two master-detail relationships to two parent objects.

[shariq]

yes Lightning work with Visualforce.

[shariq]

Yes. Salesforce Lightning Design System.

[shariq]

Not necessarily, We can start with a Component bundle.

[shariq]

we can deploy component by using managed packages, Force.com IDE, Force.com Migration Tool or Change Sets.

[shariq]

Lightning Experience is the name for the all new Salesforce desktop app, with over 25 new features, built with a modern user interface and optimized for speed.

[shariq]

Because of the security issue as Application Event can be handled by any component so sensitive data be compromised

[shariq]

Yes. With the help of lightning:navigate tag and then use the page reference in JS Controller.

[shariq]

A lightning tag has inbuilt SLDS we do not need to put extra effort to improve the look and feel, also it has may awesome tags to handle the Error or bad inputs. Error handling is very easy for lightning tags.

[shariq]

Avoid Server Calls: – Main advantage of Salesforce Lightning is that we can avoid many server calls while working with Lightning Components and reason behind this is JS controller using JS we can manipulate the data into the controller and display as per our need.
Lazy Loading to increase performance – another awesome feature which loads/display the particular component or particular part of the component whenever users want to load not unlike the VF page. And because of lazy loading, it increases the performance and data will reflect on the fly. Uses a stateful client and stateless server architecture that relies on JavaScript on the client side to manage UI component metadata and application data.

Faster Development: – Empowers teams to work faster with out-of-the-box components that function seamlessly with desktop and mobile devices. Building an app with components facilitates parallel design, improving overall development efficiency.
Device-aware and cross-browser compatibility: – Apps use responsive design and provide an enjoyable user experience. The Lightning Component framework supports the latest in browser technology such as HTML5, CSS3, and touch events.

Lightning App Builder: – Empowers the team/company/individual to develop the complete application without writing a single line of code using out of box functionality and this application will work well into Salesforce1 as well.
Event-driven architecture: – Uses an event-driven architecture for better decoupling between components. Any component can subscribe to an application event, or to a component event they can see.

SLDS: – SLDS means Salesforce Lightning Design System that gives you the power to style the component in your way, develop component as per your look and feel and you do not need to worry about responsive behavior it will take care all itself.

2 Way Binding: – It one of the Salesforce lightning feature that made me “Wow”and yes it is two-way binding Changes in the application state have been automagically reflected into the view and vise-versa. In fact, we could build our own directives with two-way data bound scope properties, by setting a configuration value.

Avoid ViewState Error: – Another awesome feature is that we will never get view state error while working with the lighting component.

Lightning OUT: – Here comes the true power of Salesforce Lighting that is lightning OUT which gives you the power to take your lightning component to an external site and this is the thing that enables you to show Lighting Component into VF page.

[shariq]

Document: – A description, sample code, and one or multiple references to example components
Client-side renderer to override default rendering for a component.

[shariq]

Yes, using lightning out the functionality of the salesforce lightning component.

Key points to remember: –

use <apex:includeLightning /> tags at the beginning of VF page This component loads the JavaScript file used by Lightning Components for Visualforce.
Lightning App must extend ltng:outApp library/interface.
We can use $Lightning.use() many times into VF page but that must reference the same lightning app.
We can only call those components that are referenced into the app.
LightningOutDemoApp.app

<aura:application access=”Global” extends=”ltng:outApp” >
<c:AccountList ></c:AccountList>
</aura:application>

Description of above code

access: – determines, if we can use the component throughout the Salesforce org or not acceptable values, are global, public, private

ltng:outApp: – Extending from ltng:outApp adds SLDS resources to the page to allow your Lightning components to be styled with the Salesforce Lightning Design System (SLDS). If you don’t want SLDS resources added to the page, extend from ltng:outAppUnstyled instead. using ltng:outApp we can access our lightning component into VF page or any external site.

AccountListVF.vfp

<apex:page >
<apex:includeLightning />

<– div where we will embed our lightning component –>

<div id=”lightning” />
$Lightning.use(“c:LightningOutDemoApp”, function() {
$Lightning.createComponent(“c:AccountList”,
{
“VFpageValue” : “Woohoooo, Lightning Out is an amazing feature of Salesforce Lightning”
},
“lightning”,
function(cmp) {

});
});

</apex:page>

$Lightning.use(): – Refer the lightning application that we are using.

$Lightning.createComponent(): – Used to dynamically creating the lightning component.

[shariq]

force:appHostable

[shariq]

Executing apex test classes.

[shariq]

Pinnacle: ActionPoller is utilized to call an Apex technique for the interim of time indicated.
Summit: Action Function is utilized to call Apex strategy from JavaScript.
Utilizing set Timeout in JavaScript, we can accomplish apex: actionPoller functionalities.

[shariq]

We can get the Account Id from the Contact and we can create an Opportunity under the Account