[Shweta]

Attribute : It is used to store information to be referenced  in our lightning component code. Attributes on components are like instance variables in objects. It have a name and a type.

<aura:attribute> tag is used  to add an attribute to the component.

Example :

<aura:component>
    <aura:attribute name="message" type="String"/>
    <p>{!'Hello! ' + v.message}</p>
</aura:component>

 

[Shweta]

<apex: pageblocksectionitem> : It is used to define a single piece of data in an page block section that takes up one column in a row. It can include up to two child components.

Example:

<apex:pageBlock title="Block" >
             <apex:pageBlockSection title="my section">
                <apex:pageBlockSectionItem >
                	<apex:outputLabel >My Name</apex:outputLabel>
                </apex:pageBlockSectionItem>       
                 <apex:pageBlockSectionItem >
                	<apex:outputLabel >Address</apex:outputLabel>
                 </apex:pageBlockSectionItem>
            </apex:pageBlockSection> 
        </apex:pageBlock>

 

[Shweta]

@AuraEnabled : It enables client and server side access to an apex controller method. This annotation exposes an apex method to the Aura framework for use in lightning components.

[Shweta]

Event :  It is an action that is performed by the user, while interacting with an app. In Lightning component, event are fired by the JavaScript controller actions. It is declared by the aura:event tag.

Type of Event :

Application Event : It is used when you need two independent component to communicate with each other.

Component Event : It is fired from an instance of a component. It can be handled by the component that fired the event or by a component in the containment hierarchy that receives the event.

 

[Shweta]

<apex:dataList> : It is an ordered or unordered list of values that is defined by iterating over a set of data. This component specifies how a single item should appear in the list.

[Shweta]

keyset() method : It is a method used on map that returns a set that contains all of the keys present in the map.

[Shweta]

OWD : Organization Wide Default.

It is the baseline level of access to data records for all users in an organization and specify which records can be accessed by which user and on which mode. It is used to restrict access to data.

There are four levels of access present in OWD:

• Public Full access : user can view, edit,  transfer and report on all record.
• Public Read/Write : user can edit,  view and report on all record.
• Public Read only : user can search the records, view and report on every record but the user can not edit that record.Only admin can edit that records.
• Private : only that record owner and users above that roles in an hierarchy can view, edit and report on those records.

[Shweta]

Wrapper Class : It is a collection of different Salesforce data types and used to wrap data collected from the present objects to a new object. It displays checkbox and string data types in a single table.

[Shweta]

Metadata : It is a simple lightweight language which based on XML. In Salesforce, It describes the structure of salesforce.com and Force.com development artifacts. The metadata is zipped and transferred to the Force.com servers  where it is unzipped and compiled on your behalf. Zip folder can be securely stored and in future if you need to restore you can deploy the same using workbench in your org.

[Shweta]

Order of Execution in Salesforce runs in the following order:

• Executes all before triggers.
• System validations are performed.
• Custom validations are performed.
• Saves the record but does not commit
• Executes all after triggers.
• Executes assignment rules
• Executes auto-response rules
• Executes workflow rules
• Executes escalation rules
• Commits to the database

[Shweta]

Skinny Table : It is a custom table in the Force.com platform that contains a subset of fields from a standard or custom base Salesforce object. It can improve the performance of  read-only operations.It don’t get copied over to sandbox organizations. It can also contain encrypted data.

[Shweta]

SOAP  and REST API are  used to expose your data from force.com platform to other platforms(like java) or to allow external application to invoke Apex methods.

Soap API : It supports data in the form of XML .

REST API : It supports data in the form of XML and JSON.

 

[Shweta]

Login hour : you can set the login hour with using these steps, From Setup, enter Profiles in the Quick Find box, and select Profiles. Under Login Hours click Edit and set up the schedule.

Login ip range: It control the login access for a user profile. It is used to restrict login IPs at a granular level.

you can whitelist the  IP ranges at the organization level.

[Shweta]

