[Shweta]

Company settings: It is a collection of global attributes to describe the organization using Salesforce. It consists of company, currency, fiscal year, support, and locale settings.

[Shweta]

1. From SetUp -> Click Email Administration -> Click Deliverability
2. Set Access to Send Email (All Email Services) Access Level to No Access
3. Click Save.

[Shweta]

1. From Setup -> Enter Test Deliverability in the Quick Find box -> select Test Deliverability.
2. Enter your business email address.
3. Click Send. Salesforce sends a test message from all IP addresses to your business email address. Each test message specifies the IP address from which it was sent.
4. To make sure that you received all test messages, check your business email account.

[Shweta]

Email deliverability is the likelihood of a company’s or individual’s email reaching its intended recipient. Just keep in mind the below points when setting email deliverability:
No access: Prevents all outbound emails to and from users.
System email only: Allows only automatically generated emails, such as new user and password reset emails.
All email: Allows all types of outbound email. The default for new, non-sandbox organizations.

[Shweta]

Content Version: Represents a specific version of a document in Salesforce CRM Content or Salesforce Files. In other words, this object stores document information similar to Attachment.

[Shweta]

A batch apex can be called from a trigger. But, we have to be very very careful while calling a batch apex from the trigger.

[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]

Force.com is a platform where you can develop your own application.
Salesforce.com is Sales(CRM) and Service applications which were developed and running on the Force.com Platform.

[Shweta]

We can use the final keyword to modify variables. Final variables can only be assigned a value once, either when you declare a variable or inside a constructor. You must assign a value to it in one of these two places.

[Shweta]

We can create a date newInstance() and pass the year, month, day from the DateTime to convert DateTime to date. e.g:
DateTime dTime= System.now();
Date newDate = date.newinstance(dTime.year(), dTime.month(), dTime.day());
OR, we can also use Date() method to convert DateTime to date. E.g.:
DateTime dTime= System.now();
Date newDate = dTime.date();

[Shweta]

Custom App: It is a public-facing website and customized to solve a specific business problem. It requires Visual Force, Apex, and Javascript skills.It solves complex business problems
Console App: It is built from the Salesforce Panel and sits on top of the Salesforce Panel and uses Salesforce UI. it is a collection of tabs, objects. This will be a fairly simple application that will help to support Sales, Support, etc functionality.

[Shweta]

Salesforce supports several different types of objects: standard objects, custom objects, external objects.
Standard objects: The objects provided by Salesforce. Example: Account, Contact, Lead, etc.
Custom objects: The objects created by us is called a custom object.
External object: The objects which you create a map to the data stored outside your organization.

[Shweta]

lightning:layout: It is a flexible grid system for arranging containers within a page or inside another container. The default layout is mobile-first and can be easily configured to work on different devices. This component inherits styling from the grid utility classes in the Lightning Design System.

[Shweta]

The component has two types of IDs: a local ID and a global ID:
Local ID: It is an ID that is only scoped to the component. It is often unique but it’s not required to be unique. Local ID is created by using the aura:id attribute. E.g.: To find the local ID for a component in JavaScript, use cmp.getLocalId()
Global IDs: Every component has a unique global Id, which is the generated run=me-­‐unique ID of the component instance.

[Shweta]

Data is stored for up to six months.

[Shweta]

treeGrid: It displays structured data in a table with expandable rows. lightning:treeGrid component displays hierarchical data in a table.

[Shweta]

CronTrigger: It is similar to a cron job on UNIX systems. It is the parent job that will be run, it can have many runs attached to it.
List<CronTrigger> listCronTrigger = [select Id, OwnerId, CronExpression from CronTrigger
where CronExpression like '% MyJobName'];

[Shweta]

There are a few options to validate empty text fields in Apex: We can use String.isBlank() method, this will return true if the text field is empty.

[Shweta]

In Scheduler class, we can execute at a specified time. What we are trying to do is Schedule a Batch. E.g.:
SendEmailToAccountAndContactBatch schedulable = new SendEmailToAccountAndContactBatch();
String sch = '0 0 13 ? MON,TUE,WED,THU,FRI ';
system.schedule('SendEmailToAccountAndContactBatch', sch, schedulable);
database.executebatch(schedulable);

[Shweta]

View state error: It holds the state/size of the visual force page that includes the components, field values, and controller state. This is important in the light that salesforce provides only a standard size of 135kb for any individual page. If the size of a particular page exceeds 135kb, the page will throw a view state error.

[Shweta]

We can add members to a campaign one at a time from contact or lead detail pages. With the Data Import Wizard, we can add up to 50,000 leads, contacts, or person accounts at a time to a campaign.

[Shweta]

Go to the Record Type (Setup -> Customize -> (object) -> Record Types). Click on the record type. Find the Record Type ID in the URL between id= and &type.

[Shweta]

Pagination is the process of displaying a large number of records and displaying the records on multiple pages within Salesforce. In order to control the number of records displayed on each page, we use pagination.

[Shweta]

<apex:message>: A message for a specific component, such as a warning or error. If an or component is not included in a page, most warning and error messages are only shown in the debug log.
<apex:messages>: All messages that were generated for all components on the current page.

[Shweta]

A component has two types of IDs: a local ID and a global ID.
Local ID: It is an ID that is only scoped to the component. A local ID is often unique but it’s not required to be unique.
global ID: Every component has a unique global id, which is the generated runtime-unique ID of the component instance.