Blackforce.

ca
Salesforce Administrator
Individual Project 1B

Development of a Simple
Bug Tracking Application.
(20th of Feb 2023)
SingleLogin Inc. creates different micro technology solutions for its customers. Some of
these solutions include a Booking Application, Schedule Management Application,
Online Assessment Application, Affiliate Program Application and many more.

As part of the digital transformation initiative to improve technology solution delivery

at SingleLogin Inc. as well as to complete your Salesforce setup for SingleLogin Inc. The
manager has challenged you to implement a simple bug tracking application that will
enable easy tracking of the number of bugs and customers that created the bugs. The
application will also be able to send emails when the bug is being worked on or the
issue with a Bug requires urgent attention.

Using the same Salesforce Org as project 1A, develop a simple solution that will help
SingleLogin Inc. track bugs (defects with its application).

Get a better understanding and approach by reading the background information.

Follow the instructions and answer the questions that follow.

Estimated total time = 8 hours. Due date is Tuesday, 28th of Feb, 2023.

○ In Salesforce, you can create relationships to link objects with each other,
so that when your users view records, they can also see related data. For
example, you can link a custom object called Bugs to cases to track
product defects that are associated with customer cases.

○ Before you begin creating relationships, determine the type of

relationship that suits your needs. You can define different types of
relationships by creating custom relationship fields on an object.

○ Different types of relationships between objects in Salesforce determine

how they handle data deletion, sharing, and required fields in page
layouts.

○ Master-detail - Closely links objects together such that the master record
controls certain behaviors of the detail and subdetail record. You can use
master-detail relationships to model many-to-many relationships between
any two objects. A many-to-many relationship allows each record of one
object to be linked to multiple records from another object and vice
versa.
 ○ Lookup - Links two objects together. Lookup relationships are similar to
master-detail relationships, except they don’t support sharing or roll-up
summary fields.

There are other types of relationships such as External lookup, Indirect

lookup and Hierarchical - visit here for more information.

https://help.salesforce.com/s/articleView?id=sf.overview_of_custom_obj
ect_relationships.htm&type=5

Tasks
1. You are required to Create a custom object called Bug - this tracks all
bugs created by the support user. Put all necessary fields applicable to a
bug tracking record i.e. bug name, category, open date, close date,
severity ( picklist field number 1 - 7 as drop down), bug status, and any
other fields you find useful.
2. You are also required to create another custom object called CaseBug
which has a master-detail field to both Case and Bug (this is because a
case can be related to many bugs, and a bug could be related to many
cases - This type of relationship is called many-to-many). You should now
be able to navigate between Bugs and Cases. I.e. see a list of Cases with a
Bug and see a list of Bugs with Cases e.t.c from the Bug or Case objects
respectively.
3. You are required to create another custom object called BugDetails - the
bug details object stores a text long area comments about a bug. It is an
historical work log progress made on fixing the bug. We can have
multiple bug details associated with one bug. No bug details should be
associated with multiple bugs.
4. Using Salesforce Flow, create a custom button on Case's record page
called "Convert To Bug" which automatically creates a Bug record. You
should copy some of the data from the Case record to the new Bug record,
automatically fill the other fields and more importantly make a CaseBug
to relate that Case to the Bug you just made.
5. Draw the final schema Diagram for Case, Bug, CaseBug and BugDetails.
The schema diagram should illustrate the relationships between these
objects.

6. Carry out the following test and answer the questions:

a. Create a new Case and a Bug record.
b. Create at least 5 new BugDetails records.
c. What type of relationship is between the Bug and BugDetails?
d. What happens to all the BugDetails when you Delete the Bug?

7. Roll Up Summary - Roll-Up Summary Fields in Salesforce summarize data

from a set of related detail records and automatically display the output
on the master record. You can perform different types of calculations with
a roll-up summary field. You can count the number of detail records
related to a master record. Or, you can calculate the sum, minimum
value, or maximum value of a field in the detail records.

a. Using Rollup Summary, you are required to display the total

number of Bug details per Bug on the Bug Record.

8. Formula and Validation Rule - Formula fields are custom fields that
automatically provide results based on records and related records.
They are a valuable and powerful tool provided by Salesforce to the
Admins as they are updated automatically in real-time whenever a record
is accessed. On the other hand, Validation rules in salesforce contains a
formula or expressions that evaluates the data in one or more fields in
a record to meet the standards and returns a value “True” or “False”.
Validation rules display an error message to the user when the Condition is
“False”. Validation Rules are used to prevent bad data from entering
the system.
a. Using the formula, create a field that displays a red, orange, yellow
or green image. The field should check for bug severity. If it is
between 1 - 2 inclusive (display green), if it is between 3 - 4
inclusive (display orange), if it is between 5 - 6 inclusive (Display
Yellow) and if it is 7 (Display red).

