Internship Report

A Salesforce Developer Virtual Internship Report Submitted to

Jawaharlal Nehru Technological University Anantapur,

Ananthapuramu
in partial fulfillment of the
requirements for the award of the degree
of

BACHELOR OF TECHNOLOGY
IN
Computer Science and Systems engineering

M VENUGOPAL NAIK 22125A1509

Department of Computer Science and Systems Engineering

SREE VIDYANIKETHAN ENGINEERING
COLLEGE
(AUTONOMOUS)
(Affiliated to JNTUA, Ananthapuramu, Approved by AICTE, Accredited by NBA& NAAC)
Sree Sainath Nagar, Tirupati – 517102, A.P., INDIA 2023 -24
 Department of Computer Science and Systems Engineering
SREE VIDYANIKETHAN ENGINEERING COLLEGE
(AUTONOMOUS)
(Affiliated to JNTUA, Ananthapuramu, Approved by AICTE, Accredited by NBA & NAAC)
Sree Sainath Nagar, Tirupati – 517102, A.P., INDIA 2023 -24

Certificate

This is to certify that, the Salesforce Virtual Internship entitled

“Salesforce Developer Virtual Internship”

is the bonafide work done by

M VENUGOPAL NAIK 22125A1509

in the Department of Computer Science and Systems Engineering, Sree Vidyanikethan

Engineering College (Autonomous), Sree Sainath Nagar, Tirupati and is submitted to Jawaharlal
Nehru Technological University Anantapur, Ananthapuramu for partial fulfillment of the
requirements of the award of B-Tech degree in computer science and systems engineering during the
academic year 2023-2024.

Supervisor: Head of the Dept.:

Mr.M. Ramu M.Tech., Dr. K. Ramani, M.Tech., Ph.D.

Assistant Professor Professor
Dept. of Computer science and systems Dept. of Computer science and
engineering systems engineering
Sree Vidyanikethan Engineering Sree Vidyanikethan Engineering
College Sree Sainath Nagar, Tirupati – College Sree Sainath Nagar,
517102 Tirupati 517102

INTERNAL EXAMINER EXTERNAL EXAMINER

ii
COMPLETION CERTIFICATE

ii
 ABSTRACT

Cloud computing has revolutionized the way organizations approach data storage, processing, and
application deployment. By providing on-demand access to computing resources, cloud technology
enables scalability, flexibility, and cost-efficiency, supporting diverse business and technological needs.
Core service models—Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a
Service (SaaS)—offer varying levels of control and convenience to users. Key benefits include reduced
capital expenditure, improved collaboration, and enhanced data security when implemented with best
practices. Despite challenges such as data privacy concerns and dependency on internet connectivity,
cloud computing continues to evolve, driven by advances in virtualization, containerization, and
orchestration technologies. This abstract underscores the growing importance of cloud solutions in
driving digital transformation and supporting innovative applications across industries.

Keywords: Lightening app builder, Flowbuilder, Flow Orchestration, Automated actions, Migration flow.

iii
 TABLE OF CONTENTS

CERTIFICATE i

ABSTRACT ii

TABLEOF CONTENTS iv

LISTOF FIGURES vi

1. INTRODUCTION 1

2. MODULE 1 : [LIGHTENING APP BUILDER] 2-8

2.1 Get Started with the Lightning App Builder

2.2 Build a Custom Home Page for Lightning Experience

2.3 Build a Custom Record Page for

LightningExperienceand the

Salesforce Mobile App

2.4 Build an App Home Lightning Page

2.5 Work with Custom Lightning Components

3. MODULE 2 : [FLOW BUILDER] 9-17

3.1 Learn About Flow Resources and Variables

3.2 Create a Variable
3.3 Add Screens to Your Flow
3.4 Add Logic to Your Flow
3.5 Add Actions to Your Flow