If you want to  find object management setting for Custom objects ( objects that you create to store information ) .

From Setup, enter the name of the appropriate object in the Quick Find box, then select the specific customization. For example, to add a custom field to the Case object, enter Case in the Quick Find box, then select Fields under Cases.

[Shweta]

<apex:outputLabel> : It Is a label for an input or output field . It  provides a label for a controller method that does not correspond to a field on a Salesforce object. This component  supports HTML pass-through attributes using the "html-" prefix. It  is associated with another component via "for" attribute.

<apex:outputText> : It displays text on a visualforce page. Also it escape the rendered text if it contains HTML characters. It can be customized using CSS styles.

 

[Shweta]

Cursors : It is equivalent to the Soql query result set. In cursor a user can have up to 10 query cursors open at a time. If 10 QueryLocator cursors are open in the application and  the same user, attempts to open a new one, then the oldest of the 10 cursors is released. If the client application attempts to open the released query cursor, an error results.

[Shweta]

Recursion occurs when same code is executed again and again. you can avoid it by using Static Boolean variable.

To avoid the recursion on trigger make sure your trigger is getting executed only one time.

Example :  you have to create a class with a static boolean variable with default value true and once you check make the variable false.

Public class check{
private static boolean run = true;
public static boolean runOnce(){
if(run){
run = false;
return true;
}
else{
return run; }
} }

 

[Shweta]

getHost() method is used for get the host name of current running URL.

 

[Shweta]

Before Trigger : It is used for update or validate record values before they’re saved to the database. In this, Database saves the records that fired the before trigger after the trigger finishes execution. If you want to update and delete a record in before trigger , it will give you a runtime error.

Example :

trigger sampleTrigger on Account (before insert) {

for(Account a : Trigger.New) {

a.Fax = 'New Fax'; } }

It updates the Fax field for each account in a for loop.

After Trigger : It can be used to access field values that are set by the database. We can't use After trigger if we want to update a record because it causes a read-only error. if you want to delete the database in after trigger , it will give the runtime error.

[Shweta]

Apex best practices in Salesforce are :

• Bulkify your apex code
• Avoid Query or DML statements inside the For loop
• Bulkify Helper methods
• Streamlining Multiple Triggers on the Same Object
• Use @future Appropriately
• Write Test Methods to Verify Large Datasets

 

 

 

[Shweta]

apex:pageMessage : It  is used to display a  custom message in the page using the Salesforce formatting.

ex : <apex:pageMessage summary="Hello" severity="info" strength="3" />  And

Severity is used for control the display of the message box.

Strength is used for controls the visibility and size of the message box.

[Shweta]

Big object : Object that allows you to stores and manages massive amount of data on the Salesforce platform without affecting performance.  It provide consistent performance for a billion records or more, and are accessible with a standard set of APIs to your org or external system.

There are two types of Big Object:

1. Standard Big Object
2. Custom Big Object

[Shweta]

In Salesforce Classic, you can create four different types of email templates:

1.Text : In this, All users can create or change text email templates.

2. HTML with letterhead :  Admin and users with the “Edit HTML Templates” permission can create HTML email templates based on a letterhead. HTML email templates can inherit the logo, color, and text settings from a letterhead.

3. Custom : Admin and users with the “Edit HTML Templates” permission can create custom HTML email templates without using Classic Letterhead.

4. Visualforce : Admin and developers can create the templates. It  allow for advanced merging with a recipient’s data.

[Shweta]

We can have only one controller at a time either it may be Standard Controller or Custom Controller and multiple controller extensions. There is no limit on the number of extensions you can have on a VisualForce.

 

[Shweta]

1. Insert :  If we use the DML statement insert  in bulk operation and if error occurs, the execution will stop,  and Apex code throws an error which can be handled in try catch block.
2. Database.insert : If we use the DML database method ( Database.insert)  and if error occurs the remaining records will be inserted / updated. It means partial DML operation will be done.