b. Using validation rules, ensure the bug open date cannot be

greater than the close date. Also ensure the open date or close
date cannot be in the future.
9. Record Type in Salesforce allows you to have different business processes,
picklist values, and page layouts to different users based on profile. You
might create record types to differentiate your regular sales deals from
your professional services engagements, offering different picklist values
for each.
Page layouts control the layout and organization of buttons, fields, s-
controls, Visualforce, custom links, and related lists on object record
pages. They also help determine which fields are visible, read only, and
required. Use page layouts to customize the content of record pages for
your users.

a. You are required to create three record types (Bugs, Support, Enquiry)
on the case object. Not all cases can be converted to a bug. Using record
type, page layout, support processes, dynamic forms, and conditional
visibility or any method of your choosing, ensure only cases with record
type Bugs display the "Convert To Bug" button on the case record page.

b. If the record type is Bug, then include a new status field called “In
Development” as part of the Case status field drop down option. Also,
Bug Severity should only be available if the case record type is Bug and
should be hidden for other case record types.

c. Ensure the Bug record type page layout on the Case is different
from the Support & Enquiry page layout. I.e. remove some fields
from the page out.

10.In salesforce you can use Email Templates to increase productivity and
ensure consistent messaging. Email templates with merge fields let you
quickly send emails that include field data from Salesforce records.

a. You are required to create a dedicated email template that

acknowledges the receipt of the Bug reported by the customer.
Use fields from the Case / Bug object. The content of the email
should be presented professionally. Ensure emails are highly
personalized. I.e. Dear Customer Name. No hardcoded values i.e.
date of bug creation e.t.c should be pulled from the relevant
fields.
11.Auto-Response rules in Salesforce make it possible to send an automatic
email response to a lead or case based on the record’s attributes. A
Salesforce administrator can send an automatic reply to the customers to
assure them that someone from your company has acknowledged their
query. You can create as many auto-response rules as you want based on
any attribute of the incoming lead or case, but only one rule for the leads
and one for cases can be active at a time.

a. You are required to create an Auto Response rule for new cases
whose Record Type = Bugs. The Auto Response rule should use the
Email Template created above.

b. Can you create another email alert when a Bug is Closed? How
would you achieve this?

12.Assignment rules are a powerful Salesforce feature that can help

automate your organization’s lead generation and support processes.
Assignment rules dictate to whom a lead or case is assigned based on
criteria specified within Salesforce. Typically, your organization will have
one rule for each overall purpose — like one lead assignment rule for
importing leads and a different lead assignment rule for web-generated
leads. Each rule can consist of multiple entries to specify precisely how
leads or cases are assigned. Use case assignment rules to determine how
cases are assigned to users or put into queues.

a. You are required to create a Bug Support Team queue and also
automatically assign all Cases with record type = Bugs to this
queue.

b. Ensure all the members of the Queue should get an email upon
assignment.

13.An escalation rule automatically reroutes a case and can notify a user if
the case remains open after a certain period of time has passed. With an
escalation rule, you can: Choose to escalate a case to a queue or to
another user. Configure the rule to automatically notify a user. Configure
rule entries to define the order, criteria, and escalation actions.
 a. You are required to escalate a case to the Operation Support
Manager if a case with record type = Bug and severity = 7 has not
been resolved after 72 hours.

14.Salesforce Chatter provides enterprise collaboration tools that can help

your employees work more efficiently, be more productive and innovate
as a team. With Chatter as your enterprise collaboration solution,
employees can share files, form groups, share questions and answers, do
polls and more.
a. Using the Salesforce process builder or any automation tool of your
choosing, you are required to send an automatic broadcast to a
public chatter group consisting of the bug support team members
everytime a new case is created and case record type = Bug.

Ensure Bug is part of the objects on the navigation tab of your dedicated application.
Feel free to include extra reports and dashboards that help Track Cases and Bugs in the
system.

Note: You are required to take a screenshot of every itemized section above and submit
a single PDF file via the submission portal. I.e. Take a screenshot of Questions 1, 2,
and
3 ..up until the last question PLUS a screenshot of your 25,000 trailhead points -
compulsory. Compile it and create a single PDF file. Do not skip the questions. Do
the question one after the other.

Maintain your original Salesforce org used for implementing this project. Do not
delete this org until the end of your training program at BlackForce. This org
together with the Screenshots will be used as part of the screening exercise for
Internships, Side Gigs, Interviews and Reference from BlackForce.

The deadline to submit the project is Tuesday 28th of February, 2023 - at 8 pm

EST. No exceptions. All members including Standard, Professional and CPD
(Currently or actively looking for a job only) MUST submit this project to maintain
their active membership.

Good Luck!