Bug #790
SL 031 - UN list not filtered by IBG Core
| Status: | Work Completed-End life cycle | Start date: | February 21, 2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | February 23, 2011 | |
| Assignee: |  Latipah Abdul Rashid | % Done: | 100% | |
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
IBG Core did not filter UN blacklisted name (tranx coming from OTC).
History
#1
Updated by Latipah Abdul Rashid over 13 years ago
- Status changed from New - Begin Life Cycle to Development / Work In Progress
- % Done changed from 0 to 80
IBG Core will check the Beneficiary Name against the blacklisted name list.
Based on the screen shot, the Beneficiary Name provided is "AWEYS HASSAN DAH", instead of the name maintained in the blacklist name list, "AWEYS HASSAN DAHIR".
IBG Core will only filter the exact same name found in the blacklisted name list.
#2
Updated by Latipah Abdul Rashid over 13 years ago
- Assignee changed from Vincent Devethas to Latipah Abdul Rashid
- % Done changed from 80 to 90
Found out from Vincent, for the blacklist validation, IBGCore will validate the full beneficiary name, before truncate the name to 20 chars to fit in Nacha file.
Get the IBGCore, IBGWS and Scheduler projects from Production server, found that ResourceUtilScheduler.class is missing in both project IBGCore and IBGWS, causing the failure for DB connection to BIB schema.
Copied to DEV and tested using IB. At IB, blacklist validation had been disabled to makesure trxn go to blacklist validation at IBGCore.
Although class is missing, it didn't throw ClassNotFoundException, instead it just didn't block the blacklisted name - trxn was accepted. When added the class, the blacklisted name was blocked - trxn was unsuccesful due to blacklisted beneficiary.
In STG, the class is missing in IBGWS_STG, but founded in IBGCore and IBGGFS.
Added the class to STG for testing.
#3
Updated by Latipah Abdul Rashid over 13 years ago
- Status changed from Development / Work In Progress to User Acceptance Test
#4
Updated by Latipah Abdul Rashid over 13 years ago
- Status changed from User Acceptance Test to Pending Prod Deployment
#5
Updated by Sarinah Darsy about 13 years ago
- Status changed from Pending Prod Deployment to Work Completed-End life cycle
- % Done changed from 90 to 100