LWC Assignment

Video (Unfortunately it's too bright. Some screenshots to see true colors)

Updates:

2021-07-09 - Fixed a bug when new Order Items could be saved as different rows in one Order

Yes, it's better to use Prodict2Id as product identifier instead of product name. If it was real project I would never use name as identifier. But here I left it as it is. If 2 products have same names a user can't distinguish between them, and according to "Each product can only appear once in the list" it should be ok for test assignment, I think.

Build an order record page consisting of 2 LWC components

Orderable product will be displayed in a 2-column list displaying Name and List Price (component 1)

a. Products are orderable when they have a Pricebook Entry in the Pricebook related to the current order (standard pricebook for this assignment) and when that Pricebook Entry is active
b. Each product can only appear once in the list

The UI needs to provide the ability for the user to add a product from the list (component 1) to the order

a. When the same product is not yet added to the order it will be added with a quantity of 1
b. When the product already exists the quantity of the existing order product be increased by 1

All Order Products in the current order will be displayed in a table displaying the Name, Unit Price, Quantity and Total Price (component 2)

a. When the user adds a new product or updates an existing product on the order (see point 2) the list needs to display the newly added

A test coverage of at least 80% for both APEX components is required.
The use of Aura components is prohibited.
Create a Salesforce Developer login for this assignment and build it as a SFDX project.

Once you build this, create a public repository on GitHub, check in all the components and share the repository path with us.

Try to use OOTB LWC components provided by Salesforce, see also the component library from Salesforce: https://developer.salesforce.com/docs/component-library/overview/components
Make sure you commit the Order Flexi page to git
Apply best practices, we will be reviewing both the functionality and implementation of your solution
To avoid any minus points when your code is not deployable, include short video of your solution that covers the Acceptance Criteria and commit it to git
Document your code to help us understand the technical choices you made when building the solution

The number of products can exceed 200; the solution needs to be able to handle this while providing a proper user experience.
To ensure an optimal user experience the page should not be reloaded and only the changed or new items should be refreshed/added
The end user needs to be able to confirm the order in an external system with the click of a button.

a. The request format expected by the external system should follow the following JSON structure: { "accountNumber": "", "orderNumber": "", "type": "order type", "status": "order status", "orderProducts": [{ "name": "product name", "code": "product code", "unitPrice": 10.00, "quantity": 1 }] }
b. Request is sent as POST
c. Order of the JSON fields in the above JSON structure is not relevant but the data type is.
d. Errors and time-outs of the external system need to be handled
- i. All 200 responses are considered OK
- ii. Any non-200 response is handled as ERROR
e. For this use case generate a new endpoint URL at https://requestcatcher.com/

After the order is confirmed successfully in the external system the status of the order and order items will be updated to “Activated” a. When activated the end user will not be able to add new order items or confirm the order for a second time.
A test coverage of at least 80% for both LWC components is required.