Month: March 2025

Monday, March 17 2025 – Last week, I focused on completing the final features required for this project, at least for now. However, before diving into feature development, I first addressed several UI bugs based on the latest findings. Once those were fixed, I quickly moved on to implementing the new functionality.

The first step was developing the display list. Similar to a previous feature I worked on, this one included two modes: Unprocessed Mode, which filters the list accordingly, and All Mode, which displays the full list along with its relevant features.

Once the table was set up, I proceeded to configure the filters for the All Mode. This whole feature was divided into three main sections, with the second section being relatively straightforward, it simply involved displaying a list of data within a table component. Since no user interaction or buttons were required here, it was a simple implementation.

The final section was the core functionality of the feature. Users needed to search for an item, and if the correct item code was entered, the corresponding data would be displayed, and the next set of actions would become available. If the code was incorrect, the backend would return an error message. Additionally, users were required to input some confirmation details before they could proceed with the Stow button. An Undo button was also included for this feature.

During testing, I initially struggled to execute the stow function. After troubleshooting, I discovered that the issue was caused by the store code not being set to the one the user was currently in. Once I corrected this, the feature worked as expected.

By the end of the week, only one unresolved issue remained which is items from a specific store were not processed correctly, while others worked fine. Investigating this will be my priority for next week.

Monday, March 10 2025 – Last week, I started working on another feature, built upon the existing system. This feature had a similar layout to the one I worked on previously, so I aimed to complete it as quickly as possible. My initial tasks included setting up the display table and implementing search filters on the main page.

Next, I focused on the detail page, working on the layout and command buttons. However, when implementing the create command and sending API requests, I encountered an unclear error that I suspected originated from the backend. To troubleshoot, I verified the validity of the command data before escalating the issue to Mr. Peter. Once discussed the bug in detail, and alongside this, I reported other bugs I had discovered and documented additional UI issues that needed fixing.

By the next day, the bug was resolved, allowing me to proceed with configuring the modes correctly. As the week comes to an end, there are minor adjustments needed for the detail page, particularly in edit mode, which I plan to complete next week.

Monday, March 3 2025 – Continuing from last week, I focused on the detail page, which includes both a read-only mode and a create mode, as there is no edit functionality for this feature. My priority was to complete the create mode first before working on the read-only mode.

The second component I worked on displayed the line items of an order selected from the first table, which lists all available orders. This component allows users to pick line items to be issued. The selected data is then passed to a third component, which consolidates multiple line items from different orders.

Since the feature involves transferring data between components and handling API requests, I had to manage multiple DTOs. Given that both view and create modes were involved, I created a new object to act as a bridge between the DTOs and command requests.

I first ensured that the create command worked successfully. Since there were only two commands for the detail page which is create and cancel, the mode-switching logic was relatively simple. After confirming that the create function worked correctly, I tested the cancel function as well.

By the end of the week, I had completed the feature. However, further testing is needed to identify and fix any remaining bugs.

Monday, February 25 2025 – Last week, I began working on a new feature. Initially, I assumed that the detail view page would closely follow a previous feature I had developed. However, I soon realized that the detail view page required a different approach. The goal of this feature was to align with the existing system’s design.

To simplify the process, I first created a button that displayed a list of orders, allowing users to select one. However, Mr. Peter pointed out that this feature needed to support line items from multiple orders, meaning my initial design was too restrictive. I quickly adjusted my approach and started designing the detail page accordingly.

Similar to my previous feature, I decided to break the page into components. The first component I worked on was the list display. I created a table to list orders and another table to show the line items of a selected order.

As this was a short work week for me, I couldn’t complete all the components. There’s still more to build, and I will continue making progress in the coming week.