4. MODULE 3: [HELP ARTICLE - AUTOMATE YOUR

BUSINESS PROCESSES] 18-20
4.1 Migration to Flow
4.2 Flow Orchestration
4.3 Automated actions

iv
5. MODULE 4: [Automate BusinessProcesses for a 21-27
Recruiting App]
5.1 Build a Process for Creating Interviewer Records
5.2 Laythe Groundwork for an Approval Process
5.3 Create an Approval Process
5.4 Create a Process for Submitting Positions for Approval
5.5 Create a Candidate Rating Flow

6. CONCLUSION 28

7. REFERENCES 29

v
 List Of Figures

S.NO Figure name Page No

2.1 Lightning App User 3

Interface

2.2 Custom Home Page 4

2.3 Activation ofnewHome 5

page
2.4 Custom Lightning 5
Page

2.5 Dynamic Page 6

2.6 App Page 6

2.7 Adding Page 7

2.8 Lightning 7

experience in app

2.9 Component page 8

3.1 Runtime experiences 9

3.2 Name Component 12

3.3 Decision Flow 13

3.4 Updating Variable 13

3.5 Reconnecting Elements 14

3.6 Get Records 15

3.7 Update Records 16

3.8 Connect elements 17

vi
4.1 WorkFlow Rules 19

4.2 Migration tool 19

5.1 Setting Process 22

5.2 ApprovalProcess 23

5.3 Add an Screen element 25

5.4 Setting an start element 26

5.5 Deploying Flow 27

vii
 1. INTRODUCTION

Salesforce now offers a variety of software solutions and platforms for developers to create and
share custom software/applications. Salesforce is used in the form of SaaS or PaaS by tech giants
such as Google, Twitter, Amazon, and Facebook. Giving users everything they need in one place is
simple with the point-and-click Lightning App Builder, which makes it simple to create custom
pages for the Salesforce mobile app and Lightning Experience. The Lightning App Builder is yet
another one- stop shop for configuring Lightning apps.
Custom actions known as flow actions are used to create flows. Without writing code, they offer a
safe approach to develop customised functionality. Only the Salesforce mobile app and Lightning
Experience offer flow activities. The Automated Process User is used by Flow Orchestration to
provide notifications. The Organization-Wide Email Address (i.e., the 'From' Address that your
organisation will send as) must be specified in order for the Automated Process User to send email.
In the Process Automation Settings, that is accomplished. The maximum level of access is provided
by triggered flows that employ the Automated Process User and conduct a flow in System Context
without Sharing. However, some items, like Connect APIs, are not accessible by default to
Automated Process Users. Nevertheless, the APU can be given a permission set. Although you can't
do it via Setup UI, you can use Developer Console to provide the User with the alias "autoproc" a
permission set.

1
 MODULE -1
Lightening App Builder

2
 Lightening App Builder

2.1 Get Started with the Lightning App Builder:

a) How Lightening app builder works?

 With Lightening app, Users can build a dashboard-style apps, single page apps,
point-appsto solve a particular task.
 You can create pages for the Lightning Experience or the Salesforce mobile
app using acustom layout called a Lightning page.
b) Lightning Components:
 In the Lightning App Builder, you can add a Lightning component,
which is asmall,adaptable, and reusable element, to a Lightning
page.
 Lightning components are Standard Components, Custom
Components, Third-partyComponents.
c) Lightning app builder user interface:
 Header shows a labeland contains a page list whereuser can see a last 10 modified pages.
 Toolbar is used to cut and copy the page content, undo and redo or
activating thelighteningpage
 Lightning app page canvas is used to drag a component to rearrange.

Fig.2.1 : Lightening App user Interface

3
 d) Lightning Page types:
 By using app page, users can directly create an home page for an third-party app
that canadd directly into salesforce.
 Custom home pages is created by lightning app builder.
 Byrecord page, users can create an customised record page.
