[Somendra]

Manual sharing allows users to grant one-off access to their individual records for users, roles, and public groups. Manual sharing is available: To the record owners, their managers in the role hierarchy, and administrators. For objects set as public read-only or private in organization-wide defaults.

[Somendra]

yes

[Somendra]

The AppLauncher namespace provides methods for managing the appearance of apps in the App Launcher, including their visibility and sort order.
The following class is in the AppLauncher namespace.
AppMenu Class
Contains methods to set the appearance of apps in the App Launcher.
CommunityLogoController Class
Represents the logo of the community. For internal use only.
EmployeeLoginLinkController Class
Represents the link on the login form that employees can click to log in. For internal use only.
LoginFormController Class
Represents a login form. For internal use only.
SocialLoginController Class
Represents the social authentication providers configured for the community. For internal use only.

[Somendra]

Fields that are automatically indexed in Salesforce are:
RecordTypeId.
Division.
CreatedDate.
Systemmodstamp (LastModifiedDate)
Name.
Email (for contacts and leads)
Foreign key relationships (lookups and master-detail)
The unique Salesforce record ID, which is the primary key for each object.

[Somendra]

The Auth namespace contains the following exception.

Auth.​AuthProviderPluginException
Auth.​ConnectedAppPlugin​Exception
Auth.DiscoveryCustomErrorException
Auth.JWTBearerTokenExchange.​JWTBearerTokenExchangeException​
Auth.LoginDiscoveryException
Auth.VerificationException

for more details click here

• This reply was modified 5 years, 3 months ago by  Somendra.
• This reply was modified 5 years, 3 months ago by  Somendra.

[Somendra]

Hi Piyush,

Different data types available in Apex are,

1.Basic data type (Integer/Boolean/String)
2.Boolean
3.Date/Datetime/Time
4.ID (18 bits and 15 bits, can be converted to and from String)
5.Integer/Long/Double/Decimal
6.String
7.Blob
8.Object
9.Enum (enumeration type)
10.sObjects ( sObjects/Account/Position_c, etc. )
11.Collection (list, set, map, etc.)
12.User-defined and system custom objects
13.Null

[Somendra]

Hi Nikita,

As far as I'm aware the only limit is your data storage, you can see what you've used by going to Setup -> Administration Setup -> Data Management -> Storage Usage.

In one of the Orgs I work with I can see one object has almost 2GB of data for just under a million records, and this accounts for a little over a third of the storage available. Your storage space depends on your Salesforce Edition and number of users.  See here for details.

[Somendra]

Hello Nikita,

Triggers are pure custom coding (Apex) to create solutions for different business problems. It can be used for various different things and can be executed at different times.

Simply I can say validation rule is just blocking invalid data based on the business rule, a trigger can do the same thing, but can do more.

[Somendra]

Hi Piyush,

In simple words, Web-to-Lead is Generate Leads from Your Website for Your Sales Teams. This feature create or generate upto 500 leads per day with prospecting data from your company’s website visitors.
Salesforce runs field validation rules before creating records submitted via Web-to-Lead and only creates records that have valid values.
If a new lead cannot be generated due to errors in your Web-to-Lead setup, Customer Support is notified of the problem so that we can help you correct it.

[Somendra]

Following is the list of tools used in salesforce for deployment.

1.Eclipse with Force.com IDE
2.com Migration Tool – ANT/Java based
3.Salesforce Package
4.Change Sets
5.Integration

[Somendra]

In some ways, List-type Custom Settings are very similar to Custom Objects. In fact, if you use a tool like the Data Loader to view a list of objects in your org, you’ll see that Custom Settings are listed together with Custom Objects, without any visible distinction between the two.

In Custom objects you can create validation rules , triggers , workflows , page-layout and record type whereas not in custom setting.

Custom Settings are used to Avoiding Governor Limits

Depending on how your Apex code interacts with Custom Settings, they can have zero impact on certain governor limits. That’s right – you can retrieve all of the values in a Custom Setting with absolutely no impact on the governor’s count of the number of queries you’ve performed or the number of rows you’ve retrieved.  This makes Custom Settings particularly useful for reference data, like lists of Postal Code / State mappings.

[Somendra]

Till now we can not send email to distribution List as per my knowledge...

I think there is already an Idea on this topic in the Salesforce IdeaExchange. You can vote for it.
Emailing a Group (Email Distribution List) (https://success.salesforce.com/ideaView?id=08730000000BpZ7)

[Somendra]

Workflow consists of the following components:
– Workflow Rules – trigger criteria for performing various workflow actions
– Workflow Tasks – action that assigns a task to a targeted user
– Workflow Email Alerts – action that sends an email to targeted recipients
– Workflow Field Updates – action that updates the value of a field automatically
– Workflow Outbound Messages – action that sends a secure configurable API message (in XML format) to a designated listener (not covered in this class)

[Somendra]

In import wizard while importing , duplicates can be ignored but in case of data loader duplicates cannot be ignored.

import wizard supports schedule export while data loader doesn't.

[Somendra]

trigger convertLead on Lead (before update) {
for(Lead myLead:Trigger.new){
if(myLead.status == 'qualified'){
list<Account> acc = [select id,name from account where name =: myLead.Company limit 1];
if(acc.size() == 0){
Id accId = create.createNewAccount(myLead.Company);
create.createContact(accId,myLead.LastName);
create.createOpportunity(accId,myLead.Company);
}
else{
create.createContact(acc[0].Id,myLead.LastName);
create.createOpportunity(acc[0].Id,myLead.Company);
}
}
}
}

Helper class-

public class create {
public static id createNewAccount(String accName){
Account acc = new Account(name = accName);
insert acc;
return acc.Id;
}
public static void createContact(id accID,String lName){
Contact con = new Contact(lastname = lName,accountId=accID);
insert con;
}
public static void createOpportunity(id accID,String company)
{
Opportunity opp = new Opportunity(name = company+'-',accountId=accID,StageName='prospecting',closedate=system.today());
insert opp;
}
}