Fix Readme
Abstract
This document contains V3.2.6 fix list information for Financial Transaction Manager for Digital Payments (DP) for Multiplatforms.
Content
V3.2.6 Fix List for Financial Transaction Manager for Digital Payments
This document contains fix list information for:
V3.2.6 Financial Transaction Manager for Digital Payments (DP) for Multiplatforms
The following table provides 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.6 Release Information for Financial Transaction Manager for Digital Payments.
| V.R.M.F fix list | Links to FixCentral download (by Fix ID) |
Product | Build Date | Pre-requisites |
| 3.2.6.1 interim fix 6 | 3.2.6.1-FTM-DP-MP-iFix0006 | DP | 20220304-1519 | 3.2.6.1 |
| 3.2.6.1 interim fix 5 | 3.2.6.1-FTM-DP-MP-iFix0005 | DP | 20211111-0756 | 3.2.6.1 |
| 3.2.6.1 interim fix 4.2 | 3.2.6.1-FTM-DP-MP-iFix0004.2 | DP | 20220113-1056 | 3.2.6.1 |
| 3.2.6.1 interim fix 4.1 | 3.2.6.1-FTM-DP-MP-iFix0004.1 | DP | 20211214-2148 | 3.2.6.1 |
| 3.2.6.1 interim fix 4 | 3.2.6.1-FTM-DP-MP-iFix0004 | DP | 20210915-0912 | 3.2.6.1 |
| 3.2.6.1 interim fix 3 | 3.2.6.1-FTM-DP-MP-iFix0003 | DP | 20210714-1900 | 3.2.6.1 |
| 3.2.6.1 interim fix 2 | 3.2.6.1-FTM-DP-MP-iFix0002 | DP | 20210526-0946 | 3.2.6.1 |
| 3.2.6.1 interim fix 1 | 3.2.6.1-FTM-DP-MP-iFix0001 | DP | 20210512-1900 | 3.2.6.1 |
| 3.2.6.1 | 3.2.6-FTM-DP-MP-fp0001 | DP | 20210127-1900 | None |
| 3.2.6.0 | Available from Passport Advantage | DP | 20201210-2223 | None |
Note: APAR links for security fixes aren’t active.
Refer to V3.2.6 Release Information for Financial Transaction Manager for Digital Payments (DP) for further details on issues and changes.
Note: The update instructions referred to by interim fixes are located in the install location\component\doc folder, for example: install location\shared\v326\pfs\Gateway\doc\updates.
| Back to top | 3.2.6.1 interim fix 6 |
| Fix Number | Type | Component(s) | Description |
| 133961 | Defect |
Transaction Server- Console
Web Services - Engine
|
Problem: When a Response to Request for Payment for the transit scenario (not on-us) is processed, Digital Payments retrieves routing information from the transmission. However, the on-us scenario might not have the transmission, which prevents correct processing of the Response to Request for Payment. Resolution: Digital Payments, for the on-us scenario, now retrieves the routing information such as Sender or Receiver from the transaction level instead of the transmission. The transit scenario continues to follow the existing process. |
| 133962 | Defect |
Transaction Server- Console
Web Services - Engine
|
Problem: The customer reference ID that is used in the on-us and transit scenarios are different, which causes a reference failure when Initiate Credit Transfer is the response to the on-us Request for Payment. Resolution: Digital Payments, for the on-us scenario, now retrieves the customer reference ID from the alternate transaction ID. The transit scenario continues to follow the existing process. |
| Back to top | 3.2.6.1 interim fix 5 |
| Fix Number | Type | Component(s) | Description |
| DT114193 | Defect |
Gateway Other
Transaction Server Console
Transaction Server Other |
Issues found with nonrequired fields during pain.001 validation. |
| DT114194 | Defect |
Gateway Other
Transaction Server Console
Transaction Server Other |
The Initiate Credit Transfer web service API and Create Request For Payment web service API does not enforce scheme validation. |
| 130018 | Defect | Web Services - Engine | Problem: The JAXB transformation was not enabled to validate the Create initiate credit transfer and Create request for payment web services API. Resolution: The new validateSchema request parameter is added for both Create Initiate Credit Transfer and Create Request for Payment web services API. If the new parameter is not used, the APIs ignore it so the compatibility with an earlier version is still supported. |
| Back to top | 3.2.6.1 interim fix 4.2 |
Note: 3.2.6.1 interim fix 4.2 contains a security fix.
| Back to top | 3.2.6.1 interim fix 4.1 |
Note: 3.2.6.1 interim fix 4.1 contains a security fix.
| Back to top | 3.2.6.1 interim fix 4 |
| Fix Number | Type | Component(s) | Description |
| DT108637 | Defect | Transaction Server Console Transaction Server Other |
RFRF API returned HTTP 207 in case it is in async mode transaction was successful. |
| DT108645 | Defect | Transaction Server Console Transaction Server Other |
RFI Webservice does not work for inbound RFP. |
| DT109393 | Defect | Core Other Transaction Server Console |
Participant details API results in 400 "Null". |
| DT109907 | Defect | Transaction Server Console Transaction Server Other |
Incoming API call in the evening hours is failing due to next business day not Active. |
| DT110176 | Defect | Transaction Server Console Transaction Server Other |
Purge BDay fails with SQL error. |
| DT110761 | Defect | Core Console | New Participant Profile error message not allowing to complete setup in first version. |
| DT112136 | Defect | Distribution Engine | Distribution Engine: Setting producer priority when the internal map payments message is posted |
| DT112137 | Defect | Distribution Engine | Transaction Server: Priority is not set on Messaging API event messages. |
| DT112159 | Defect | Distribution Engine | Distribution Engine: Modifying timing file stats for payment list processing so a single record is logged |
| DT112160 | Defect | Distribution Engine | Distribution Engine: Adding a stat to the timing files to show the message priority as read from the queue. |
| 127653 | Defect | Gateway Other | Problem: Gateway Servers log unlimited errors to the database at 10 per second. Resolution: Addressed issue when IBM MQ is down, Gateway was logging too many errors. |
| 127783 | Defect | Transaction Server Console | Problem: IP components behave differently for an ISF created by using APIs versus an ISF created by using an IBM MQ channel. Resolution: Addressed an issue where the API-created ISF data was missing the message name, which caused issues in IP. |
| 127798 | Defect | Transaction Server Console | Problem: When the Request For Return Of Funds web service is used, Digital Payments is not finding the correct Transaction ID to perform the action against. Resolution: Code fix for when the Request For Return Of Funds web service was used, Digital Payments was not finding the correct Transaction ID to perform the action against. |
| Back to top | 3.2.6.1 interim fix 3 |
| Fix Number | Type | Component(s) | Description |
| DT104146 | Defect |
Approvals Other
Transaction Server Console
|
Unable to see detailed information for transactions from approval page for rejects. |
| DT104147 | Defect | Transaction Server Console | initiateCreditTransfer web service does not map PmtInfId. |
| 124238 | Defect | Transaction Server Console Transaction Server Other |
Problem: Credit Transfer web service Master Flag issue. Resolution: When a transaction is created by using the Credit Transfer web service, the transmission's status was being set to active. This fix addresses that issue and uses a valid status, S_OutPTCreated, to create the transmission. |
| 125124 | Defect | Gateway Other | Problem: Gateway Server overwrites the batch priority that was set from the Immediate Payments batch in FTMFileReader. Resolution: In Gateway Server, the FTM file reader copies the priority from the incoming Immediate Payments file and batch to their Digital Payments counterparts. These values were being overwritten by the clearing attributes that are produced by Business Rules. The change was to not apply the clearing attribute priority whenever a priority was already set on the presentment record. |
| 125761 | Defect | Core Other Transaction Server Console |
Problem: Participant Detail API is returning the TCH statuses to SinglePoint as “available” even though PD is showing no TCH status. Resolution: This fix addresses the incorrect return of TCH data during the Read Participant Details web service by doing a role check. |
| Back to top | 3.2.6.1 interim fix 2 |
| Fix Number | Type | Component(s) | Description |
| DT103409 | Defect | Core - Other Web Services - Engine |
Participant ID not found error is generated during Create Schedule Model for newly created participants. |
| Back to top | 3.2.6.1 interim fix 1 |
| Fix Number | Type | Component(s) | Description |
| DT093078 | Defect | Transaction Server - Console | RFRF Accept and Return Response - Address Fields should not be required. |
| DT098603 | Defect | Core - Console Transaction Server - Console Web Services - Engine |
Update/PUT recurring model no longer requires Participant Account information. |
| DT099854 | Defect |
Core - Console
Core - Other
|
Create Schedule Payment Model API no longer requires payment scheme. |
| DT099935 | Defect |
Core - Console
Core - Other
|
Time zone issue for the Scheduled Payment Model API when recurring models are created or updated. |
| DT101548 | Defect | Web Services - Engine Transaction Server - Console |
Credit Transfer web service schema gives an error “LEI required for given orgId" |
| DT101959 | Defect |
Core - Other
Transaction Server - Console
|
Credit Transfer incorrect status of the response. |
| 117471 | Defect | Java - JRE | SECURITY: This defect provides a security fix. |
| 120675 | Defect | Java - JRE | SECURITY: This defect provides a security fix. |
| 121891 | Defect | Core - Other | Problem: DELETE recurring models API does not work. Resolution: This fix addresses the issue of missing values for the created and added by fields in the response when a Schedule Payment Model is created. The created field is populated by a timestamp during creation and the added by field is filled with the user who created the model. |
| Back to top | 3.2.6.1 release |
| Fix Number | Type | Component(s) | Description |
| DT089252 | Defect | Core - Other | Scheduledpaymentmodel not retrieving 'created' and 'createdby' in response. |
| 100495 | Defect | Framework - Console | SECURITY: This defect provides a security fix. |
| 112573 | Defect | Core - Console | SECURITY: This defect provides a security fix. |
| 114839 | Defect | Transaction Server - Console | Problem: Inbound batches page shows a plus sign (+) in the ID column. Clicking the plus sign (+) results in a Dojo error. Resolution: The query was corrected to display the page correctly. |
| 117178 | Defect |
Transaction Server Console
Web Services Engine
|
SECURITY: This defect provides a security fix. |
| 118529 | Defect | Transaction Server - Console | Problem: Nonpayment transaction detail is failing to render due to a missing retrying column. Resolution: The Retrying column needs to have either N or Y as its character value and not a null value. The null character prevents the transmission hierarchy page from being displayed correctly. |
| 118836 | Defect | Core - Console | Problem: Liberty business rules, workflow, retry config, web service fails when Business Rules Server is configured for SSL. Resolution: Updated the sample example for SSL configuration property to be defaultSSLConfig. |
| 118734 | Defect | Core - Console | Problem: Participant Directory - Activate of a New Version of a participant hangs. Resolution: This problem was caused by a code delivery error in the source code repository. The code delivery error was fixed. |
| 118965 | Defect | SDK | Problem: Liberty businessRulesServer needs to provide a sample Business Rules user exit and a user exit location in server.xml. Resolution: The sample Business Rules web services user exit was added under pfs\SDK\WebServicesBusinessRules along with the JAR files that are required to compile it. The instructions are also added in the Sample directory. |
| 119202 | Defect | Transaction Server - Console | Problem: Invalid parameter - Unknown column name RETRYING. Resolution: The missing RETRYING columns are added to the nonpayment transaction. |
| 119250 | Defect | Auto Adjust - Engine Business Rules - Other Transaction Correction and Reconciliation - Engine Transaction Server - Console Web Services - Other |
Problem: BusinessRulesServer web service invocations are not calling all the Business Rules user exit methods. Resolution: SampleBusinessRules now calls nonItemRequest and nonItemResponse when user exit is enabled. |
| Back to top | 3.2.6.0 release |
| Fix Number | Type | Component(s) | Description |
| DT088813 | Defect |
Risk Management -Console
Risk Management - Engine
|
Parent and child exposure limits are not working as expected. |
| DT089001 | Defect | Risk Management - Other | Cannot get Risk prefunded account processing to call the Risk prefunded user exit. |
| 108515 | Defect | Transaction Server - Console | Problem: Request for return of funds camt.056 on the Inbound Transactions page has no trace number information displayed. Resolution: Code was changed to use the correct database view. |
| 108516 | Defect | Transaction Server - Console | Problem: Request for return of funds camt.056 on the Inbound Transactions page is missing parties information. Resolution: Stored the RecipientName, CompanyName, or both, values in a database table. |
| 108518 | Defect | Database - Other | Problem: Request for return of funds camt.056 on Inbound Transactions page shows $0.00 as the system amount. Resolution: Code was changed to use the correct database view. |
| 108520 | Defect | Transaction Server - Console | Problem: Request for return of funds camt.056 on the Inbound Hierarchy page links to corresponding pacs.008 on the Related Txns tab but the tab is missing the pacs.002 back to the CSM. Resolution: Added to the related transactions tab those transactions that are related to the transmission the payment is for. |
| 117314 | Defect | Business Rules Console | Problem: Unable to activate release on the Control Center user interface. Resolution: The release state description requires a null check, in case the state is not finalized in releases. |
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPKQ5","label":"IBM Financial Transaction Manager"},"ARM Category":[{"code":"a8m50000000ClaTAAS","label":"Product Documentation"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"3.2.6"}]
Was this topic helpful?
Document Information
Modified date:
07 March 2022
UID
ibm16369157