2.2 Build a Custom Home Page for Lightning Experience
a) Create a Custom Home Page for Lightning Experience:
 After login into salesforce, go to setup->enter appbuilder and go to lightning app builder.
 Click on new->go to home page->set up through wizard and name the page
 Add todayevents and todaytasks to the Home page and Click save.

Fig.2.2 : Custom Home page

b) Roll Out Your Custom Home Page to Your Lightning Experience Users:
 To activate new page user can have three options.
 Click app and profile, Select the Sales app, then click Next.
 Scroll down the list of profiles and select System Administrator, then click Next.
 Review the assignment, and then click Save. then clicks assign to apps and profiles.

4
 Fig.2.3 : Activation of new home page
2.3 Build a Custom Record Page for Lightning Experience and the Salesforce
MobileApp:
a. Create a Custom Lightning Record Page
 Go to setup->App Builder->Select lightning app builder.
 Select record page->start stepping through wizard.
 Choosethe Header, Subheader, Right Sidebar template, and click Finish.
 Choose the Header, Subheader, Right Sidebar template, and click Finish

 Add a Chattercomponent to the lower right region.

 Add a Tabs component to the lower left region.

Fig.2.4 : Custom Lightning page

5
 b) Make Your Record Page Dynamic:
 Add a rich component to text to above component page
 Make a component bold and italic->Keep display as card and select
 This is used to create dynamic record with all filters.
 Used to retrieve the selected records.

Fig.2.5 : Dynamic Page

 After Filtering and adding page, Activate the page.
2.4 Build an App Home Lightning Page:
a) Create an App Page:
 Go to setup->App page->Name a page
 Select a regions fo app page->Inproperties pane->Select accounts
 Click page->Select->Add actions to page->Click done
 App page is created.

Fig.2.6 : App Page

6
b) Add Your App Page to Lightning Experience:
 To use the page->Activate the page
 After activation->click on Lightning experience tab
 Select the sales app->Add page to app
 Select the mobile Navigation->Add page to app

Fig.2.7 : Adding Page to app

c)Test Your App Page in Lightning Experience:
 Fromapp launcher->select page
 Click top and accounts ofnavigation barapp looks like:

Fig.2.8 : Lightning experience in salesforce app

7
2.5 Work with Custom Lightning Components:
a) Custom Lightning Components in the Lightning App Builder:
 Custom Ligtning components is created using two programming
modules i.e.Lightningweb components and aura components.
 Components appear in Lightning components page
b) Install a Custom Lightning Component:
 To install a package->enter a package id->Click on install
 Install for admins only.
c) Add the Custom Lightning Component to Your App Page:
 After installation ofpackage->Add a component to a page
 Add aopportunityto a list view component
 Deselect Has opentasks->then click save
 Page is added to Lightning component.
d) Test the Custom Component:
 Openthe app on mobile->login into trailhead
 To add new custom component->Go to top and accounts->scroll down until
thenewcomponent

Fig.2.9 : Custom component on mobile app

8
3. MODULE 2

Flow Builder

9
 FLOW BUILDER
 Before starting flow builder, first complete the build a simple flow project.

3.1 Learn About Flow Resources and Variables:

a) Flow Resources:

 Aconstant is a fixed figure, like the tax rate.

 A screen component's option is represented by the words Choice, Picklist Choice
Set, orRecordChoice Set. The label and value of each option are explicitly set
using the choiceresource. The values of a picklist (or multi-select picklist) field in
your org or a filtered list of records are used to produce choices for you in choice
sets, however.
 Similar to a formula field, formula represents a determined value. Create a formula,
forinstance,that determines the time in 30 days from today, and use that formula to
determine when an opportunity will close.

b) Introducing Variables:

 A variable serves as a stand-in for a value you are unsure of. Although variables are
the only flow resources that can change while the flow is in progress, all flow
resources are placeholders.

3.2 Create a Variable:

