[Shweta]

In Salesforce, We can use SOAP & REST for integration, SOAP will communicate through the WSDL file while the REST will communicate through the HTTP file.

[Shweta]

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.

[Shweta]

<aura:method /> tag is used to define a method as part of a component’s API. It enables you to directly call a method in a component’s client-side controller instead of firing and handling a component event.

[Shweta]

You can display up to 2000 records on a VF page. If you want to display more records beyond the supported limit you have two options for that:
1. you need to enable readOnly attribute value as true or,
2. you can implement pagination in our pages.

[Shweta]

We have two options for pagination inside the Visualforce:
1. Offset Pagination: using Offset pagination, We are limited to 2,000 records.
2. StandardSetController Pagination: Using StandardSetController pagination, we can paginate up to 10,000.

[Shweta]

Standard list controllers allow you to create Visualforce pages that can display or act on a set of records. Examples of existing Salesforce pages that work with a set of records include list pages, related lists, and mass action pages. It can be used with the following objects: Account, Contact, Case, etc.

[Shweta]

Initially, we had to create test data in every test method, because every test method is considered a different transaction with its own governor limits. But with the help of testsetup, You can write a method in the test class, with @TestSetUp annotation applied, and create all your common test data in this method.

[Shweta]

Auto-response rule: It is a set of conditions for sending automatic email responses to lead or case submissions based on the attributes of the submitted record. Applicable leads include those captured through a Web-to-Lead form. Auto-Response rules can be created for the following, Self-Service portal.

[Shweta]

CPQ: In CPQ,
C: C is for Configure
P: P is for Price
Q: Q is for Quote
Using Salesforce CPQ, you and your sales team can go from creating a new opportunity to handing the customer a quote in a matter of minutes. It can help turn your sales team into a lean, mean selling machine.

[Shweta]

We can add or edit a chart from the Report Builder.
1. Click Add Chart in report builder. For existing charts, click Edit Chart.
2. Select a chart type.
3. Enter the appropriate settings on the Chart Data tab for the chart type you selected.
4. Enter the appropriate settings on the Formatting tab.
Click OK.

[Shweta]

component.find() : returns the Aura.Component instance by its local ID. If the Aura.component local ID is unique, it returns the component, and if there are multiple Aura.component with the same local ID, it returns an array of the components.
Syntax: component.find("auraid");

[Shweta]

The scrollable utility is used when you need to provide scrolling within a section of a page. For example, when the content within an element exceeds either the width or height of the element, applying .slds-scrollable--y provides a vertical scrollbar, while .slds-scrollable--x adds a horizontal scrollbar.

[Shweta]

There are four types of dashboard components in Salesforce:
1. Table: It is used to show a set of report data in column form.
2. Chart: it uses when you want to show data graphically.
3. Gauge: It uses when you have a single value that you want to show within a range of custom values.
4. Metric: It uses when you have one key value to display.

[Shweta]

Namespace prefixes are used in managed packages to differentiate custom object and field names from those in use by other organizations.
Example: Let's suppose two companies are making an app and both companies create a custom field on the contact object called Name. Each company has its own unique namespace, which prefixes the names of all of its components. Company A's name field might actually be called CompanyA__Name__c, which makes it different from company B's name field.

[Shweta]

event.preventDefault(): It is used to prevents the execution of any of the handlers in the default phase.

[Shweta]

Here is the Sample code which you can use to remove the ',' if there is any at the end of your string.
string teststring = 'Myteststring,' ;
if(teststring.endsWith(','))

{teststring= teststring.substring(0,teststring.length()-1);
system.debug('@@@' + teststring);
}

[Shweta]

It is not possible for triggers to ignore validation rules without adding custom logic. If the request to save a record originates outside of a Standard UI edit page, any before triggers you've defined will run prior to the execution of validation rules.
Here is strategy to bypass this behavior:
1. Add a "Skip Validation" Checkbox field to the object
2. Set the "Skip Validation" field to TRUE in a before trigger.
3. Add logic to your validation rules so that they do not execute if "Skip Validation" is set to TRUE.

[Shweta]

DataTypes : In Apex, all variables and expressions have a data type, such as sObject, primitive, or enum.
Variables: Local variables are declared with Java-style syntax. As with Java, multiple variables can be declared and initialized in a single statement.

[Shweta]

Bucket field: It is an incredibly powerful functionality used to quickly categorize values for a field in a report without the need to have a custom formula field at the object level.

[Shweta]

Dynamic Dashboard: It enables multiple users to access a dashboard that was previously accessed only by a single static user. It means that the dynamic dashboard can be used by a specific user alongside a logged-in user, and display data specific to both users accordingly.
You can't schedule refreshes for dynamic dashboards. They must be refreshed manually.

[Shweta]

Recursive Trigger: If a trigger is called again and again than it is called a recursive trigger.
To avoid recursive triggers we can create a class with a static Boolean variable with default value true. e.g.
public Class checkRecursive{
private static boolean run = true;
public static boolean runOnce(){
if(run){
run=false;
return true;
}else{
return run;
}
}

[Shweta]

getter method: This method will return a value to a visualforce page whenever a name variable is called.
Setter method: This will take the value from the visualforce page and stores to the Apex variable name.

[Shweta]

getQuery(): It is used to instantiate the Database.QueryLocator object. This is useful when testing the start method and the start method automatically locks the set of records in the batch.

[Shweta]

App: An app is a group of tabs that work as a unit to provide application functionality.
Package: A package is a bundle/Collection/container for a list of components or a related applications.

[Shweta]

It returns the token for the sObject corresponding to this ID. This method is primarily used to describe information.