Developer Fundamentals Flashcards
What is MVC?
Model,View,Controller
What is Multi-tenant Environment?
Unique URL Endpoints
Governor Limits -
Data Retrieval
Data Creation
API Limits
Benefits - Economy of scale from shared services
Quick Turn around time
Industry standardization
What is Lightning Component Framework?
A UI framework by Salesforce for dynamic, responsive web apps on desktop and mobile devices.
- Component-based development. - Event-driven communication. - Responsive design. - Built-in security.
What are the capabilities of the Lightning Component Framework?
Aura Components & Lightning Web Components.
The components built using the framework can be added as custom tabs on the navigation bar.
Uses JavaScript on the client-side and Apex on the Server side.
What is Component Based Development?
An approach where apps are built by combining reusable, independent components
- Faster development with component reuse. - Easier maintenance and collaboration.
What is Lightning Web Components?
A modern UI framework for web apps using web standards like HTML, CSS, and JavaScript.
What is Global Access modifier?
The global access modifier indicates that this class is accessible outside of its namespace, making it available for use in other namespaces or packages.
What is example of Array in Apex?
Contact[] ContactList: This is a public property of the class, and it returns an array of Contact objects.
What is example of Controller - getting return of records in Apex class?
global class ListofContactController {
global Contact[] ContactList{ get{ return [SELECT Id, Name FROM Contact]; } }
}
What is an example of calling a custom controller in visualforce?
<apex:page>
<apex:pageBlock>
<apex:pageBlockTable>
<apex:column></apex:column>
</apex:pageBlockTable>
</apex:pageBlock>
</apex:page>
When should you use declarative customizations in Salesforce?
Declarative customizations should be used when possible for simple use cases that do not require complex logic or extensive data processing. They are ideal for scenarios where you can achieve the desired outcome using point-and-click tools like Process Builder, Flow Builder, Workflow Rules, Validation Rules, and Page Layouts.
What are some common use cases for declarative customizations?
Automatically assigning record ownership based on criteria. - Sending email notifications when certain conditions are met. - Enforcing data validation rules using Validation Rules. - Customizing the layout and fields on record detail pages with Page Layouts. - Creating simple calculations using Formula Fields.
What are the advantages of declarative customizations?
No coding skills required, making it accessible to non-developers. - Faster implementation and easier maintenance. - Built-in features for version control and auditing changes. - Typically fewer governor limit considerations compared to programmatic solutions.
When should you consider using programmatic customizations in Salesforce?
Programmatic customizations are necessary when you need to implement complex business logic, extensive data processing, or integrations that cannot be achieved using declarative tools alone. You should consider programmatic solutions when declarative tools cannot meet the specific requirements of your project.
What are some common use cases for programmatic customizations?
Complex data transformations and data migrations. - Integrating Salesforce with external systems using APIs. - Implementing custom algorithms or business processes that require conditional logic. - Extensive data manipulation or calculations beyond the capabilities of Formula Fields. - Implementing custom user interfaces or web applications using Visualforce or Lightning components.
What are the advantages of programmatic customizations?
Greater flexibility and control over business processes. - Ability to handle complex logic and integrations. - Custom user interface development with Visualforce or Lightning components. - Extensibility and customization of Salesforce beyond the capabilities of declarative tools.
What are governor limits in Salesforce, and how do they relate to programmatic customizations?
Governor limits are runtime constraints imposed by Salesforce to ensure the efficient use of system resources and to prevent monopolization of shared resources. Programmatic customizations, such as Apex code and triggers, need to be designed with these limits in mind. Developers must ensure that their code operates within these limits to avoid performance issues and potential exceptions.
When is it appropriate to use formula fields in Salesforce?
Formula fields are appropriate for scenarios where you need to calculate values based on data from the same record or related records and display the result in a field. They are useful for simple calculations, such as computing a total amount or determining a record’s status based on certain criteria. Formula fields are an excellent choice when the logic can be expressed using formula functions and does not require extensive processing or external data sources.
What are best practices for using formula fields effectively?
- Keep formula fields simple and avoid complex logic. - Minimize the use of cross-object formula fields to avoid performance issues. - Leverage formula functions and operators for efficient calculations. - Test formula fields thoroughly to ensure they produce the expected results. - Document formula logic and field descriptions for clarity.
In what scenarios should you consider using roll-up summaries in Salesforce?
Roll-up summaries are valuable when you need to calculate and display aggregated data from related records, such as counting the number of related child records or summing up a specific field’s values from child records. They are most effective when dealing with parent-child relationships in Salesforce objects like Accounts and Contacts or Opportunities and Products. Roll-up summaries simplify reporting and provide real-time visibility into data without the need for custom code or complex queries.
What are best practices for using roll-up summaries efficiently?
Identify the appropriate parent-child relationships for roll-up summaries. - Configure the roll-up summary field to perform the desired aggregation, such as COUNT, SUM, or AVG. - Consider using filtering criteria to refine the set of child records to include in the calculation. - Regularly review and maintain roll-up summaries, especially when data models change. - Be mindful of governor limits, as roll-up summaries consume limits when recalculating data.
When designing a data model in Salesforce, what factors should be considered?
When designing a data model, consider: - The nature of the business processes being modeled. - The relationships between different data entities. - Data volume and scalability requirements. - Reporting and analytics needs. - Integration requirements with external systems.
What is an object in Salesforce, and how does it relate to data modeling?
In Salesforce, an object is a database table that stores specific types of data, such as Accounts, Contacts, or Custom Objects. Objects are used to model and organize data within the application. When designing a data model, you determine which standard and custom objects are needed to represent different data entities and their relationships.