Fix Readme
Abstract
This document contains the fix list information for Financial Transaction Manager for Digital Payments for Multiplatforms 3.2.10.
Content
Fix List for Financial Transaction Manager for Digital Payments 3.2.10
This document contains fix list information for:
Financial Transaction Manager for Digital Payments for Multiplatforms 3.2.10
The following tables provide a complete listing of the available FTM for Digital Payments fixes on all platforms. Multiplatforms fixes are available on Fix Central.
Note:
- Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
- To avoid a loss of functionality when you migrate from one release to another, check the Compatibility Matrix for the release being migrated to. The Compatibility Matrix is located in the V3.2.10 Release Information for Financial Transaction Manager for Digital Payments.
| V.R.M.F fix list | Links to Fix Central download (by Fix ID) |
Product | Build date | Pre-requisites |
| 3.2.10.1 interim fix 2 | 3.2.10.1-FTM-DP-MP-iFix0002 | Digital Payments | 20221109-1253 | 3.2.10.1 |
| 3.2.10.1 interim fix 1 | 3.2.10.1-FTM-DP-MP-iFix0001 | Digital Payments | 20220707-1901 | 3.2.10.1 |
| 3.2.10.1 | 3.2.10.1-FTM-DP-MP-fp0001 | Digital Payments | 20220614-1900 | None |
| 3.2.10.0 interim fix 6 | 3.2.10.0-FTM-DP-MP-iFix0006 | Digital Payments | 20230621-1900 | 3.2.10.0 |
| 3.2.10.0 interim fix 5 | 3.2.10.0-FTM-DP-MP-iFix0005 | Digital Payments | 20230313-1147 | 3.2.10.0 |
| 3.2.10.0 interim fix 4 | 3.2.10.0-FTM-DP-MP-iFix0004 | Digital Payments | 20221202-0808 | 3.2.10.0 |
| 3.2.10.0 interim fix 3 | 3.2.10.0-FTM-DP-MP-iFix0003 | Digital Payments | 20220921-1000 | 3.2.10.0 |
| 3.2.10.0 interim fix 2 | 3.2.10.0-FTM-DP-MP-iFix0002 | Digital Payments | 20220829-1558 | 3.2.10.0 |
| 3.2.10.0 interim fix 1 | 3.2.10.0-FTM-DP-MP-iFix0001 | Digital Payments | 20220531-0708 | 3.2.10.0 |
| 3.2.10.0 | Available from Passport Advantage | Digital Payments | 20220406-1900 | None |
Note: APAR links for security fixes aren’t active.
Refer to V3.2.10 Release Information for Financial Transaction Manager for Digital Payments for more information about issues and changes.
Note: The update instructions referred to by interim fixes are located in the installation location\component\doc folder, for example:
installation location\shared\v3210\pfs\Gateway\doc\updates.
| Back to top | 3.2.10.1 interim fix 2 |
Note: 3.2.10.1 interim fix 2 contains a security fix.
| Fix number | Type | Component | Description |
| DT141144 | Defect | Gateway Other | ACH NACHA file with multiple file blocks fails. |
| DT141573 | Defect | Real Time Payments Console | Need to identify a small business vs a consumer payment in CXCParticipantView.Get (read) service response. |
| DT143902 | Defect | Distribution Engine | Distribution Engine: Treat max payments = 1, same as single transaction in mapper. |
| DT149278 | Defect | Distribution Engine | Deadlocks are causing payments to fail. |
| DT160860 | Defect | Business Rules Console | Payments are failing at Gateway Server during Business Rules Server refresh. |
| DT169084 | Defect | Core Console | User Interface issues on Inbound Transmission page filter. |
| DT169121 | Defect | Gateway Console | Resend functionality is not working. |
| DT172889 | Defect | Transaction Server Other | Problem: Zelle processing timeout that is related to an SQL deadlock issue. Resolution: Modified the purge delete query to improve performance and prevent the deadlock. |
| Back to top | 3.2.10.1 interim fix 1 |
| Fix number | Type | Component | Description |
| DT139229 | Defect | Real Time Payments Console Core - Other |
Financial Transaction Manager is not populating certain fields on the Transfer Token page. |
| 137935 | Defect | Gateway - Other | Problem: Sending point validation error due to ACH reader parsing immediate origin. Resolution: Added a parameter to the Gateway Server properties to allow the user to toggle whether the first byte of the origin and destination in the ACH file header is truncated. |
| Back to top | 3.2.10.1 release |
| Fix number | Type | Component | Description |
| 137053 | Defect | Real Time Payments | Problem: After a client identifier for a participant was updated from one that was previously used by another participant, the transaction is failing. The client identifier was found for the original participant and not for the most recent participant. Resolution: The product now selects the correct client identifier that is associated with the correct participant. *** Note - The query was corrected, but the issue could remain until the Gateway cache is refreshed. You can refresh the cache in a few ways:
|
| 137384 | Defect | Database_Other | Problem: SQLCODE -433 errors are possible when you are using the Inbound Transactions page. This error can occur when columns with more than 20 characters long are passed into the user-defined function PARTNERS_NAME_BDID2 used by the view PAY_AND_NON_PAY_TXN_V. Resolution: The PAY_AND_NON_PAY_TXN_V view was changed to truncate the columns that are passed to the user-defined function PARTNERS_NAME_BDID2 to 20 characters. |
| 136992 | Defect | Real Time Payments | Problem: An issue was found where the PartnerType was still using the result from an old query when the CXCPayment.Read web service is used. That query was recently changed to better improve performance and introduced this issue. Resolution: Updated the web service response to not populate the result by using the old query, but populate the web service response with data that is provided from the new query. |
| Back to top | 3.2.10.0 interim fix 6 |
| Fix number | Type | Component | Description |
| DT198711 | Defect | Real Time Payments | Actor Organization Id is incorrect on the details from a result on the Transfer Token screen. |
| DT208791 | Defect | Real Time Payments | Financial Transaction Manager is updating the Fraud column incorrectly when multiple messages are being sent from Fraud for the same payment. |
| DT208938 | Defect | Real Time Payments | Recipient Names are not being trimmed when they enter the database. |
| DT211291 | Defect | Real Time Payments | Financial Transaction Manager is not able to handle Return scenario when recipient account is NSF. |
| DT213971 | Defect | Real Time Payments | Add recipient call flow needs to change depending on the status of token. |
| DT223035 | Defect | Real Time Payments | Financial Transaction Manager incoming Payments don't go through fraud check before transferring funds. |
| 146404 | Defect | Real Time Payments | Problem: FTM does not set the final status for incoming standard payments to "Settled" once settlement payment has been received. Resolution: Currently FTM does not support setting the status to "Settled". That functionality will be added in a future release. To help customers identify payments that have been reconciled, fields were added to the CXCPayment object in the CXCParticipantView.READ response and CXCPayment.READ response. The added fields are: fundsReversed and fundsTransfered. |
| Back to top | 3.2.10.0 interim fix 5 |
| Fix number | Type | Component | Description |
| DT130821 | Defect | Transaction Server Console | The incoming gateway is hanging that causes to be killed. |
| DT179219 | Defect | Real Time Payments | Issues have been discovered that a payment request can be sent to a mobile number that does not have a 1 appended to the front. |
| DT179700 | Defect | Core Real Time Payments |
Improve the readPendingCXCPaymentsForRecipientToken query. |
| DT189751 | Defect | Real Time Payments | Error is thrown for the entire ZRC contactscheck request when token size is greater than 255. |
| DT196534 | Defect | Transaction Server Console | Processing time out error. |
| DT196789 | Defect | Real Time Payments | Zelle Received Payments Information is not displaying under "Activity" tab. |
| DT196790 | Defect | Real Time Payments | Financial Transaction Manager is failing to cancel payments. |
| DT198719 | Defect | Core | Error while adding Individual Single/Multi Day limit with same description as before after it has been deleted. |
| DT198721 | Defect | Core Real Time Payments |
Recipient's Sent Payment Counter Issue. |
| DT198790 | Defect | Real Time Payments | DB2 Table Alter partition was executing with incorrect date range. |
| DT201255 | Defect | Real Time Payments | Zelle: realtime and standard payments appear in the same outbound ACH settlement batch. |
| DT201261 | Defect | Real Time Payments | Message - Application raised error or warning with diagnostic text: "Recipient nickname must be unique for a participant." |
| Back to top | 3.2.10.0 interim fix 4 |
| Fix number | Type | Component | Description |
| DT129313 | Defect | Real Time Payments | ContactsCheck service showing character number validation error for all tokens when only one is invalid. |
| DT141573 | Defect | Real Time Payments Console | Need to identify a small business vs a consumer payment in CXCParticipantView.Get (read) service response. |
| DT160191 | Defect | Real Time Payments | Incoming payment status changes from EWS are failing. |
| DT169123 | Defect | Core | Issue with updating and displaying limits. |
| DT169719 | Defect | Real Time Payments | Fraud User Exit is not invoked when a contact is re-added. |
| DT170170 | Defect | Core | Originator recipient nickname too long. |
| DT170409 | Defect | Core Real Time Payments |
Zelle - Lock timeouts causing transactions to be rolled back. |
| DT172033 | Defect | Real Time Payments | Failed payments stay in Pending processing instead of Canceled/Failed. |
| DT173020 | Defect | Real Time Payments | Recipient ID field is populated after adding a recipient. |
| DT172889 | Defect | Transaction Server Other | Zelle processing timeout related to SQL deadlock. |
| DT174544 | Defect | Real Time Payments | Tactical activations by Org Change notifications cause timeouts. |
| DT178401 | Defect | Core Real Time Payments |
Recipient token status not available for recipients that do not present in contact list. |
| DT178404 | Defect | Real Time Payments | ZellePaymentCleanupTask is unable to be scheduled. |
| DT178405 | Defect | Build Package | Recipient QR code response is outputting first or business name and last name field values as null. |
| DT178406 | Defect | Real Time Payments | Pending payment request is not marked as 'Canceled/Inactive'. |
| Back to top | 3.2.10.0 interim fix 3 |
Note: 3.2.10.0 interim fix 3 contains a security fix.
| Fix number | Type | Component | Description |
| DT148921 | Defect | Real Time Payments | Pending Processing Payments are accumulating. |
| DT160443 | Defect | Real Time Payments | Zelle Participant Directory page performance is slow. |
| Back to top | 3.2.10.0 interim fix 2 |
| Fix number | Type | Component | Description |
| DT129081 | Defect | Real Time Payments | Zelle Ready Contacts web service is getting a database exception with an error "Recipient nickname must be unique for a participant". |
| DT105093 | Defect | Distribution Console Distribution Engine |
File names for NACHA files are incorrect. |
| DT139229 | Defect | Core Other Real Time Payments Other Real Time Payments Console |
Incorrect data and missing fields are found when you are viewing the Transfer Token page. |
| DT143214 | Defect | Transaction Server Other | ITS Purge: Orphan presentment groups are not being purged for case of abandoned business day purge. |
| DT143731 | Defect | Core Real Time Payments |
Recipient table has incorrect last modified date. |
| 138493 | Defect | Core Other Real Time Payments Other |
Problem: Zelle Recipients are not being correctly populated in the participant directory and are not showing correctly on the customer's application. Resolution: Corrected issue where incorrect joins in queries might allow incorrect results to be returned. |
| 138471 | Defect | Risk Monitor | Problem: Risk monitors are always being applied to business days even if configured to calendar days. Resolution: Addressed issue where the payments were being applied to the incorrect dates. |
| Back to top | 3.2.10.0 interim fix 1 |
| Fix number | Type | Component | Description |
| DT124858 | Defect | Real Time Payments | Financial Transaction Manager is not handling the valid scenario when an actor ID can be null, which causes a validation error. |
| DT134144 | Defect | Real Time Payments | Transfer Token page fields aren't populated correctly when they are in the Early Warning Services getTokenHistory response as profileUpdated. |
| Back to top | 3.2.10.0 release |
| Fix number | Type | Component | Description |
| 131392 | Defect | NOC_Engine | Problem: NOC file processing was causing an exception in the case where the corresponding NOC, or the original record that caused the NOC, was not found. Resolution: When COR is received, the process now checks for the original item first. If the matching original item is found, it processes the NOC. If the original item is not found, the NOC refusal is generated based on the NOC item attempted processed. |
| 133458 | Defect | Zelle | Problem: Unnecessary processing and poor performance updating all Early Warning Services organizations during GetCXCOrganization task. Resolution: The refresh Early Warning Services organizations logic was updated so that new participant directory versions are only created for Early Warning Services organization participants when a new Early Warning Services organization is received. Or, when an actual organization change is received from Early Warning Services. |
| 134176 | Defect | Database_Other | Problem: Response time for Request For Payment and Initiate Credit Transfer web service APIs required improvement. Resolution: Changed a database index to improve the response time. |
| 134558 | Defect | Distribution_Engine | Problem: Eligible payments query does not work when processing presentment is used as the level for the presentment-ready handler. Resolution: Corrected the SQL that is called by the eligible transactions feature. Now, when the Distribution Ready indicator is set to a value of Yes on the processing batch (as opposed to the inbound batch), the payments are displayed and made available for processing by the eligible transactions feature. |
| 134563 | Defect | Distribution_Engine | Problem: In the Distribution user interface under Eligible Transactions, eligible sidepoints operations and filtering are not working correctly. Resolution: SQL related to the eligible transactions feature was corrected so that sidepoints of batches, which are eligible for distribution, are also displayed as eligible for distribution and available for processing by the eligible transactions feature. |
| 135108 | Defect | Distribution_Engine | Problem: Cancelling an inbound transaction for an already distributed outbound transmission is not working. Resolution: When a cancel operation is issued on a payment whose related outbound transmission was transmitted, issue a payment reversal rather than cancelling and unmapping the payment. |
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9JGN","label":"IBM Financial Transaction Manager for Digital Payments"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"}],"Version":"3.2.10"}]
Was this topic helpful?
Document Information
Modified date:
12 February 2024
UID
ibm16568417