Bug #12381
Task #11680: [Phase_2] : RFP 1.2.2.3- DuitNow - Instant Transfer
DuitNow - Arrangement of Mobile details receipt should follow Web receipt
Status: | System Integration Test | Start date: | October 06, 2021 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | Nurul Syahirah Md Nawi | % Done: | 90% | ||
Category: | - | Spent time: | - | ||
Target version: | - |
Description
Path: BSNeBIZ Mobile (IOS & Android) > Make Duitnow Payment > Verify > Approve
Current: Details receipt for User with workflow (Initiator, Verifier, Approver) & Single User for Mobile (IOS & Android) are not in correct order.
Expected: Arrangement of mobile details receipt should follow same as web receipt for each user.
Please refer attachment.
History
#1 Updated by Nurul Syahirah Md Nawi almost 3 years ago
- Subject changed from DuitNow - Display Error Message for Beneficiary ID to DuitNow - Arrangement of Mobile details receipt should follow Web receipt
#2 Updated by Najmi Pasarudin over 2 years ago
- Assignee changed from Najmi Pasarudin to Nurul Hasnieza Bt Mohd Zamri
Hi Hasnieza, please help with this task.
#3 Updated by Nurul Hasnieza Bt Mohd Zamri over 2 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
- Assignee changed from Nurul Hasnieza Bt Mohd Zamri to Rahmat Aina Nadia
- % Done changed from 0 to 50
Issue is triggered when getting unordered set of value request from mobile.
Suspected occur during mfp which is converting LinkedHashMap to HashMap. So, both mobile and restful side have to update
new parameter datatype which is LinkedHashMap to make sure the receipt details are in correct order.
#4 Updated by Rahmat Aina Nadia over 2 years ago
- Assignee changed from Rahmat Aina Nadia to Lai Wen Hong
As per discussion last Thursday (31/3/2022), mobile has discarded all new changes on request parameters and remains existing when executing receipt service. LinkedHashmap and two new parameters which are transactionDate and referenceNumber are not needed from mobile side.
#5 Updated by Lai Wen Hong over 2 years ago
- % Done changed from 50 to 90
Issue:
Arrangement of Mobile details receipt is not same as Web receipt
Finding:
The receipt map used is from mobile and it is not in proper order.
(More detailed cause had been mentioned by Hasnieza in previous update)
Solution:
Instead of using receipt map passed from mobile, now using receipt map retrieved from database which is same arrangement as Web.
The code change will be completed at backend restful.
- Path: BSNeBIZ Mobile (IOS & Android) > Make Duitnow Payment > Verify > Approve
- Expected result: Arrangement of mobile details receipt is same as web receipt for each user.
#6 Updated by Lai Wen Hong over 2 years ago
- Status changed from Development / Work In Progress to Internal Testing
- Assignee changed from Lai Wen Hong to Nurul Syahirah Md Nawi
#7 Updated by Nurul Syahirah Md Nawi over 2 years ago
- File Updated_SU.PNG added
- File Updated_Initiator.PNG added
- File Updated_verifier.PNG added
- File Updated_approver.PNG added
Tested & passed
#8 Updated by Nurul Syahirah Md Nawi over 2 years ago
- Status changed from Internal Testing to System Integration Test