Activity
From June 20, 2010 to July 19, 2010
July 16, 2010
-
11:32 Revision 356:bee0400ba6e6: new blacklist checking method amended.
- set new parameter in email sending method
change OFAC DB setting
sample XML for IBG and ESB to view
July 15, 2010
-
-
- Since the GFS IBG Transactions - TT against Cash, TT against Cheque, TT against GL will be treated as TT against CASA...
July 13, 2010
-
14:50 Task #247: Migration Plan for IBGCore for GFS
- Prepare migration plan for IBG GFS which is targeted on 22 July 2010.
-
- Technical documentation update to include GFS configuration and setting.
July 09, 2010
-
18:16 Revision 355:91ef8d2b48e9: addEntry(): modify IBGEntry.setDesc from "INVALID BENEFICIARY ACCOUNT ...
-
14:49 Bug #253: MEPS-GFS-UAT-10-072
- Wrong put the version. Update the correct version.
-
- Rename ‘Temporary Account’ to ‘Transition Account’ done. change at one file at IBApplicationResources.propert...
July 08, 2010
-
- connection error between IBG and Phoenix due to ESB Web Service connectivity failure.
-
- connection error between IBG and Phoenix due to ESB Web Service connectivity failure.
-
-
- 14:58 Revision 354:398f49cb07ee: IBG GFS UAT fixes:
- GFSIBS-10-P2R1-073 - MEPS IBG maximum allowed transaction is RM100,000.
However, system unable to perform transaction... - 12:23 Revision 353:37ef594c11a5: new libraries
July 07, 2010
-
- For normal transfer, GFS has to send charges amount to IBG to debit from sender account. Special cases like TT agains...
-
- Unable to perform transaction with error message as per attached.
-
- Symbol ‘ NOT displayed correctly in Corus
-
- MEPS IBG maximum allowed transaction is RM100,000.
However, system unable to perform transaction amounted RM100,000... -
- Incorrect error msg – Should be Invalid Beneficiary ID Format
-
- Rename ‘Temporary Account’ to ‘Transition Account’
-
- Charges debited twice in Phx
-
12:13 Task #248 (Closed - End of life cycle): Update IBGCore Documentation
- Update all the IBGCore documentation to reflect this changes.
-
- Prepare migration plan and scripts for deployment
-
- Monitor UAT progress and close this issue when obtained UAT Signoff.
July 01, 2010
-
- Not an issue. Unable to check for blacklist due to connection error. Had informed IT to check on the connection from ...
-
- Issue Not-On-Us. GFS should allow only CASA Account types to perform IBG.
-
- Change the error message for Transactions that Exceeds the Transfer Limit to the requested message (Maximum MEPS IBG ...
-
- IBG do filter the IBG Transaction by current date to perform the transaction. Reject the transaction if the effective...
-
- GFS alwarys sends a null value for Beneficiary ID. Ignore the Beneficiary ID and validate the rest of the Identificat...
-
- GFS sends the value date as the effective date instead of business date
-
- GFS sends the correct charges & principle description to IBG
-
- GFS send the charges value
- 19:42 Revision 352:22791bae6b20: 01/07/2010 - IBG GFS Fixes
- GFSIBS-10-P2R1-055 - validate all beneficiary ID
GFSIBS-10-P2R1-058 - change error message for Exceed Transfer Limit
June 29, 2010
-
- Blacklisted name NOT rejected by IBG Core.
-
- Invalid pop-up error message.
Message should be ‘Account type must be Current / Savings Account (MYR)’.
Inves... -
- Incorrect pop-up message.
Pop-up message should be ‘Maximum MEPS IBG transfer limit is RM100,000’ -
- Future payment date is allowed.
-
- IBG Core accepts invalid Beneficiary’s ID
-
- GFS & IBG system date 1.6.10 but tranx failed due to ‘Invalid Date’
When IBG change date change to 29.6.10, tran... -
- Description should be “OTC Fund Transfer : MEPS IBG†but shown as “Testâ€
*Investigation* : GFS to set de... -
- Charges not debited
Investigation: It suspected that GFS send charge amount = 0. So, no Charge amount Transfer occ... - 19:26 Revision 351:9c94b4c47039: F
-
-
-
-
-
June 28, 2010
June 25, 2010
June 24, 2010
-
- Delay due to additional change request
-
- Delay due to the additional change request and phoenix integration.
Also available in: Atom