Scribd
Upload
215 views

DMART-Case Study

This case study outlines requirements for developing a customized "DMart" application on the Salesforce platform to automate the complete buying and selling process for DMart retail stores. The key objectives are to reduce manual efforts and time using three custom objects - Merchandise, Sell Item, and Invoice. The application would have four types of users and requirements include configuring picklists, relationships between objects, approval processes, reports, dashboards, and screens using components like LWC, flows, and APIs.

Uploaded by

kowsalyasr1503
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
215 views

DMART-Case Study

This case study outlines requirements for developing a customized "DMart" application on the Salesforce platform to automate the complete buying and selling process for DMart retail stores. The key objectives are to reduce manual efforts and time using three custom objects - Merchandise, Sell Item, and Invoice. The application would have four types of users and requirements include configuring picklists, relationships between objects, approval processes, reports, dashboards, and screens using components like LWC, flows, and APIs.

Uploaded by

kowsalyasr1503
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

_______________DMart Case Study_______________

Develop a customized “DMart” (retail) application on the Salesforce platform.

This application is supposed to provide solution to automate complete buying


and selling process of DMart & following processes to reduce manual efforts
and time.

Type of Users:

1. Merchandise User
2. Sales User
3. Support Users (2 Teams – one for India & the other for US)
4. CEO

This application is going to use mainly 3 custom objects for end to end
automation of DMart application. Below are the 3 Objects and its purpose.

Objects:

1) Merchandise: the purpose of this object is to track purchase of


products/items for DMart.
2) Sell Item: the purpose of this object is to sell the products/items to
customers.
3) Invoice: the purpose of this object is to raise the Invoice whenever we are
selling the products/items to customers.

Custom Objects:

1. Merchandise:
a. Merchandise Name - Text
b. Merchandise Desc - Textarea
c. Merchandise Stock – Number (*to indicate quantity)
d. Merchandise Price – Currency
e. Merchandise Country – Picklist(IND/USA)
f. Merchandise States – Picklist(UP/MP/NY/NJ)
2. Sell Item:
a. SellItem Name - Text
b. SellItem Desc - Textarea
c. SellItem Stock – Number (*to indicate quantity)
d. SellItem Price – Currency
e. Total SellItem Price: formula field (SellItem.Stock *
SellItem.Price)
3. Invoice:
a. Invoice Number – Auto Number
b. Invoice Desc - Textarea
c. Invoice Status - Picklist(Open/Closed/Finalized/Bargain)
d. Invoice Close Date – Date
e. Invoice Total Price – Roll-up Summery (Sum of “Total SellItem
Price” from SellItem Object)

Note: Here we have to launch Merchandise and Invoice Object as a TAB


whereas Sell Item Object should not as it’s a dependent Object of Merchandise
as well as Invoice too as it will act as a junction object you will find it into
related list to Merchandise and Invoice.

Relationships among Objects as below:

ERD:
Use Cases:

1) At the time of buying the product from Merchandise object,


Merchandise States should be dependent to Merchandise Country when
Merchandise User is selecting Merchandise Country as IND then UP/MP
states should be populated else if Country is USA then States should be
NY/NJ.
2) Selling Stock should not be greater than merchandise Stock.
3) Please make sure your selling stock should also be reduced from
Merchandise Stock whenever Sales user selling the items to customers
from SellItem Object. [do using Apex concepts – test class to have over
85% coverage]
4) If the selling price should be greater than 50000 then there should be an
email notification to CEO.
5) During the closing of the invoice with Invoice Status as “Closed”, please
make sure invoice close date should not be blank.
6) Please make sure Invoice Object will show Invoice Total Price which is
aggregate of Total SellItem price from SellItem Object.
7) Whenever we are selling the stock more than 10000, it should go to the
Manager for approval.
8) Only Merchandise User can create/edit the record into Merchandise
Object.
9) Only Sales User can create/update the records into SellItem Object
10) Only Support user can delete the record from the
Merchandise/SellItem Object.
11) Visibility of Case records in the 2 Support Teams should be based
on hierarchy. One Support user should only see his\her own cases. There
is 1 support user who is also a manager for both Support teams. This
manager should be able to see cases from both teams.
12) Only Support User can reopen the Invoice.
13) Not to be implemented, BUT: understand and prepare a
presentation on how the objectives stated in this case study for
Merchandise \ Invoices \ Sell Item can be achieved using Accounts \
Contacts & standard object in place of the proposed custom objects.

14) Sales reports to show:


a. Compare Revenue with Current year vs Pervious year
b. Top 10 Brand products by sales
c. Invoice Report

15) Dashboard to show visual representation of above reports. It


should display the data I the reports specific to the logged in user.

16) Create Home Page for the Dmart App. This should have the
dashboard you created above and another component using which a
user can first select any merchandise from a list of merchandises and
then in the next screen enter a discount percentage. Once submitted,
the price of the merchandise should be reduced by the discount
percentage specified. Also the Description field of all SellItems for this
Merchandise should now also have this text appended “This item was
sold with an old price!” (use screen based flow for this component).

17) Have a button on the Invoice record page that when clicked will
create & open a PDF of the invoice. Implement with LWC and use Parent
– Child relationship between 2 components.

18) Create a single page application using LWC for Merchandise using
which a user can Add, Search, Delete, Show merchandise records.
Implement Modals, Apex, LDS, Pagination & Data Table.

19) Integration - To integrate with legacy systems and any external


systems with REST API [NOT TO BE DONE BY YP TRAINEES]

You might also like