Support #13491

[SCP ID :##6660##] : Fix DuitNow reversal for new parameter

Added by Zahir Abd Latif over 1 year ago. Updated about 1 year ago.

Status:Work Completed-End life cycleStart date:May 05, 2023
Priority:NormalDue date:
Assignee:Zahir Abd Latif% Done:

100%

Category:TechnicalSpent time:-
Target version:-

Description

Hi,
Kindly attend below request:-

Issue: eBiz unable to do reversal for new DuitNow parameter ns2:RP. eBiz currently only able to do reversal for parameter ns1:RP

History

#1 Updated by Binti Marobi Athirah Umairah over 1 year ago

  • Category set to Technical
  • Assignee changed from Nurul Athira Abdul Rahim to Najmi Pasarudin

#2 Updated by Najmi Pasarudin over 1 year ago

  • Status changed from New - Begin Life Cycle to Development / Work In Progress

#3 Updated by Najmi Pasarudin over 1 year ago

  • Status changed from Development / Work In Progress to Pending SIT Deployment
  • Assignee changed from Najmi Pasarudin to Nurul Hasnieza Bt Mohd Zamri
  • % Done changed from 0 to 90

Hi Hasnieza,
Please pull bsn-esb and deploy SIT for bsn-cdb, bsn-cronjob, bsn-restful and bsn-si-cron.

Issue:
  1. BSNeBiz unable to do reversal for new DuitNow parameter ns2:RP. eBiz currently only able to do reversal for parameter ns1:RP
  2. DuitNow response timeout but BSNeBiz did reversal
Finding:
  1. Datapower or RPP updated their webservice parameter name. Thus current code no longer working.
  2. BSNeBiz record timeout error as status RJCT which will do reversal
Solution:
  1. Fix DuitNow response only. To read error parameter ns1:RP or ns2:RP or any name ends with :RP as RP.
  2. Fix DuitNow failed response bean from RJCT to 999 to indicates server error or timeout.
Test scenario 1, positive testing:
  1. Access BSNeBiz
  2. Create DuitNow transfer using initiator or single user
  3. Approve the transfer
  4. Expected result, DuitNow success
Test scenario 2, ns2:RP testing:
  1. Change server time to get DuitNow timestamp error
  2. Access BSNeBiz
  3. Create DuitNow transfer using initiator or single user
  4. Approve the transfer
  5. Expected result, DuitNow failed
  6. Check the log. DuitNow must return ns2:RP as error code. If not, the testing is invalid.
Test scenario 3, timeout or connection error:
  1. Access BSNeBiz
  2. Create DuitNow transfer using initiator only
  3. Before approve the transfer, change the DuitNow webservice IP to get connection error
  4. Approve the transfer
  5. Expected result, DuitNow failed
  6. Check the log. DuitNow must show connection error and has no response.

#4 Updated by Nurul Hasnieza Bt Mohd Zamri over 1 year ago

  • Status changed from Pending SIT Deployment to Finished Development

#5 Updated by Nurul Hasnieza Bt Mohd Zamri over 1 year ago

  • Status changed from Finished Development to Internal Testing
  • Assignee changed from Nurul Hasnieza Bt Mohd Zamri to Binti Marobi Athirah Umairah

SIT deploy on 09/05/2023.

Kindly retest.

#6 Updated by Binti Marobi Athirah Umairah about 1 year ago

  • Status changed from Internal Testing to Work Completed-End life cycle
  • Assignee changed from Binti Marobi Athirah Umairah to Zahir Abd Latif
  • % Done changed from 90 to 100

Deploy to Prod on 23/06/23. Migration ID00069

Also available in: Atom PDF