Support #13973

[SCP ID :##7010##] : Unable to find customer in UPASS Portal

Added by Zahir Abd Latif 5 months ago. Updated 5 months ago.

Status:InvestigationStart date:April 19, 2024
Priority:NormalDue date:
Assignee:Zhen Loong Koh% Done:

0%

Category:-Spent time:-
Target version:-

Description

Hi,
Kindly attend below request:-

Above subject refer, noticed that there were something wrong during calling api alluser where by it doesn't populate correct result when filtering result 'mal'.

This user existed in DB level.

select * from xynapse_upass.tb_am_user where u_user_alias ='mal';

Attached refer.

CAS_InspectElement_mal.txt Magnifier (100 KB) Zahir Abd Latif, April 19, 2024 16:38

CAS_username_mal.csv Magnifier (742 Bytes) Zahir Abd Latif, April 19, 2024 16:38

History

#1 Updated by Bin Madzlan Muhammad Muhafiz 5 months ago

  • Status changed from New - Begin Life Cycle to Investigation
  • Assignee changed from Bin Madzlan Muhammad Muhafiz to Zhen Loong Koh
  • Priority changed from High to Normal

The root cause is frontend is searching the user based on a string pattern instead of exact string and upasscore limits the result by 100 records, since there are >100 users with 'mal' in their aliases, the query will not provide the full result due to upasscore limiting it by 100 records therefore the user is not found in the list.

We have 2 solutions:
Long term: modify sql query to remove the LIMIT clause and add pagination using spring jpa (Impacted Area: frontend and backend)

Short term: modify frontend to allow the option to search the user based on exact alias (Impacted Area: frontend)

Also available in: Atom PDF