a) Create a Variable:

 Fromsetup->select flows->select screen flow

 Fromtoolbox, click manager->Type the name of variable and description

 Ifuser want to allow many variables->select multiple variables

 Choosetheobject whose record values you want to store when choosing record variables.

b) Store Information in a Flow Variable:

 A variable is only as useful as the values it contains, and Flow Builder provides a
few optionsforfilling that variable with data.

10
3.3 Add Screens to Your Flow
a) The Runtime Experiences:

 Lightning runtime and Classic runtime arethe two distinct runtime experiences for flows.

 Lightning runtime resembles Lightning Experience, as its name would imply,

whereasClassicruntime resembles Visualforce.

Fig.3.1 : RunTime experiences

b) The Screen Element:

 Screen component(1) consists of all screen available in org

 In Screen canvas, user can build the screen

 The properties pane displays either the screen's properties or the properties of
thechosencomponent, depending on the canvas selection.

c) Name Component:

 Name component displays fields only first name and last name.The label for component is name.

 The fields on the (!contact") record variable are where the First Name and Last
Name valuesarekept.

11
 Fig.3.2 : Name Component

c) Toggle Component:

 When toggle component opens, it shows a message “Contact already exists, update the record”

 Thetoggle's label reads "Update existing" when it is turned on.

 If not, the label for the toggle is Create other contact.

3.4 Add Logics to flow

a) Create Branches with Decision Elements:

 The final result, known as the default outcome, is made available to you via Flow
Builder.Itserves as a backup.

 The flow choosesthe connector for the default outcome if the prerequisites for
all otheroutcomesare not satisfied.

 Look at the decision built in the New Contact flow

12
 Fig.3.3 : Decision Flow

b) Update Variable Values with Assignment Elements:

 An Assignment element is the simplest approachto alter a variable's value.

 Depending onthe operator chosen and the value entered, the variable's value changes.

 Value for date variables is the specified Variable's value multiplied bythe number ofdays.

 Thetext input or chosen for Value is appended to the end ofthe variable for text variables.

Fig.3.4 : Updating Variable

c) Update the Flow:

 A decision element verifies two possibilities: if the user chose to alter the current
record or not, and whether a contact record matching the user's selection already
exists.

 So that you only utilise the Get Records element if the user choose to edit a
matched record, relocate the first condition into its own Decision element.

d) Create a New Decision:

 Onto the canvas, drag a Decision element.

 Label the choice: Update If Existing? Update If Existing is automatically assigned as

the APIName.

13
  Assign the word "Yes" to the first result. Make Update Yes the new API name. This makes it
simple to read the label for the choice connector while making it simple to distinguish the
name of that outcome from others in the Manager tab.
 Configure one condition for the outcome and leave When to Execute Outcome as-is.

e) Update the Original Decision:

 Click Update or Create? twice.

 Locate the condition that corresponds to the new update-if-existing? decision rule that you
added."! update toggle. value" should be present in the Resource field.

 Click the Delete icon for that circumstance.

 Select "Done"

f) Reconnect the Elements:

 Eliminate the link between Find a Match and Contact Information.

 On the connector, click. Blue is the new color when it is highlighted.

 Delete the current document.

 Update Contact Information if Existing by Connecting.

 Update If Existing? to Connect and Find a Match. Choose the Yes response when prompted,
then click Done.

Fig.3.5 : Reconnecting elements

14
3.5 Add Actions to Your Flow
a) Get Records:

 You specify which object to look up, howto filter the object's records, and how to
rank the filtered data in a Get Records element.

 Next, you decide whether to manually save variables and how many records to store.

Fig.3.6 : Get Records

b) Update Records Elements:

 The flow updates the records using the other field values in the variable whether you choose
to use a record variable or record collection variable. It first utilises the IDs in the variable to
identify the records to update.

 If not, you can manually provide filter criteria to determine which records need updating. You
must manually choose which field values to modify when using this option.

