Question:- What is Visualforce in Force.com?
Answer:- Visualforce can be defined as the user interface for the Force.com platform. It is a component-based framework that can include over 100 in-built components. It includes a tag-based markup language, and each Visualforce tag corresponds to a page or a field. The Visualforce framework works on the standard MVC paradigm. It is possible to have tight integration with the database and also deploy auto-generated controllers for database objects. Developers can use Apex codes to write their own controllers. It is also possible to access AJAX components, or they can create their own components.
Question:- What is a static resource in Salesforce?
Answer:- A static resource lets us upload content that is in the form of .jar and .zip formats, style sheets, JavaScript, and so on. It is recommended to deploy a static resource rather than uploading files to the Documents tab since it is possible to pack a set of files into a directory hierarchy and upload it. These files can easily be referred to on a Visualforce page.
Question:- Differentiate between Salesforce Object Query Language and Salesforce Object Search Language.
Answer:- • Salesforce Object Query Language (SOQL) lets us search for only one object. We can query for all types of fields in SOQL. Data Manipulation Language (DML) operations can be performed on the query results. • Salesforce Object Search Language (SOSL) lets us search for multiple objects. But, in SOSL, we can query only for texts, emails, and phone numbers. Also, DML operations cannot be performed on the search results.
Question:- What are the different methods of Batch Apex class?
Answer:- Database.Batchable interface contains three methods that must be implemented: Start method: global (Database.QueryLocator | Iterable) start(Database.BatchableContext bc) {} Execute method: global void execute(Database.BatchableContext BC, list
){} Finish method: global void finish(Database.BatchableContext BC){}
Question:- What is the difference between Standard and Custom Controller?
Answer:- • Standard Controllers: Standard Controllers are created for all standard Salesforce pages. They consist of the same logic and functionalities that are utilized in any standard Salesforce page. They can be easily utilized with both standard and custom objects. • Custom Controllers: Custom Controllers is a class written in Apex and it overrides the standard functionality of a standard controller of a page. It executes the logic of a page without utilizing the Standard Controllers. We use custom controllers whenever we want to run a Visualforce page fully in system mode, which means that the security and permissions of the current user will not be recognized.
Question:- What are the different data types that a standard field record name can have?
Answer:- A standard field record consists of either auto-number or text field, read-only data type with a maximum limit of 80 characters. It depends on whether the field name consists of a unique text ID or numerical ID. To create auto numbers, the format should be described while defining the field and later when every record is added, the number gets auto-generated. For example:- Sr No-{1} Sr No-{2}
Question:- Where we can use Lightning Components?
Answer:- We can use Lightning components for various purposes, lets see some of them: • To drag-and-drop Components in the Lightning App Builder and Community Builder. • To add more Lightning Components to Lightning Pages. • To add Lightning Components to Lightning Experience Record Pages. • To override Standard Actions.
Question:- What are the tools included in lightning?
Answer:- • Lightning Component Framework – It provides components and extensions that can be utilized to develop reusable custom components, standalone apps, and customize the Salesforce1 Mobile App. • Lightning App Builder – An UI tool that lets you build apps rapidly with the help of drag and drop components provided by Salesforce. • Lightning Connect – An integration tool to easily integrate Salesforce to consume data from any external source OData specification. • Lightning Process Builder – Lightning Process Builder in Salesforce is a visualization tool for the automation of business processes. • Lightning Schema Builder – It is a visualization tool used to view and create objects, fields, and relationships.
Question:- What are Governor Limits in Salesforce?
Answer:- Governor Limits are some of the biggest challenges for a Salesforce developer. As whenever the Apex code exceeds the limit, it issues a run-time exception and it cannot be handled. The following is the list of some of the key Governor Limits in Salesforce: • Push Notification Limits • Per-Transaction Apex Limits • com Platform Apex Limits • Size-Specific Apex Limits • Miscellaneous Apex Limits • Static Apex Limits • Email Limits
Question:- What are the different types of collections in Salesforce Apex?
Answer:- Collections are the type of variables used to store multiple numbers of records (data). Types of collections in Salesforce are: • Lists • Maps • Sets
Question:- What are maps in Apex?
Answer:- Maps are used to store data in the form of key–value pairs, where each unique key maps to a single value. Syntax: Map country_city = new Map();
Question:- What is an Apex transaction?
Answer:- An Apex transaction represents a set of operations that are executed as a single unit. These operations include DML operations that are responsible for querying records. All the DML operations in a transaction either get completed successfully or get rolled back completely if an error occurs even in saving a single record.
Question:- What is the difference between public classes and global classes in Salesforce Apex?
Answer:- A global class is accessible across the Salesforce instance, irrespective of namespaces. Whereas, public classes are accessible only in the corresponding namespaces.
Question:- What are getter and setter methods?
Answer:- The get (getter) method is used to pass values from the controller to the VF page. Whereas, the set (setter) method is used to set the value back to the controller variable.