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 information.
• 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 for Merchant Registration Form and Profile Update in Client Portal
  • The Merchant registration form and Profile update in the Client Portal were experiencing field responsiveness issues. When entering or editing data, the form structure was being shuffled, causing inconvenience to users. This issue has been investigated and resolved. Now, the form structure remains stable and consistent, improving the user experience for registration and profile updates.

BUGS FIX #

• Need to Separate Update Account from Profile Update
  • The issue was identified regarding updating account details within the client-side profile update. This arose due to certain account details being initially collected as non-mandatory fields, which have now become mandatory. Consequently, when attempting to update the account, these data fields were being validated, resulting in error messages. The update now handles account details separately from profile updates to prevent validation conflicts and ensure a smoother user experience.
• Return Received Update Request
  • There was an issue with accepting returned items through the client portal. Specifically, archived orders could not be approved as received by the client. This prevented users from properly managing returned items. The update implements new validations that allow for the approval of both normal and archived orders without requiring changes to the interface. These validations are now handled at the code level to ensure seamless processing of returned items through the client portal.