15
 Fig.3.7 : Update Records

c) Create Records Elements:

 You have two options for setting the values ofa single record.

 Select to set the record fields using all the values from a record variable if you've already filled
in a record variable with the field values for the new record. Next, decide whether to use a
record variable or a record collection variable. The flow enters the ID of the newly formed
record in the ID field of the record variable when the record is created.

 Set the record fields using different variables, resources, and literal values to manually map
value from different resources in the flow.

d) Action Types:

You can utilise these actions in Salesforce without developing or configuring anything else.

 Share on Chatter.

 Email is sent.

 For approval, submit.

 A permission set can be activated or deactivated.

16
e) Connect the Elements:

 Connect the Post to Chatter core action to the elements Create Contact and Update Contact.

 Connect the Confirm screen to the Post to Chatter core function.

 Keep the flow going and disregard the caution.

Fig.3.8 : Connect the elements

17
 4. MODULE 3

Help Article-Automate Your Business Processes

18
 HELP ARTICLE - AUTOMATE YOUR BUSINESS
PROCESSES
4.1 Migration to Flow:
a) Workflow Rule with an Email Alert:
 Most workflow rules are used to change fields on the same record or send email alerts.
Although triggered flows are known to be quicker than these kinds of workflow rules,
the yare nonetheless faster. Move your workflow rules over to Flow Builder right away.

Fig.4.1 : WorkFlow rules

 The migration tool does a great job and even adds the workflow rule name and
descriptionin the details of the new flow.

Fig.4.2 : Migration Tool

19
 4.2 Flow
Orchestration
a) What Is Flow Orchestration?
 You may develop orchestrations—multi-step processes that interact with several users—
using Flow Orchestration, formerly known as Orchestrator. An orchestration is a
collectionof stages, each of which is made up of a number of actions. Interactive and
background steps are both possible on a stage. An allocated user and a predetermined
screen flow are used in interactive steps.
 On the page layout for the type of record that the interactive step impacts, an
administratoradds the Orchestrator Work Guide Lightning App Builder component. The
selected user gets an email with a link to their assigned action when an orchestration
executes an interactive step.
4.3 Automated
Actions
a) Email Alert
Actions:
 Email alerts are emails that are created by a machine and sent to certain recipients. The
typical email bodytext and recipient list make up these steps.
 Email alerts can be connected to workflows, processes, flows, approval procedures, or
entitlement processes. Additionally, they are accessible via the Invocable Actions REST
API endpoint.
b) Outbound Message Actions:
 Information is sent to a specified endpoint, such as an external service, via an outbound
message. From Setup, you setup outgoing messages. You must use SOAP API to build
a listener for the messages and configure the external endpoint.
 Outbound communications can be connected to flows, workflow regulations, approval
procedures, or entitlement procedures.

20
 5. MODULE 4
Automate business Processes for a Recruiting App

21
 Automate Business Processes for a Recruiting App

5.1 Build a Process for Creating Interviewer Records:

a) Set Up a Process with Process Builder:

 Fromsetup->Go to Process Builder->Name the record and start the process

 Click add object->select position frompickup list

 Set the conditions by selecting Conditions are met under Criteria for Executing Actions.

Fig.5.1 : setting process

 Byclicking +, link the interviewer's recordto the job's record. Rowand adding the specifics.

b) Test the Process:

 Beforetesting->Activate the process

 Open App launcher, then click recuriting

 Select the record named Nontechnical position, and fill the details.

5.2 Lay the Groundwork for an Approval Process

a) Create a Folderand Email Templates
 Fromsetup->Go to classic templates->Create an folder

 Give an folder name and give an access to everyone

 Click new template->Make sure that text is selected

22
b) Create Fields:
 Select Position under Object Manager byclicking Setup.

 Click New after selecting Fields & Relationships.

 Click Next after selecting Lookup Relationship as the Data Type.

 Click Next after selecting User fromthe Related To picklist.

 As the Field Label, type

