SCHOOL OF MECHANICAL ENGINEERING
(SMEC)
FALL SEMESTER (2025-2026)
RECORD
Name
Reg. No.
Course Name
Course Code
Class ID
Slot
R. Imranesa
23BMV1044
Cloud computing
BMEE355E
CH2025260100639
L37+L38+L45+L46
Submitted to:
Dr. Pradeep N
SMEC
Assistant Prof. Sr Gr. II
1
List of Experiments
Ex no.
Title
Pg. No
1
Exercise on Salesforce Exploration and CRM
3-4
2
Exercise on creation custom Salesforce
components
5-6
3
Exercise on data Management & Automation
7-8
4
Exercise on data Security at different levels
9-10
5
Exercise on data Security using Profiles and
Permission Sets
11-12
6
Exercise on reporting & analytics using
Salesforce Reports
13-14
7
Exercise on data visualizations using Salesforce
Dashboard
15-16
8
Exercise on workflow automation
17-18
9
Exercise on workflow automation
19-20
10
Exercise on Customization with Lightning
21-22
2
Exp.1 Exercise on salesforce exploration and CRM
Date: 15/07/2025
Aim:
Salesforce really gives businesses a boost in handling things better. We will check
out the details on this cloud CRM. This cloud CRM pulls together customer data
in one spot, makes daily tasks run smoother, and helps build stronger connections
with clients.
Procedure:
▪ log in to the salesforce platform using trail head cloud domain.
▪ Create your own playground (workspace). you can create your own
playground in profile page → Hand-on args → create playground (or) you
will be able to create your own playground will be visible in task menu.
▪ moved through the Salesforce Home interface. We wanted to get a feel for
the overall layout, the various menus, and all those options for customizing
the workspace.
▪ check CRM Component such as accounts, contact, leads and opportunities.
identify how they connected with managing customer preferences.
▪ Examined different Salesforce modules — Sales Cloud, Service Cloud, and
Marketing Cloud — to identify their specific roles in CRM operations.
▪ Create a new Lead. Set the First Name and the Last Name to. Set the
Company.
▪ Go to your Playground, click the "Leads" tab, click "New," and type in
the information exactly as instructed. Click "Save."
▪ Go back to the Trailhead module page and click the "Verify" button.
Trailhead will automatically check your Playground to see if you did the
task correctly.
3
Conclusion:
This end-to-end exploration really confirms it. Salesforce stands out as a
comprehensive platform overall. It delivers the data model needed to understand
customers better. You also get automated workflows that manage them in an
efficient way. Then there are specialized tools tailored for each department.
Analytics come in to help derive those key insights. On top of that, the
extensibility lets it adapt to just about any business challenge.
4
Exp.2
Date
Exercise on creation of custom salesforce
components
12/08/2025
Aim:
To build a custom Lightning App builder on your local computer, send it to your
Salesforce org, and add it to the Home Page so you can see it in live.
Procedure:
▪ Log in Trailhead platform navigate to existing playground (or) create a new
playground and click Setup.
▪ Click object manager next to home and create a custom object will be
named “client Property” to manage client’s property with appropriate data
type.
▪
Added a Validation Rule to ensure that all required fields were filled
before saving a record.
▪ Create new custom app and make part of the object using lightning builder
app.
▪ Tested the functionality by creating, saving, and editing sample records
within the new component.
▪ Complete the task.
5
Conclusion:
This exercise provides a comprehensive, end-to-end simulation of the entire
declarative development process on the Salesforce platform. The conclusions
we can draw from this are not just about the technical steps, but about the core
philosophy of how to build integrated, user-focused solutions that directly
address business needs and drive real value.
6
Exp.3
Date
Exercise on data management & automation
31/10/2025
Aim:
To understand how Salesforce manages business data efficiently and to explore
automation tools such as Workflow Rules, Process Builder, and Flow for
optimizing repetitive business processes.
Procedure:
▪ Log in Trailhead platform navigate to existing playground (or) create a new
playground and click Setup and navigate to object manager.
▪
▪
▪
▪
▪
▪
▪
Analysed standard object data models like Accounts, Contacts, and
Opportunities in the Object Manager.
Imported data using both the step-by-step Data Import Wizard and the bulk
Data Loader.
Reviewed data recovery (Recycle Bin) and backup (Data Export Service)
functionalities.
Built automations using Process Builder (to update Opportunity Status) and
Workflow Rules (to send Lead notifications).
Designed a Flow to automatically assign new Cases based on priority and
region.
Tested all automations to verify correct system-triggered updates,
notifications, and assignments.
Evaluated how automation reduces manual work and improves data
consistency.
▪ Click Next, then Start Import. Verify the Results.
7
Conclusion:
This demonstrate a comprehensive, hands-on understanding of Salesforce's core
data management and process automation capabilities. By handling the full data
lifecycle—from import and bulk updates to recovery—and building several types
of automated workflows, you've proven your ability to configure the platform to
improve efficiency, reduce manual error, and enforce consistent business
processes.
8
Exp.4
Date
Exercise on data security at different levels
09/08/2025
Aim:
The objective was to gain a practical, hands-on understanding of Salesforce's
multi-layered security. understand how each component works together to protect
data and govern user visibility.
Procedure:
▪ Log in Trailhead platform navigate to existing playground (or) create a
▪
▪
▪
▪
▪
▪
▪
▪
▪
new playground and click Setup
Analysed and modified Organization-Wide Defaults (OWD) for objects
like Accounts and Contacts to set baseline visibility.
Managed Object-Level Security (OLS) by adjusting permissions (Read,
Create, Edit, Delete) on Profiles.
Applied Field-Level Security (FLS) to hide sensitive data (like phone
numbers) from specific users.
Established Record-Level Security using a Role Hierarchy to test how
data access rolls up from junior to senior roles.
Enforced system-level access controls by setting Profile-based Login
Hours and permitted Login IP Ranges.
Strengthened identity verification by activating Two-Factor
Authentication (2FA) for an admin user.
Wrote a criteria-based Sharing Rule to automatically grant record access
to a designated Public Group.
Validated the entire security model by logging in as different test users to
confirm visibility restrictions.
Assessed the overall impact of these configurations on data privacy and
organizational governance.
9
Conclusion:
A comprehensive, multi-layered security framework was successfully configured
and validated. This demonstrated a strong ability to manipulate Salesforce's
declarative security tools to enforce complex business rules. The hands-on testing
confirmed how OWD, Profiles, FLS, and Role Hierarchies interconnect to secure
an organization, protect sensitive information, and ensure that users can only
access the specific data required for their roles, thereby enforcing robust data
privacy and governance.
10
Exp.5
Date
Exercise on data security using profiles and
permission sets
03/08/2025
Aim:
The objective was to gain hands-on experience with Salesforce's user access and
permission framework. This involved a practical exploration of the two primary
tools for managing user rights: Profiles and Permission Sets. The goal was to
configure a restrictive baseline profile, test its limitations, and then use a
Permission Set to strategically grant additional access, demonstrating a flexible
and scalable approach to user security
Procedure:
▪ Accessed the Profiles menu within a Trailhead environment's Setup →
Users → Profiles.
▪ Analysed the baseline permissions for key standard profiles like System
Administrator, Standard User, and Read-Only.
▪ Cloned the Standard User profile to forge a custom one, granting Read,
Create, and Edit on Leads/Opportunities but blocking Delete actions.
▪ Applied this new custom profile to a test user account to prepare for handson validation.
▪ Configured Field-Level Security (FLS) within the profile to mask sensitive
data (like deal amounts) and confirmed invisibility by logging in as the test
user.
▪ Navigated to the Permission Sets menu in Setup to begin building a new,
additive permission layer.
▪ Populated the Permission Set with extra privileges, such as access to
Campaigns and Reports, leaving the base profile untouched.
▪ Assigned the new Permission Set to the test user, observing the immediate
extension of their functional access.
▪ Demonstrated the power of "stacking" multiple Permission Sets to grant
flexible, role-specific access.
▪ Performed comprehensive testing by attempting restricted actions (like
deletion) to confirm the security rules were properly enforced.
11
Conclusion:
demonstrated that Profiles effectively set the foundational, baseline permissions
for a user (including FLS), while Permission Sets act as a flexible, additive layer
to grant extra privileges as needed. This validation confirms the best-practice
method for managing user access, which avoids profile proliferation and allows
for scalable, role-specific permissions.
12
Exp.6
Date
Exercise on reporting & analytics using
salesforce reports
31/10/2025
Aim:
To learn how to create, customize, and analyze Salesforce reports to convert raw
business data into meaningful insights for decision-making. The objective is to
understand how Salesforce’s reporting and analytics tools help track sales
performance, monitor operations, and visualize key business metrics.
Procedure:
▪ Logged in to Salesforce using the Trailhead (Trailblazer) platform and
navigated to the Reports tab from the App Launcher.
▪ Explored the Reports Home Page to understand the different report folders,
templates, and recently viewed reports available to the user.
▪ Created a New Report by selecting the Leads and Opportunities report type
to analyse sales performance.
▪ Added relevant fields such as Lead Source, Opportunity Stage, Amount, and
Close Date to study the relationship between lead generation and revenue
conversion.
▪ Applied Filters to display only records that were Closed Won within the
current fiscal quarter.
▪ Used Grouping features to categorize data by Sales Representative and
Region, allowing for comparative performance analysis.
▪ Customized the report format by switching between Tabular, Summary, and
Matrix views to understand how each format serves different analytical
purposes.
▪ Inserted Charts (bar, pie, and funnel types) into the report to visualize data
trends, revenue distribution, and sales pipeline progress.
▪ Save the report. Created a Custom Dashboard linked to multiple reports,
integrating key metrics such as total sales, top-performing regions, and lead
conversion rates.
13
▪ Configured Dashboard Filters to allow dynamic data visualization, enabling
users to drill down into specific time periods or sales teams.
▪ Analysed the generated insights to evaluate business performance, identify
weak areas, and suggest data-driven improvements.
Conclusion:
This experiment demonstrated how Salesforce’s reporting and analytics tools
transform stored business data into actionable intelligence. By creating
customized reports and dashboards, users can monitor key performance
indicators, forecast sales trends, and make informed strategic decisions.
14
Exp.7
Date
Exercise on data visualization using
salesforce dashboard
31/10/2025
Aim:
The objective was to build and configure a comprehensive Salesforce dashboard
from start to finish. This involved translating raw data from multiple underlying
reports into a consolidated, interactive, and visually intuitive "Sales Performance
Dashboard." The goal was to leverage advanced features like component
customization, dynamic filters, user-based visibility (Dynamic Dashboards) for
business users.
Procedure:
▪ Accessed the Dashboards tab within a Trailhead practice environment.
▪ Initiated the creation of a new "Sales Performance Dashboard" to visually
track business analytics.
▪ Configured the dashboard's storage folder and set sharing permissions for
relevant users and teams.
▪ Populated the dashboard by adding components sourced from underlying
reports (e.g., Leads by Source, Opps by Stage).
▪ Utilized a variety of component types (bar charts, pie charts, funnel charts,
gauges) to best represent different metrics.
▪ Ensured all visual components were correctly linked to their respective live
report data sources.
▪ Implemented dashboard-level filters (like Region and Time Period) to
enable dynamic, interactive data segmentation.
▪ Customized component properties, including titles, legends, and colour
schemes, to enhance readability.
▪ Configured the dashboard to run as the "viewing user" (Dynamic
Dashboard) to respect individual data access levels.
▪ Set up an automated refresh schedule, ensuring dashboard data remains
current without manual intervention.
▪ Verified the dashboard's responsiveness and visual integrity on both
desktop and mobile layouts.
15
▪ Analysed the completed dashboard to derive actionable insights on sales
trends and performance gaps.
Conclusion:
A fully functional, multi-component "Sales Performance Dashboard" was
successfully built and deployed. This process demonstrated a comprehensive
ability to transform disparate report data into a single, high-level visual tool. By
configuring interactive filters, dynamic user visibility, and automated refreshes,
the dashboard was proven to be an effective, scalable, and user-friendly asset for
analysing sales performance, identifying trends, and enabling data-driven
decision-making
16
Exp.8
Date
Exercise on workflow automation
31.10.2025
Aim:
The objective was to gain hands-on proficiency with Salesforce's suite of
declarative automation tools. This involved building, testing, and comparing
three distinct tools: the legacy Workflow Rules, the more robust Process Builder
And to understand their individual capabilities, limitations, and strategic place in
the platform.
Procedure:
▪ Accessed the Workflow Rules configuration page via the Setup menu in a
Trailhead org.
▪ Configured a new Workflow Rule on the Lead object, designed to fire
when a Lead's status is "Hot."
▪ Set the Evaluation Criteria for the rule to trigger on record creation or
when edited to meet the criteria.
▪ Created an Email Alert action, complete with a template, to notify the sales
team of the "Hot" lead.
▪ Added a second action, a Field Update, to automatically set the lead's
"Priority" to "High."
▪ Activated the workflow and verified its logic by creating test leads,
confirming it fired only for "Hot" leads.
▪ Shifted to Process Builder to automate a sales process: creating a followup Task when an Opportunity stage hits "Proposal/Price Quote."
▪ Defined the process's trigger criteria and added multiple actions, including
Create a Record (Task) and Post to Chatter for team visibility.
▪ Deployed the process, then tested it by moving a sample Opportunity to
the "Proposal" stage and checking for the automated task.
▪ Explored Flow Builder to construct a Screen Flow, designing a userfacing interface for collecting customer feedback.
▪ Activated the flow and placed it on a Lightning page, testing the end-toend process from user input to the database update.
17
▪ Compared the features of Workflow Rules, Process Builder, and Flow,
noting their differences in power and aligning with the best practice of
prioritizing Flow for new automations.
Conclusion:
series of automations was successfully built, tested, and validated across all three
of Salesforce's primary declarative tools. This practical application demonstrated
a clear understanding of each tool's specific strengths. It confirmed the ability to
use Workflow Rules for simple, single-object actions, Process Builder for more
complex, multi-action processes, and Flow for sophisticated, interactive user
experiences. This hands-on comparison solidified the understanding of why Flow
is now the recommended and most powerful automation solution, capable of
handling scenarios that were once split across multiple tools.
18
Exp.9
Date
Exercise on validation and workflow rules
17/09/2025
Aim:
the objective was to gain practical experience with two fundamental Salesforce
platform features: Validation Rules for data integrity and Workflow Rules for
process automation. The goal was to test these features together to understand
their interaction and the standard order of execution.
Procedure:
▪
▪
▪
▪
▪
▪
▪
▪
▪
▪
▪
Navigated to the Object Manager in a Trailhead environment to
configure object-specific logic.
Selected the Lead object to create a Validation Rule ensuring data quality
for web-sourced leads.
Built the validation logic using the formula AND(ISPICKVAL(Lead
Source, "Web"), ISBLANK(Email)) and set the corresponding
error message.
Confirmed the rule's effectiveness by attempting to save test Leads from
the "Web" source without an email.
Implemented a second Validation Rule on the Opportunity object to
prevent illogical date entries (e.g., Close Date before Created Date).
Accessed the Workflow Rules menu to design an automation that fires
when an Opportunity is "Closed Won."
Set the workflow's evaluation criteria to trigger whenever a record is
created or edited to meet the "Closed Won" status.
Added two workflow actions: an Email Alert to notify management and a
Field Update to set the Opportunity Probability to 100%.
Activated the workflow and performed a test by closing a sample
Opportunity, verifying both the email and field change.
Simulated a complete business process, demonstrating how data integrity
(validation) is enforced before automation (workflow) is triggered.
Analysed and confirmed Salesforce's internal order of execution, noting
that Validation Rules are always checked before Workflow Rules.
19
Conclusion:
his process demonstrated a clear understanding of how to use Validation Rules to
enforce data quality standards before any subsequent automation occurs. The test
of the "Closed Won" workflow confirmed the ability to automatically trigger
multiple actions (Email Alert, Field Update), proving how validation and
workflows combine to create a robust, accurate, and efficient business process
within Salesforce.
20
Exp.10 Exercise on customization with lightning
Date
30/09/2025
Aim:
To explore and implement customization features in Salesforce Lightning
Experience, including Lightning App Builder, Lightning Pages, and Lightning
Components, in order to create personalized, user-friendly interfaces and improve
workflow efficiency.
Procedure:
▪ Logged into a Trailhead org and confirmed the user interface was set to
Lightning Experience.
▪ Navigated to the Lightning App Builder tool via the Setup menu to access
customization options.
▪ Initiated the creation of a new, custom Lightning App Page named "Sales
Performance Console."
▪ Populated the new page with standard components, including Reports,
Dashboards, and Recent Items.
▪ Integrated custom Lightning Components to display specialized, dynamic data
like active opportunities.
▪ Utilized the drag-and-drop interface to configure the page's layout, prioritizing
key components.
▪ Applied component visibility filters to dynamically show or hide elements
based on user or record criteria.
▪ Modified an existing Record Page (Opportunity) by reorganizing the layout,
adding new tabs, and embedding related lists.
▪ Leveraged Dynamic Forms to create conditional field visibility (e.g., showing
a discount field only when needed).
▪ Edited the App Launcher to include the newly created "Sales Performance
Console" for easy navigation.
21
▪ Applied custom branding to the org using Themes, adjusting logos, colors, and
backgrounds.
▪ Conducted thorough testing by logging in as different user personas to verify
all visibility rules and layout changes.
▪ Published and activated the new Lightning App Page, making it live and
accessible to users in the organization.
Conclusion:
A fully customized "Sales Performance Console" App Page and a modernized
Opportunity Record Page were successfully built, tested, and activated. This
process demonstrated a strong ability to use the Lightning App Builder to create
dynamic, responsive, and role-specific user interfaces. By applying conditional
visibility, Dynamic Forms, and custom branding, the user experience was
significantly enhanced, proving that the Lightning platform can be tailored to
improve workflow efficiency and drive user engagement without code.
22