A library of user acceptance test scripts, test runs recorded and signed off in each company’s own database, and a tighter Customer Master.
Customer Master: Own Permissions and GSTIN Checks
Creating, changing and deleting a customer now need their own permissions rather than the lead view permission, and the screen hides what the user may not do. Existing customised roles keep their current access.
The GSTIN is checked for its format, state code and check character, and the Tax ID must match the PAN inside the GSTIN — or is filled from it. The address list shows the address type and country by name, and the customer, address and contact dialogs show errors against the field at fault.
UAT Test Script Library
A new UAT Test Scripts page under Help & Support holds step-by-step acceptance test scripts, common to every client in the same way as the help pages. Each script is organised into test cases and steps with the expected result, and can be printed or downloaded as a blank Excel execution workbook.
The first script is UAT-MD-001 Customer Master (19 cases, 66 steps).
UAT Test Runs and Sign-off
A new UAT Testing page records a test run in the company’s own database. A run keeps a copy of the script, its version and the build under test, so later changes to the script never alter what was tested. Testers mark each step Pass, Fail or Blocked; a Fail or Blocked step must state the actual result. A live progress board shows where the run stands, and the results export to Excel.
The run is signed off by the Tester, the Process Owner and the Implementation Lead — one person per role, each confirming their identity again (authenticator code, or password) at the moment of signing. Acceptance locks the results; a rejection withdraws the sign-offs and reopens the run. New roles UAT Tester and UAT Signatory grant access.