One Line Description Salesforce
One Line Description Salesforce
Apex Programming
● Apex: Salesforce’s server-side language used to write custom business logic and
automate processes on the Salesforce platform.
● Apex Triggers: Code executed before or after records are inserted, updated, or deleted
in Salesforce.
● Apex Classes: Groups of methods and variables used to implement business logic in
Salesforce.
● SOQL: A query language used to fetch Salesforce data, similar to SQL but specific to
Salesforce’s data model.
3. Visualforce Pages
● Visualforce: A framework for creating custom UIs in Salesforce using HTML, CSS, and
JavaScript integrated with Salesforce data.
● LWC: A modern JavaScript framework for building Salesforce UIs with a focus on
performance, reactivity, and web standards.
5. Flow Builder
● Flow: A declarative tool used for automating business processes, collecting user input,
and performing record updates without code.
6. Process Builder
● Process Builder: A no-code automation tool to define criteria and actions for record
updates, email alerts, and more.
● REST API: Used for connecting Salesforce to external systems with a stateless, scalable
approach for web services.
● SOAP API: Used for larger, more secure integrations with enterprise systems, relying on
XML for data transmission.
8. Salesforce DX
● Salesforce DX: A set of tools for managing Salesforce development, supporting version
control, continuous integration, and automation of deployments.
9. Batch Apex
● Batch Apex: A class for processing large amounts of records asynchronously in chunks,
useful for bulk data processing.
● Queueable Apex: Used for complex asynchronous operations, such as chaining jobs or
processing large datasets.
● Sharing Rules: Define how record access is granted to users based on criteria, roles,
and groups, ensuring data visibility across users.
● Apex Sharing: A method to programmatically share records with other users, beyond
what sharing rules allow.
● Profiles: Define baseline permissions for user access to Salesforce objects, fields, and
records.
● Permission Sets: Provide additional permissions to users, overriding profile settings.
● Role Hierarchy: A structure that defines the data access level across users, where
higher roles can access data owned by lower roles.
● Web Services: Enable communication between different applications over the internet,
using protocols like SOAP and REST.
● SOAP API: A protocol that uses XML for messaging and is more rigid, suitable for
enterprise-level integrations.
● REST API: A flexible, lightweight alternative to SOAP, using HTTP methods like GET,
POST, PUT, and DELETE.
● Integration Patterns: Best practices for integrating Salesforce with other systems, such
as Real-Time, Batch, Request-Reply, and Fire-and-Forget.
● Apex Best Practices: Includes writing bulk-safe code, minimizing SOQL queries,
handling exceptions, and using try-catch blocks for error handling.
● Manual Sharing: Used by users to manually share specific records with other users
when required, without setting up rules.
● Test Classes: Ensure 75% code coverage for Apex classes before deployment; tests
simulate data and ensure the Apex code works as expected.
● Custom Objects: Objects that are created to store data specific to your organization,
alongside standard Salesforce objects.
● Object Relationships: Relationships define how objects are related to one another,
including Lookup, Master-Detail, and Many-to-Many (Junction Object).
● Data Import: Using tools like Data Loader and Data Import Wizard to import or export
Salesforce data.
● Lightning App Builder: A drag-and-drop tool for creating custom Salesforce pages,
combining Lightning components and standard Salesforce components.
● CI/CD: Continuous Integration and Continuous Delivery processes for automating testing
and deployment, ensuring smooth updates and rollbacks.
● Stateful Batch Apex: Maintains state between transactions, useful for storing
intermediary data.
● Stateless Batch Apex: Doesn’t maintain state and works with each record
independently, ensuring performance and scalability.
● Health Cloud: A CRM solution tailored for the healthcare industry, allowing better
management of patient data and providing a 360-degree view of the patient.
● Sales Cloud: A CRM application for managing sales processes, from lead generation to
opportunity management, closing deals, and reporting.
● Marketing Cloud: A suite of tools for managing and automating marketing efforts,
including email marketing, social media engagement, and customer journeys.
● Lightning Data Service: A client-side service that enables components to access and
manipulate Salesforce data without needing Apex code.
● Mixed DML: An issue that occurs when DML operations on setup and non-setup objects
are performed in the same transaction. It can cause errors and needs to be avoided.
Validation Rules
● Validation Rule: A rule used in Salesforce to enforce data integrity by specifying criteria
that must be met before a record can be saved. If the criteria are not met, an error
message is shown.
○ Example: A validation rule might prevent a user from saving a record if a
required field is empty or if a value entered is incorrect.
○ Usage: Ensures that records meet certain conditions, like making sure the "Close
Date" on a sales opportunity is not in the past.
● API: A set of protocols and tools that allow different software systems to communicate
with each other. In Salesforce, APIs allow integration with external systems to access,
update, or retrieve data from Salesforce programmatically.
○ REST API: Used for accessing and interacting with Salesforce data through
HTTP requests. Best suited for mobile or web-based applications.
○ SOAP API: Used for more complex integration scenarios with external systems.
It uses XML to encode messages.
○ Bulk API: Used for handling large volumes of data in Salesforce, ideal for data
migration and data management.
● Usage in Salesforce:
○ Access Salesforce data from external applications or databases.
○ Integrate third-party systems, such as payment processors or marketing
automation tools, with Salesforce.
Webhook
● Webhook: A webhook is a real-time data push from one system to another when an
event occurs. Unlike traditional APIs, where a system checks for updates periodically,
webhooks allow an event to trigger a notification automatically to a pre-configured URL.
○ Example: When a payment is processed in an external payment system, a
webhook sends a notification to Salesforce to update the payment status.
● Usage in Salesforce:
○ Integration with external systems: Webhooks enable seamless data exchange
between Salesforce and other platforms, such as payment gateways or
marketing tools.
○ Real-time updates: Webhooks can be used to send alerts or trigger actions in
Salesforce based on events occurring outside of the platform.
Approval Process
● DOM (Document Object Model): The DOM is an interface that allows programs to
dynamically access and manipulate the content, structure, and styles of web documents.
It is represented as a tree structure where each element of the document is a node.
○ In Salesforce: DOM plays a role when developing Visualforce pages or Lightning
Components, allowing developers to interact with page elements using
JavaScript.
○ Key Points:
■ The DOM allows real-time changes to web pages and their elements.
■ Developers can manipulate the DOM to add interactivity and dynamic
behavior to the page.
■ Common operations include updating content, changing styles, or
modifying page structure on the fly.
● REST API: Lightweight and easy to use for mobile applications or simple integration.
Access records using standard HTTP methods.
● SOAP API: Works well with heavy-duty integrations and complex systems.
● Bulk API: Allows you to upload or delete large volumes of data quickly, suitable for data
migrations.