Asset Search Functionality:

 Build an Aura Component

 Deploy / Demonstrate the Solution
 Develop Test Classes
 Use your best judgement to assume where the requirement is not explicitly mentioned

Problem Description:

ABC company is creating an asset library where anyone can submit their reusable
code/components/products and others can search and access that easily.
Below are the requirements for asset Library:
1. There will be one custom object Called “Asset” which will have following fields -
o Asset Name(Standard)
o Description
o Status - Picklist (Draft , Submitted, Under Review, Approved , Rejected)
o Documentation Link - text
o Video Link - text
o Source Code Link - text
o Submitted Date - date
o Executive Sponsor
o Functional Sponsor
o Technical Owner
o Comments
o 2 record types
1. Accelerator (reusable/generic code)
2. Product (full product/application)
2. OWD on asset will be private . Create a sharing rule to share them with a public group -
which will have all users; when status = “Approved”. Admin will have “View all”
permission so that he can see all assets.
3. Everyone will have access to “Asset” object and create an asset but it won't be displayed
on “Asset Search” page until status is ‘Approved’
4. Asset Search Page (Lightning Component) - “Main custom solution for this challenge”
o Should display a list of assets similar to “ Recent <***> “ list view.
o Also have options for
1. All Assets - all visible to user based on sharing rules. Ex: users will see all
Approved & Owned assets, whereas admins will see all the assets
irrespective of the status. - strictly controller by sharing and visibility
standard feature.
2. My Assets - all assets owned/submitted by the user.
o Page should have “list” view.
o Search Filters -
1. Search by Asset Name
2. Search by Status (Only to admin)
o Each Asset should display following fields -
1. Asset Name
2. Description
3. Submitted By
4. Document link
5. Video link
6. Source Code link
7. Status (Only to admins)
8. 2 buttons for admins inside modal - Approve and Reject.
9. If admin clicks on Approve, modal should open and display following
checklist. Until admin select all the checkboxes, approve button in modal
should not be enabled.
1. Submitted Documentation
2. Submitted Video
3. Submitted Source Code
10. User should be able to provide his comments  either he approve or reject
and status should change accordingly.