Improvements #
- Add Branch Column to rate card in Client Side – The Rate Card in the Client Side has been updated to include a Branch column, fulfilling the requested enhancement. Now, clients can easily access rate information specific to different branches, providing them with more detailed.
- Need to Add Last Modified User into All Client Edit Interface – When editing Merchant details, a new field labeled “Last Modified User” will be displayed. This field will show the username or identifier of the user who made the last modification to the Merchant’s information. This feature will enhance accountability and tracking within the system.
- Field Responsiveness checking Merchant registration Form and Profile update in Client Portal – The Merchant registration form and Profile update in the Client Portal are experiencing field responsiveness issues. When entering or editing data in the fields, the form structure is being shuffled, causing inconvenience to users. Investigate and resolve the field responsiveness issues in the Merchant registration form and Profile update in the Client Portal. Ensure that the form structure remains stable and consistent regardless of user actions such as data entry or editing. This will enhance user experience and streamline the registration and profile update processes.
Bugs #
- Need to separate Update Account from Profile Update – The issue has been identified regarding updating account details within the client-side profile update. This arose due to certain account details being collected initially as non-mandatory fields, which have now become mandatory. Consequently, when attempting to update the account, these data fields are being validated, resulting in error messages. To address this issue, it is necessary to handle the validation of account details update and profile update as separate sections. By doing so, we can prevent validation conflicts and error messages, ensuring a smoother update process for both account and profile information.
- Return Received Update Request – There is an issue with accepting returned items through the client portal. Specifically, archive orders cannot be approved as received by the client. This prevents users from properly managing returned items. Implement new validations to allow for the approval of both normal and archive orders without requiring changes to the interface. These validations will be handled at the code level to ensure seamless processing of returned items through the client portal.