A PROJECT REPORT
submitted by
Akanksha Kumari Sinha
Registration Number – 20110109003
on
Salesforce Developer Virtual Internship
in partial fulfillment of the requirements for the award of the
degree of
BACHELOR OF TECHNOLOGY ([Link])
in
Electrical and Electronics Engineering
December 2023 – January 2024 (6 weeks)
INTRODUCTION
Salesforce is an American cloud-based software company headquartered in San
Francisco, California. It provides customer relations management (CRM) software
and applications focused on sales, customer service, marketing automation,
analytics, and application development.
Salesforce is headquartered in San Francisco, California, the US. In 2009,
Salesforce passed $1 billion in annual revenue.
Customer Relation Management
It is a process in which a business or other organization administers its interactions
with customers, typically using data analysis to study large amounts of information.
CRM systems compile data from a range of different communication channels,
including a company's website, telephone (which much software come with a
softphone), email, live chat, marketing materials and more recently, social media.
They allow businesses to learn more about their target audiences and how to better
cater to their needs, thus retaining customers and driving sales growth.
History
The company was founded in 1999 by former Oracle executive Marc Benioff,
together with Parker Harris, Dave Moellenhoff, and Frank Dominguez as a software
as a service (SaaS) company.
Page | 1
Services
Salesforce applications are built using Apex, a proprietary Java-like programming
language to generate HTML originally via the "Visualforce" framework. Beginning
in 2015, the "Lightning Components" framework has been supported.
The Services offered by Salesforce:
● SAAS (Software as a Service): Here, you can directly obtain the built-in
software and make use of it.
● PAAS (Platform as a Service): PAAS offers you the framework and
platform to build your websites and apps.
● IAAS (Infrastructure as a Service): IAAS plays a vital role in Salesforce
development, although not very widely used.
AppExchange: Launched in 2005, the Salesforce AppExchange is an online app
store that allows users to sell third-party applications and consulting services.
Trailhead: Launched in 2014, Trailhead is a free online learning platform with
courses focused on Salesforce technologies.
Page | 2
SMART INTERNZ
SmartInternz is an Experiential Learning & Remote Externship Platform to bring
academia & industries very close for a common goal of talent creation under
SmartBridge Corporation.
It provides experience through real-world projects supported by mentors.
SmartInternz‟s platform also provides a collaborative work environment for
students and companies to effectively run internships.
SmartInternz is an innovative product of TheSmartBridge, which is registered as
SmartBridge Educational Services Private Limited.
Salesforce Developer Virtual Internship was completed with the help of
SmartInternz Platform.
Here’s my SmartInternz Externship page:
Page | 3
TRAILHEAD
Trailhead is a series of online tutorials that coach beginner and intermediate
developers on how to code for the Salesforce platform. Trailhead education, which
was launched in 2014, comes in three levels: trails, modules and units.
Lessons are presented in a specific sequence, so customers have a predefined path
to follow and a "guided, curated" experience, according to Salesforce.
The learning program is designed to help users by providing a series of interactive
assessments to identify whether learners have learned the content. Gamification is
built into the Trailhead program, so developers can also earn badges for milestones
reached in their Trailhead education.
Here’s my Trailhead profile:
Page | 4
TASKS ACCOMPLISHED DURING THIS INTERNSHIP
For the completion of Salesforce Developer Virtual Internship , we were
instructed to complete Developer Super Set on the Trailhead Platform.
What we did to Earn This Superbadge:
● Demonstrated programmatic skills with Apex and wrote Apex unit tests.
● Identified process automation tools and strategies.
Concepts Tested in This Superbadge:
● Apex Development
● Process Automation
Developer SuperSet Capstone:
The Developer Super Set capstone is a Salesforce credential composed of two
SuperBadges.
Page | 5
● Apex Specialist
● Process Automation Specialist
Completed these SuperBadges to unlock this super set capstone, and then completed
the challenges given to earn the Developer Super Set.
Apex Specialist Superbadge includes:
● Automate record creation using Apex triggers
● Synchronize Salesforce data with an external system using asynchronous
REST callouts.
● Schedule synchronization using Apex code
● Test automation logic to confirm Apex trigger side effects
● Test integration logic using callout mocks
● Test scheduling logic to confirm action gets queued
Process Automation Specialist Superbadge includes:
● Demonstrating knowledge of automation and troubleshooting for approval
processes.
● Identify Flow elements and the best practices for scalability and improved
performance.
● Demonstrate the knowledge of screen flows and screen flow distribution.
Page | 6
1. APEX SPECIALIST SUPERBADGE
Salesforce Apex is a Microsoft-certified framework for building software as a
service (SaaS) apps on top of Salesforce's customer relationship management
(CRM) functionality.
Apex enables developers to access the Salesforce platform back-end database and
client- server interfaces to create third-party SaaS applications.
Apex includes an application programming interface (API) that Salesforce
developers can use to access user data on the platform.
This API enables Apex developers to use standard SaaS components, like web
widgets or a multi-tenant database, without the need to develop much of the
infrastructure traditionally associated with SaaS programs.
Apex is a proprietary language developed by [Link]. It is a strongly typed,
object-oriented programming language that allows developers to execute flow and
transaction control statements on the [Link] platform server in conjunction with
calls to the [Link] API.
Under this SuperBadge, the prerequisites that we completed were:
Page | 7
Concepts Tested in This Superbadge:
● Apex Triggers
● Asynchronous Apex
● Apex Integration
● Apex Testing
We had to set up a new Trailhead Playground or Developer Edition org for this
Superbadge. Install a package (package Id: 04t6g000008av9iAAA). This package
contained metadata we used to complete this challenge.
In these SuperBadges, we tested the trigger to ensure that it worked as expected.
Followed best practices by testing for both positive use cases (when the trigger
needs to fire) and negative use cases (when the trigger must not fire).
When we have 100% code coverage on our trigger and handler, write test cases for
our callout and scheduled Apex classes. We need to have 100% code coverage for
all Apex in our org.
Ensure that our code operates as expected in the scheduled context by validating
that it executes after [Link]() without exception. Also assert that a scheduled
asynchronous job is in the queue. The test classes for the callout service and
scheduled test must also have 100% test coverage.
Page | 8
1.1 APEX TRIGGERS
Apex triggers enable you to perform custom actions before or after events to records
in Salesforce, such as insertions, updates, or deletions. Just like database systems
support triggers, Apex provides trigger support for managing records.
Typically, you use triggers to perform operations based on specific conditions, to
modify related records or restrict certain operations from happening. You can use
triggers to do anything you can do in Apex, including executing SOQL and DML
or calling custom Apex methods.
Use triggers to perform tasks that can‟t be done by using the point-and- click tools
in the Salesforce user interface.
For example, if validating a field value or updating a field on a record, use validation
rules and flows. Use Apex triggers if performance and scale is important, if your
logic is too complex for the point-and-click tools, or if you're executing CPU-
intensive operations.
This module consisted of two units:
● Get Started with Apex Triggers
● Bulk Apex Triggers
GET STARTED WITH APEX TRIGGERS
Learning Objectives in this unit are:
● Writing a trigger for a Salesforce object.
● Using trigger context variables.
● Calling a class method from a trigger.
Page | 9
● Using the sObject addError() method in a trigger to restrict the save
operations.
Types of Triggers
There are two types of triggers-
Before triggers - They are used to update or validate record values before they are
saved to the database.
After triggers - They are used to access field values that are set by the system (such
as a record's Id or LastModifiedDate field), and to affect changes in other records.
The records that fire the after trigger are read-only.
Trigger Syntax
The syntax of a trigger definition is different from a class definition‟s syntax. A
trigger definition starts with the trigger keyword. It is then followed by the name of
the trigger, the Salesforce object that the trigger is associated with, and the
conditions under which it fires.
A trigger has the following syntax:
trigger TriggerName on ObjectName (trigger_events) { code_block
To execute a trigger before or after insert, update, delete, and undelete operations,
specify multiple trigger events in a comma-separated list.
Page | 10
The events you can specify are:
● before insert
● before update
● before delete
● after insert
● after update
● after delete
Using Context Variables
To access the records that caused the trigger to fire, use context variables.
For example, [Link] contains all the records that were inserted in insert or
update triggers. [Link] provides the old version of sObjects before they were
updated in update triggers, or a list of deleted sObjects in delete triggers. Triggers
can fire when one record is inserted, or when many records are inserted in bulk via
the API or Apex. Therefore, context variables, such as [Link], can contain
only one record or multiple records. You can iterate over [Link] to get each
individual sObject.
Calling a Class Method from a Trigger
You can call public utility methods from a trigger. Calling methods of other classes
enables code reuse, reduces the size of your triggers, and improves maintenance of
your Apex code. It also allows you to use object-oriented programming.
Page | 11
Adding Related Records
This trigger adds a related opportunity for each new or updated account if no
opportunity is already associated with the account. The trigger first performs a
SOQL query to get all child opportunities for the accounts that the trigger fired on.
Next, the trigger iterates over the list of sObjects in [Link] to get each account
sObject. If the account doesn‟t have any related opportunity sObjects, the for loop
creates one. If the trigger created any new opportunities, the final statement inserts
them.
Using Trigger Exceptions
We sometimes need to add restrictions on certain database operations, such as
preventing records from being saved when certain conditions are met. To prevent
saving records in a trigger, call the addError() method on the sObject in question.
The error message is displayed in the user interface and is logged.
The following trigger prevents the deletion of an account if it has related
opportunities. This trigger prevents the cascade delete of opportunities.
Page | 12
BULK APEX TRIGGERS
Learning Objectives in this unit are:
● Write triggers that operate on collections of sObjects.
● Write triggers that perform efficient SOQL and DML operations.
Bulk Trigger Design Patterns
Apex triggers are optimized to operate in bulk. We recommend using bulk design
patterns for processing records in triggers. When you use bulk design patterns, your
triggers have better performance, consume less server resources, and are less likely
to exceed platform limits.
The benefit of bulkifying your code is that bulkified code can process large numbers
of records efficiently and run within governor limits on the Lightning Platform.
These governor limits are in place to ensure that runaway code doesn‟t monopolize
resources on the multitenant platform.
Operating on Record Sets
Bulkified triggers operate on all sObjects in the trigger context. Typically, triggers
operate on one record if the action that fired the trigger originates from the user
interface. But if the origin of the action was bulk DML or the API, the trigger
operates on a record set rather than one record. For example, when you import many
records via the API, triggers operate on the full record set.
Page | 13
Performing Bulk SOǪL
SOQL queries can be powerful. You can retrieve related records and check a
combination of multiple conditions in one query. By using SOQL features, you can
write less code and make fewer queries to the database. Making fewer database
queries helps you avoid hitting query limits, which are 100 SOQL queries for
synchronous Apex or 200 for asynchronous Apex.
Performing Bulk DML
When performing DML calls in a trigger or in a class, perform DML calls on a
collection of sObjects when possible. Performing DML on each sObject
individually uses resources inefficiently. The Apex runtime allows up to 150 DML
calls in one transaction.
Page | 14
1.2 APEX TESTING
The Apex testing framework enables you to write and execute tests for your Apex
classes and triggers on the Lightning Platform. Apex unit tests ensure high quality
for your Apex code and let you meet requirements for deploying Apex.
Testing is the key to successful long-term development and is a critical component
of the development process. The Apex testing framework makes it easy to test your
Apex code. Apex code can only be written in a sandbox environment or a Developer
org, not in production. Apex code can be deployed to a production org from a
sandbox. Also, app developers can distribute Apex code to customers from their
Developer orgs by uploading packages to the Lightning Platform AppExchange. In
addition to being critical for quality assurance, Apex unit tests are also requirements
for deploying and distributing Apex.
This module consisted of three units:
● Get Started with Apex Unit Tests
● Test Apex Triggers
● Create Test Data for Apex Tests
Test Method Syntax
Test methods are defined using the @isTest annotation and have the following
syntax:
@isTest static void testName() {
// code_block
Page | 15
Test methods must be defined in test classes, which are classes annotated with
@isTest.
@isTest
private class MyTestClass { @isTest static void myTest() {
// code_block
Test classes can be either private or public. If you‟re using a test class for unit
testing only, declare it as private. Public test classes are typically used for test data
factory classes.
Create and Execute a Test Suite
A test suite is a collection of Apex test classes that you run together. For example,
create a suite of tests that you run every time you prepare for a deployment or
Salesforce releases a new version. Set up a test suite in the Developer Console to
define a set of test classes that you execute together regularly.
Add a Test Utility Class
Let‟s refactor the previous test method by replacing test data creation with a call
to a utility class method. First, you need to create the test utility class.
The TestDataFactory class is a special type of class—it is a public class that is
annotated with @isTest and can be accessed only from a running test. Test utility
classes contain methods that can be called by test methods to perform useful tasks,
Page | 16
such as setting up test data. Test utility classes are excluded from the org‟s code
size limit.
Test for Different Conditions
One test method is not enough to test all the possible inputs for the trigger. We
need to test some other conditions, such as when an account without opportunities
is deleted. We also need to test the same scenarios with a bulk number of records
instead of just a single record.
Run All Test Methods
The final step is to run the test methods in our test class, now that the class
contains more comprehensive tests and has been refactored to use a test data
factory.
Check the results in the Tests tab by expanding the latest test run. The test run
should report that all tests passed!
Page | 17
1.3 ASYNCHRONOUS APEX
Asynchronous Apex is used to run processes in a separate thread, at a later time. An
asynchronous process is a process or function that executes a task "in the
background" without the user having to wait for the task to finish.
Here‟s a real-world example. Let‟s say we have a list of things to accomplish before
our weekly Dance Revolution practice. Your car is making a funny noise, you need
a different color hair gel and you have to pick up your uniform from your mom‟s
house. You could take your car to the mechanic and wait until it is fixed before
completing the rest of your list (synchronous processing), or you could leave it there
and get your other things done, and have the shop call you when it‟s fixed
(asynchronous processing). If you want to be home in time to iron your spandex
before practice, asynchronous processing allows you to get more stuff done in the
same amount of time without the needless waiting.
The key benefits of asynchronous processing include:
● User efficiency
● Scalability
● Higher Limits
This module consisted of five units:
● Use Future Methods
● Use Batch Apex
● Control Processes with Queueable Apex
● Schedule Jobs Using the Apex Scheduler
● Monitor Asynchronous Apex
Page | 18
Future Apex
Future Apex is used to run processes in a separate thread, at a later time when
system resources become available.
When using synchronous processing, all method calls are made from the same
thread that is executing the Apex code, and no additional processing can occur until
the process is complete. You can use future methods for any operation you‟d like
to run asynchronously in its own thread. This provides the benefits of not blocking
the user from performing other operations and providing higher governor and
execution limits for the process.
Batch Apex
Batch Apex is used to run large jobs (think thousands or millions of records!) that
would exceed normal processing limits. Using Batch Apex, you can process records
asynchronously in batches (hence the name, “Batch Apex”) to stay within platform
limits.
If you have a lot of records to process, for example, data cleansing or archiving,
Batch Apex is probably your best solution.
Here‟s how Batch Apex works under the hood. Let‟s say you want to process 1
million records using Batch Apex. The execution logic of the batch class is called
once for each batch of records you are processing. Each time you invoke a batch
class, the job is placed on the Apex job queue and is executed as a discrete
transaction.
Page | 19
Ǫueueable Apex
Released in Winter '15, Queueable Apex is essentially a superset of future methods.
We took the simplicity of future methods and the power of Batch Apex and mixed
them together to form Queueable Apex!
It gives you a class structure that the platform serializes for you, a simplified
interface without start and finish methods and even allows you to utilize more than
just primitive arguments! It is called by a simple [Link]() method,
which returns a job ID that you can monitor.
Scheduled Apex
The Apex Scheduler lets you delay execution so that you can run Apex classes at a
specified time. This is ideal for daily or weekly maintenance tasks using Batch
Apex. To take advantage of the scheduler, write an Apex class that implements the
Schedulable interface, and then schedule it for execution on a specific schedule.
Monitoring Asynchronous Jobs
The great thing about async jobs is that they work silently in the background. The
tough thing about async jobs is that they work silently in the background. You can
monitor the status of all jobs in the Salesforce user interface. From Setup, enter
Jobs in the Quick Find box, then select Apex Jobs.
If you have many batch jobs, use the Batch Jobs page to view only batch jobs. To
open the Apex Batch Jobs page, click the link at the top of the Apex Jobs page.
Use the slider in the Apex Batch Jobs page to select a specific date range and
narrow down the list of batch jobs displayed. You can view past jobs that haven‟t
been deleted yet. The Batch Jobs page groups jobs by the batch class.
Page | 20
1.4 APEX INTEGRATION
An Apex callout enables you to tightly integrate your Apex code with an external
service. The callout makes a call to an external web service or sends an HTTP
request from Apex code, and then receives the response.
Apex callouts come in two flavors.
● Web service callouts to SOAP web services use XML, and typically
require a WSDL document for code generation.
● HTTP callouts to services typically use REST with JSON.
These two types of callouts are similar in terms of sending a request to a service
and receiving a response. But while WSDL-based callouts apply to SOAP Web
services, HTTP callouts can be used with any HTTP service, either SOAP or
REST.
This module consisted of three units:
● Apex REST Callouts
● Apex SOAP Callouts
● Apex Web Services
Apex REST Callout
REST callouts are based on HTTP. To understand how callouts work, it‟s helpful
to understand a few things about HTTP. Each callout request is associated with an
HTTP method and an endpoint. The HTTP method indicates what type of action is
desired.
Page | 21
The simplest request is a GET request (GET is an HTTP method). A GET request
means that the sender wants to obtain information about a resource from the
server. When the server receives and processes this request, it returns the request
information to the recipient.
A GET request is similar to navigating to an address in the browser. When you
visit a web page, the browser performs a GET request behind the scenes. In the
browser, the result of the navigation is a new HTML page that‟s displayed. With a
callout, the result is the response object.
Apex SOAP Callout
In addition to REST callouts, Apex can also make callouts to SOAP web services
using XML. Working with SOAP can be a painful (but necessary) experience.
Fortunately, we have tools to make the process easier.
WSDL2Apex automatically generates Apex classes from a WSDL document. You
download the web service's WSDL file, and then you upload the WSDL and
WSDL2Apex generates the Apex classes for you.
The Apex classes construct the SOAP XML, transmit the data, and parse the
response XML into Apex objects. Instead of developing the logic to construct and
parse the XML of the web service messages, let the Apex classes generated by
WSDL2Apex internally handle all that overhead. If you are familiar with
WSDL2Java or with importing a WSDL as a Web Reference in .NET, this
functionality is similar to WSDL2Apex.
Page | 22
Expose Your Apex Class as a Web Service
You can expose your Apex class methods as a REST or SOAP web service
operation. By making your methods callable through the web, your external
applications can integrate with Salesforce to perform all sorts of nifty operations.
For example, say your company's call center is using an internal application to
manage on-premises resources. Customer support representatives are expected to
use the same application to perform their daily work, including managing case
records in Salesforce. By using one interface, representatives can view and update
case records and access internal resources. The application calls an Apex web
service class to manage Salesforce case records.
Expose a Class as a REST Service
Making your Apex class available as a REST web service is straightforward.
Define your class as global, and define methods as global static. Add annotations
to the class and methods.
Expose a Class as a SOAP Service
Making your Apex class available as a SOAP web service is as easy as with
REST. Define your class as global. Add the webservice keyword and the static
definition modifier to each method you want to expose.
Page | 23
2. PROCESS AUTOMATION SPECIALIST SUPERBADGE
A Process Automation is a process of automating various business processes and
workflows within an organization. It analyzes existing manual processes and design
automated solutions to improve efficiency, accuracy, and productivity.
It uses various tools and techniques such as software bots, workflow management
systems, and scripting languages to automate tasks, reducing human involvement
and errors.
Process automation is the use of technology to automate repetitive, manual, or rule-
based tasks and workflows in business operations. The goal is to achieve
organizational goals, such as: producing a product, hiring and on boarding an
employee, and providing customer service.
A process or task which basically you want to automate for your business. In other
words common tasks which we do on regular basis in our organization, if we want
that task automatically done by salesforce (without manual intervention) is called
Automation process.
It includes demonstrating the knowledge of automation, enhancement, and
troubleshooting for approval processes. Also, Identifying Flow elements and the
best practices for scalability and improved performance and demonstrating our
knowledge of screen flows and screen flow distribution.
Page | 24
Under this SuperBadge, the prerequisites that we completed were:
Concepts Tested in This Superbadge:
● Approval processes
● Flow elements and resources
● Screen flows
Process Automation Specialist Superbadge
The Process Automation Specialist Superbadge is a Salesforce credential
composed of three superbadges-
● Approval Process Specialist Superbadge
● Flow Elements and Resources Specialist Superbadge
● Screen Flow Specialist Superbadge
Page | 25
2.1 APPROVAL PROCESS SPECIALIST SUPERBADGE
The Salesforce approval process is an automated workflow that allows
organizations to approve records within Salesforce. It helps streamline the decision-
making for tasks that require approval, such as discounts, expenditures, or contract
terms.
Sales professionals frequently require transaction validation from internal
departments like legal or accounting, typically resulting in extensive email
correspondence to secure confirmations.
Recognizing the time-intensive nature of this process, Salesforce offers a built-in
approval mechanism.
The Approval Process in Salesforce stands out as one of the most versatile features,
offering vast potential for automating approvals across your organization for:
● Opportunities,
● Quotes,
● Campaigns,
● Leads,
● Custom objects.
With this functionality in place, approvals can be efficiently requested with just a
single click, streamlining the entire procedure.
Page | 26
Approval Process Management
In Approval Process Management, We created an approval process with specific
criteria, outcomes, and approvers, and also modified an approval process to reflect
new criteria.
Concepts Tested in This Superbadge
● Approval Actions
● Approval Requests
● Approval Steps
● Assigned Approvers
Approval Process Troubleshooting
Use the approval process troubleshooting skills to increase productivity. In
Approval Process Troubleshooting, We troubleshot an approval process, and also
modified an approval process to reflect new criteria.
Concepts Tested in This Superbadge
● Approval Requests
● Approval Steps
● Assigned Approvers
● Delegated Approvers
● Queues in Approvals
To complete these superbadges unit, we created a special Developer Edition org
that contains special configuration and sample data. Note that these Developer
Edition org is designed to work with the challenges in these superbadges unit.
Page | 27
2.2 FLOW ELEMENTS AND RESOURCES SPECIALIST
SUPERBADGE
The Salesforce flow elements and resources answer questions relating to flow
elements and their interactions, flow performance optimization, flow
administration, configuration, and activation.
Concepts Tested in This Superbadge
● Action elements in flow automations
● Using Get Records, Update Records, Decision, Assignment, and Loop
elements in a flow
● Collection filters and formulas
● Automation scalability
● Flow configuration
Flow Fundamentals
Flow Fundamentals configure flow actions, elements, and more to automate
business processes, update existing flows to enhance automation, use flows to send
emails, calculate values, and update records. It creates Record elements using
Resources and Flow Actions to save a record to a record variable. It includes
creating a formula in a flow and differentiating between benefits and limitations of
different types of flows.
Flow Optimization
Flow Optimization streamlines existing flows to support scalability and enhance the
user experience, optimize existing flows, enhance existing flows to automate
Page | 28
manual processes, adjust a flow so that it only runs on bulk record import. It
provides the features of collecting filters, scaling automation and user experience.
Flow Administration
Flow Administration delivers improved performance with flow adjustments and
enhancements adjust existing automations for enhanced performance and
functionality, solve for requirements allowing users appropriate access and
notifications. It includes working with different versions of flows, flow Trigger
Explorer and Process Automation Settings.
To complete these superbadges unit, we created a special Developer Edition org
that contains special configuration and sample data. Note that these Developer
Edition org is designed to work with the challenges in these superbadges unit.
Page | 29
2.3 SCREEN FLOW SPECIALIST SUPERBADGE
Salesforce Screen Flows are launched from buttons or are displayed as components,
allowing users to view information and launch processes. Screen Flows are used for
guiding users through complex processes one step at a time while collecting
required user input. They are a great way to display information on record pages
based on logic that may not be possible for formula fields.
The Screen Flow Superbadge answer questions relating to screen flow
configuration and screen flow distribution.
Salesforce Screen Flows help users save time and avoid mistakes by streamlining
complex business processes. This allows them to spend more time doing what
they do best while providing a cleaner data environment.
One process that Screen Flows are great for is the detailed management of records
related to another record. If, for example, our client has a number of email lists
that their customer contacts can subscribe to.
Not only do they provide internal users with streamlined processes that can
include exact information needed for internal users, they are also an excellent way
to allow external users on Salesforce Experience Sites to complete actions that
might otherwise be too complex.
Concepts Tested in This Superbadge
● Screen flow elements and assignments
● User experience considerations for screen flows
● Screen flow distribution across user interfaces
● Screen flow visibility
Page | 30
Screen Flow Specialist Superbadge
The Screen Flow Specialist Superbadge is a Salesforce credential composed of
two superbadge units.
● Screen Flow Fundamentals Superbadge Unit
● Screen Flow Distribution Superbadge Unit
Screen Flow Fundamentals
Screen Flow Fundamentals work with screen flows and elements to streamline
data management, configure a screen flow to collect information from users, use
Flow elements and actions to create detailed records and use Get Records
elements to find and update matching records. It includes Screen flows and Flow
elements with their actions.
Screen Flow Distribution
Screen Flow Distribution optimize and distribute screen flows across user
interfaces according to requirements and enhance existing flows to improve the
user experience. It includes distributing flows and flow interactions with
Lightning record pages and apps.
To complete these superbadges unit, we created a special Developer Edition org
that contains special configuration and sample data. Note that these Developer
Edition org is designed to work with the challenges in these superbadges unit.
Page | 31
CONCLUSION
In conclusion, the Salesforce Developer Virtual Internship provided an invaluable
opportunity to gain hands-on experience and insights into the world of Salesforce
development. Throughout the internship, various aspects of Salesforce, including
customization, configuration, and development, were explored and applied in real-
world scenarios. The internship highlighted the significance of understanding
business processes and requirements to tailor Salesforce solutions effectively.
Moreover, the internship served as a platform to enhance technical proficiency in
Apex, Visualforce, Lightning components, and other Salesforce technologies. It
provided a structured learning environment, allowing for experimentation,
troubleshooting, and the development of best practices in Salesforce development.
Overall, this Internship helped to enhance and develop my skills, abilities, and
knowledge about the development of CRM and the launching of apps through their
development environment known as orgs.
It was a good experience and knowledge about how the tech works. The
environment of the online Internship has opened me up about how the company
works. The treatment by the company was just, equitable and professional.
Page | 32