[Shweta]

Manual Sharing: It shares via a button on the record and the button enables only when OWD is private to that object. It can be granted by the record owner, anyone above the owner in role hierarchy and System Administrator. It is used to handle exception cases where access to a particular record needs to be given to a specific user.

[Shweta]

OWD: Organization-Wide Default

• It gives you a baseline level of access for each object & enables to extend that level of access using hierarchies or, sharing rules.
• This can be used to give permissions to the organization-wide and it can be used to restricting access and we can control the record level access.

[Shweta]

Sales Cloud:

• It refers to the "sales" module in salesforce.com. It includes Leads, Accounts, Contacts, Contracts, Opportunities, Products, Price Books, Quotes, and Campaigns (limits apply). It includes features such as Web-to-lead to support online lead capture, with auto-response rules. It is designed to be a start-to-end set up for the entire sales process; you use this to help generate revenue.
• It implements Sales and Marketing.

Service Cloud:

• It refers to the "service" module in salesforce.com. It includes Accounts, Contacts, Cases, and Solutions. It also encompasses features such as the Public Knowledge Base, Web-to-case, Call Center, and the Self-Service Portal, as well as customer service automation. It is designed to allow you to support past, current, and future clients' requests for assistance with a product, service, and billing. You use this to help make people happy.
• It implements Salesforce Knowledge.

[Shweta]

Sandbox: It is a copy of your production database’s configuration only, not the records. It is the place where you can do development work. Sandbox org can be used as a testing org. It is also useful from a security point of view.

Development Environment: It is nothing but a collection of stuff that you are going to use to compose the code and produce related software.

[Shweta]

Salesforce Edition:  A set of Salesforce features wrapped together is called Editions. Salesforce provides these types of editions: Essentials, Professional, Enterprise, Unlimited, and Developer Editions.

 

[Shweta]

Chatter: It is an enterprise collaboration platform from Salesforce and it can be used as a company intranet or employee directory. It allows you to collaborate with the people with each other in your organization.

[Shweta]

Date Methods in Salesforce:

• addDays: Adds the specified number of additional days to a Date.
• addMonths: Adds the specified number of additional months to a Date
• addYears: Adds the specified number of additional years to a Date
• day(): Returns the day-of-month component of a Date.
• dayOfYear(): Returns the day-of-year component of a Date.
• daysBetween(secondDate): Returns the number of days between the Date that called the method and the specified date.
• daysInMonth(year, month)
• format()
• month()
• newInstance(year, month, day)
• today()
• year()

[Shweta]

userorgroupid: The id of user or group to which access is being granted. To share records using Apex managed sharing, you need to write the Apex code. And it needs userorgroupid field value for sharing records.  Example: testShare.UserOrGroupId = userListId;

 

[Shweta]

Utility classes are helper classes that consist of reusable methods. This method is like you have any other apex class, where you have written some code and you can use those methods in Trigger.

Example:

trigger updateOpp on Opportunity (before insert){
 for(Opportunity  opp : Trigger.new){
 opp.formattedDate__c = TriggerHelper.formatDate(opp.someDate__c);
}
}

//Utility Class
Public Class TriggerHelper{
Public Static string formatDate(Date inputDate){
   return inputDate.format();
}
}

 

 

[Shweta]

Inline editing is a feature by which one can edit a record without pressing the edit button. It can not be turned on for one user and turned off for another. It is global and works for all or none. If you have changed a value using Inline Editing but forgot to press the save button then those changes will not be saved and will get discarded as soon as you close that particular window

[Shweta]

There are two types of Workflow available in Salesforce:

• Immediate Workflow rule: Workflow rule fires immediately when the workflow criteria are met, and the associated actions will take place immediately.
• Time Dependent Workflow rule: When the workflow entry criteria are met, associated actions (email alert, etc.,) will take place after a certain period of time. This time is based on the value that you set.

[Shweta]

To show a list of values in Visualforce first create the Apex class :

public class TestClass {
    public String selectedaccId {set;get;}
    List<selectOption> options=new List<selectoption>();
    public TestClass(){
        selectedaccId ='';
    }  
    public List<SelectOption> getListOfAccount(){
        options.add(new selectOption('','--Select--'));
        for(Account acc:[select id,name from account ]){
            options.add(new selectOption(acc.id,acc.name));
        }
        return options; 
    }
}

And then display it on Visualforce page :

<apex:page controller="TestClass">
    <apex:form >
        <apex:pageBlock title="Account Name">
            <apex:pageMessages />
            <apex:pageBlockSection >
                <apex:OutputPanel >
                    <apex:selectList label="Account Name" value="{!selectedaccId}" size="1" multiselect="false" required="true"  >
                        <apex:selectOptions value="{!ListOfAccount}"  />
                    </apex:selectList>
                </apex:OutputPanel> 
            </apex:pageBlockSection>
        </apex:pageBlock>
    </apex:form>
</apex:page>

 

 

[Shweta]

Salesforce Pricing (per user, per month):

• Salesforce Essentials – €25 user/month
• Lightning Professional – €75 user/month
• Lightning Enterprise – €150 user/month
• Lightning Unlimited – €300 user/month

 

[Shweta]

Dynamic Query/SOQL: It refers to the creation of a SOQL string at run time with Apex code. It enables you to create more flexible applications. You can use simple bind variables in dynamic SOQL query strings.

[Shweta]

Aggregate function: In Salesforce, It include AVG(), COUNT(), MIN(), MAX(), SUM(). It allows you to roll up and summarize your data in a query.

[Shweta]

Activity: It includes tasks (i.e., to-dos), events (i.e., meetings), and calendars. When you go to edit them in Setup to view fields, they are subdivided into Task Fields and Event Fields. But then if you want to add a custom field, it is under Activity Custom Fields.

[Shweta]

Salesforce provides you with two versions of Record Ids and used in different situations

• 15 character id: It is a case sensitive version that is referenced in the Salesforce user interface. You can use this id in while performing data operations through the user interface.
• 18 character id: It is a case sensitive version that is referenced through the APIs. It is a Salesforce best practice to use 18 character id in API.

[Shweta]

Record Type: It allows you to define different sets of picklist values for both standard and custom picklists and it help you to implement your custom business processes. It is used to drive which page layouts users see when viewing records, based on their user profile.

[Shweta]

ActionRegion: It provides an area of a Visualforce page that decides and separates which components should be processed by the force.com server when an AJAX request is generated. Only the components which are inside <apex:actionRegion>  component are processed by the server, so it increases visualforce page performance.

[Shweta]

ViewState: It holds the state of the visualforce page and the state includes the fields, components and controller state. The data of ViewState is encrypted and cannot be viewed as tools like firebug. It Stores Objects that are reachable from a non-transient data member in a controller or extension and it also Stores all the public and private data members present in Standard, Custom and Controller extensions.

[Shweta]

StandardSetController: It is an object that allows you to create list controllers similar to, or as extensions of, the pre-built Visualforce list controllers provided by Salesforce. It also contains a prototype object.

[Shweta]

Junction object: A junction object is an object when we can create many-to-many relationships using two master-detail relationships in an object.

[Shweta]

disconnectedCallback() : When the element is removed from a document and this hook flows from parent to child.

[Shweta]

The PUT method allows partial updates, so if some updates fail but others succeed, the successful updates aren’t rolled back.

[Shweta]

• JSON serialization and deserialization support : It is available for sObject, Apex primitive and collection types, return types of Database methods and instances of your Apex classes.
•  Map object is serializable into JSON only if it uses these data types as a key : Boolean, Date, DateTime, Decimal, Double, Enum, Id, Integer, Long, String, Time.