Approver1.Edit Position Layout:

 Click Page Layouts while you are still examining Position in the Object Manager.

 After selecting Edit, click the Down arrow next to Position Layout.

 Drag Section fromthe palette under the Experience & Education section to create a new section.

 Drag the Information section's Approver 1, Approver 2, and Approver 3 fields

over totheApprovers section.

5.3 Create an Approval Process

a) Set Up aMultistep Approval Process:
 Enter "approvalprocesses" in the Quick Find box and choose "approval processes" from Setup.

 Fromthe Manage Approval Processes For picklist, choose Position.

 Select Use Standard Setup Wizard fromthe picklist by clicking Create New
ApprovalProcess,then enter the parameters.
 Put New Position Approval in the Process Name field.

 Select fields fromavailable list

Fig.5.2 : Approval Processes

23
b) Create Approval Steps:
 Under initial submission list, click new, then update the field

 Select an approve status for field

 Click an approval step, and select automatically assign under selected areas

 Create an second step and third approval step.

c)Create the Final Actions:

 Under final approve list, click new, then updatethe field

 Create an new field and approve staus

 Repeat for second and third steps.

5.4 Create a Process for Submitting Positions for Approval

a) Use Process Builder to Create a New Process:

 Fromsetup, go to process builder and add a new component, and continue the process

 Enter a process name and approve the pick list

 Click an add object and select a position fromobject list

 For criteria name, enter a name and make sure the conditions met

 Save activity and click on activate.

5.5 Create a Candidate Rating Flow

a) Create Radio Buttons for Experience:
 Fromsetup, go to flows and create a new flow

 Under flow types, select a screen flow and create an new and select freeform

 Click radio buttons from input section, Enter an experience for a level

 Select an data type field and click inside a field

 Click and add choice and add an two choices for an field and repeat above process

b) Create Radio Buttons for Leadership Skills:

 Click an radio buttons and enter an name to button

 Select an datatype for radio button

 Click into choice field and select excellent.

24
  Add four choices and repeat stepsto choice fields.

 Click text and enter an label Leadership Skills Comments

c) Create Radio Buttons for Core Competencies:

 Click an radio buttons and enter an name to button

 Select an datatype for radio button

 Click into choice field and select excellent.

 Add four choices and repeat stepsto choice fields.

 Click text and enter an label Core Competencies Comment

d) Add Screen Elements:

 Click check box and label for an check box

 Enter an apiname for checkboxes

Fig.5.3 : Add an screen element

25
e)Set a Start Element

 Byclicking and holding the Start circle and moving your mouse to the New
Review element,youmay link the Start element to the New Review Screen
element.

 You can see that a solid line links the two objects.

 Click an create record and label for an record

 Click the Field box under "Set Field Values for the Review" and choose "Job Application_ _c"

Fig.5.4 : Setting an start element

f) Deploy the Flow:

 Fromsetup, go to object manager and select an job application

 Click links and buttons, Select buttonor link

 Select detail page for an link and add an new review for flow and click save

26
Fig.5.5: Deploying flow

27
 6. CONCLUSION

Lightning App Builder can be used to update the branding, navigation, settings, and management of
the lightning pages assigned to that app. A lightning page is a custom layout that can be used to
create pages for the Salesforce mobile app or lightning experience. Without the use of a
programming language, Flow Builder can be used to create code-like logic. The Salesforce Lightning
flow Builder will aid in the creation of various platform automation processes. By automating a
business process, employees can focus on core tasks rather than tedious, repetitive, and often
frustrating tasks.

28
 REFERENCES

 https://trailhead.salesforce.com/content/learn/modules/
lightning_app_builder

 https://trailhead.salesforce.com/content/learn/trails/build-flows-with-
flow-builder

 https://trailhead.salesforce.com/content/learn/projects/automate-
business-processes-recruiting-app

29